Successful Meetings: Make every meeting produce a decision or durable output
A meeting has attendees and an agenda, but no one has named the decision, action, learning, or relationship outcome it must produce.
The useful response is not more ceremony. It is a mechanism that can make every meeting produce a decision or durable output.
What the skill produces
The Successful Meetings skill turns supplied context into a meeting packet, a recorded outcome, and owned follow-up actions. It should expose missing evidence instead of inventing it. The free skill packages this mechanism for explicit use. It does not fetch remote instructions, and the practitioner remains responsible for the facts and final decision.
Run the mechanism
- Name the outcome and meeting owner before inviting attendees.
- Send the evidence and questions early enough to review.
- Record the decision, action owner, and due date before the meeting closes.
The owner should review the output against the original evidence before it is used. Any unresolved assumption stays labeled, with an owner and date when it affects the decision.
Failure check
The process becomes theater when the packet exists but the meeting still ends without a decision or owned action.
Attribution boundary
Andy Grove described meetings as a medium for managerial work. This skill applies that operating idea without claiming the framework as original.
Adoption test
Pilot the skill on one recurring meeting for four occurrences. Compare decisions reached, actions closed by date, and person-hours used.
Keep the skill only if it improves the artifact or decision against that baseline. Revise the playbook when the same failure survives more than one review cycle.
Infographic
