How to run effective meetings with purpose, outcome, and agenda

Executive overview

Most meetings fail because no one has been trained to run them well. The fix isn't fewer meetings — it's building the skills and cultural norms that make meetings worth attending.

Every meeting needs a clear purpose, a maximum of three outcomes, and an agenda. Without these, people can't opt in or out intelligently.

Meetings don't suck — people just haven't been taught how to run them.

Core meeting rules

• Every meeting needs a stated purpose: why is it happening?
• Maximum three outcomes per meeting; more than three means a separate meeting
• Always send an agenda in advance so attendees can self-select
• Book meetings for half the time you initially think they'll need
• Start on time regardless of latecomers — the race doesn't wait
• Every meeting ends five minutes early so people can transition without running late

Opting out is a skill, not rudeness

• Attendees should read the purpose, outcome, and agenda before deciding to attend
• Leaders don't need to attend every meeting — their job is to grow people, not fill chairs
• Partial attendance is valid: join for your agenda item, then leave
• Never say yes to a meeting invite without checking the agenda first

Leader's role is to grow people, not solve problems

• When a direct report asks what to do, ask them what they think instead
• Send them away to figure it out; only coach on the gaps when they return
• Teaching someone to think through a problem is more valuable than answering it
• Fix the meeting structure so your team can run meetings without you

Naming meetings by purpose

• Name recurring meetings after their function, not the group (e.g. "War meeting", "Storm meeting", "Finance meeting")
• War meeting (Weekly Action Review): dashboards, weekly priorities, five-minute updates
• Storm meeting (Strategy and Review): topics six to twelve months out
• Finance meeting: budget, cashflow, general ledger review
• Functional leaders can then attend each other's team meetings without confusion

Meeting rhythm and cascade

• All team meetings should occur at the same time each week
• Run them immediately after the leadership meeting so information flows straight down
• The head of each function walks out of leadership and into their team meeting