First, the test for whether it should exist
Before the rules, the question that removes more wasted time than all of them combined: what decision will be made in this meeting, and who has to be present to make it?
If there is no decision, you have a broadcast, and a written update reaches more people at lower cost. If there is a decision but the person who makes it is not invited, the meeting will produce a recommendation and a second meeting.
The test
A meeting earns its place when people need to respond to each other, not just to you. Information flows better in writing. Disagreement, ambiguity, and anything where tone matters flow better in a room.
The 10 rules
Give it a decision, not a topic
"Q3 planning" is a topic. "Agree the three priorities for Q3" is a decision. The second one tells people what preparation is useful and makes it obvious when you are finished.
Meetings without a stated decision expand to fill the slot, because nothing signals completion.
Write it in the invite titleSend the agenda before, not at the start
Twenty four hours ahead where possible. Three or four items, each with a purpose: decide, discuss, or inform.
An agenda revealed at the start of the meeting gives nobody time to prepare, so the first ten minutes are spent watching people read.
24 hours aheadMark each item: decide, discuss, informInvite the smallest group that can decide
Everyone who is needed for the decision, and no one else. People who need the outcome get the notes.
Each additional attendee makes the meeting slower and quieter. Past seven or so, most people switch to observing.
Optional attendees are usually not neededStart on time, whoever is missing
Waiting five minutes for a latecomer charges everyone who arrived on time. Do it twice and punctuality stops being worth anyone's effort.
Brief the person who arrives late in ten seconds, at the next natural break, not by rewinding.
Costs nothing to enforceFixes itself within two weeksOne person facilitates
Someone is responsible for keeping to the agenda, bringing in people who have not spoken, and cutting off tangents. It does not have to be the most senior person, and often works better when it is not.
Unfacilitated meetings are dominated by whoever is most comfortable talking, which is unrelated to who has the most useful thing to say.
Name them in the invitePut the decision first
Agenda order should be by importance, not by chronology or by how easy an item is. Updates last, or better, in writing beforehand.
Meetings overrun. The only question is which item gets squeezed, and it should never be the one you called the meeting for.
Updates go last, or in writingPark tangents visibly
When something important but off-agenda comes up, write it in a visible parked list and move on. Say you are doing it.
This works because the person raising it can see it has not been dismissed. Without the visible list, they will keep returning to it.
Review the parked list at the endAsk the quiet people directly
"Anyone have thoughts?" reaches the people who were going to speak anyway. Naming someone and asking for their view reaches the rest.
In most teams the person with the most relevant objection is not the most confident speaker, and the cost of not hearing it is a decision that gets reversed later.
Name people, do not open the floorEnd by stating the decision out loud
In the last two minutes, say what was decided, who owns each action, and by when. Out loud, while everyone is still present.
This is where meetings most often fail. Everyone leaves with a slightly different understanding, and the disagreement surfaces a fortnight later as a missed deadline.
Two minutesNever skip when running lateSend the notes the same day
Short. What was decided, who owns what, when it is due, and what was parked. Not a transcript.
Same day matters because it lets anyone who understood something differently correct it while it is still cheap to correct.
Decisions and owners onlySame day, not same week
Matching the format to the purpose
Different meetings fail in different ways, and applying one format to all of them is why some meetings feel pointless even when they are run competently.
| Purpose | Right length | Who attends | Ends with |
|---|---|---|---|
| Daily coordination | 15 minutes | The delivery team | Blockers assigned |
| A single decision | 20-30 minutes | Decision maker plus inputs | The decision, stated |
| Planning a period | 60-90 minutes | Team plus whoever sets priorities | Priorities and owners |
| Discovery with a customer | 30-45 minutes | Two of you at most | Confirmed understanding |
| Retrospective | 45-60 minutes | The team, no observers | One or two changes |
| Status broadcast | Should be written | Nobody | A document |
What to do about recurring meetings
Recurring meetings are where calendars silently fill up, because nobody ever revisits the decision to create one.
Twice a year, take every recurring meeting and ask three questions. Has it produced a decision in the last month? Would anyone notice if it stopped? Could it be half as long or half as frequent?
Then act on the answers. Cancel the ones that fail all three, and be specific with the ones that survive: shorten them, cut the invite list, or merge two that involve the same people covering adjacent ground.
A quicker version, if a formal audit is not going to happen: cancel a recurring meeting for two weeks and see who asks for it back. The ones nobody misses were costing real hours every week for no return.
Frequently asked questions
- How do I know if something should be a meeting or an email?
- If the purpose is to transfer information, write it. If the purpose is to reach a decision that needs discussion, or to handle something where tone matters, meet. The test is whether you need the other people to respond to each other, not just to you.
- How many people should be in a meeting?
- As few as can make the decision. Beyond about seven, most attendees stop contributing and start observing, and the meeting becomes a broadcast with extra cost. Anyone who only needs the outcome should get the notes instead of the invite.
- How long should a meeting be?
- As long as the agenda requires, which is rarely the default 30 or 60 minutes your calendar offers. Booking 20 or 45 minutes instead is a small change that recovers a surprising amount of time and gives people a gap between calls.
- Should you record meetings?
- Recording helps for meetings where people need the detail later and where not everyone could attend. Tell people it is happening and check the consent rules that apply where your attendees are, since these differ by country and in some cases require everyone's agreement.
- What do I do about a meeting I was invited to but do not need to attend?
- Decline and ask for the notes. Doing this openly is what makes it acceptable for everyone else. In most teams the volume of unnecessary attendance persists because declining feels rude rather than because anyone believes the attendance is useful.
- How do I stop a meeting from running over?
- Put the decision first rather than last. Meetings run over because the important item sits at the end of the agenda after the updates, so any overrun eats the part that mattered.
