An agenda is usually treated as a formality — a list of topics pasted into an invitation so the meeting looks organised. Used properly it does something more useful: it forces the organiser to say what the meeting is for, and in doing so it frequently reveals that the meeting is not needed. A good agenda is the cheapest meeting-reduction tool available, and it makes the meetings that survive substantially better.
The agenda is a test, not a formality
Before it is a document, an agenda is a question: what specifically will be different when this meeting ends?
If the answer is "everyone will be updated", you have a written update, not a meeting. If the answer is "we will have decided between A and B", that is a meeting — and one you can now prepare properly. If you cannot answer at all, the meeting should not happen, and writing the agenda is how you find that out before twelve people spend an hour.
This filter alone removes a surprising proportion of recurring meetings. Related: reducing your team's meeting load and email vs document: choosing the right medium.
Write items as outcomes, not topics
The single change that improves agendas most: stop writing nouns.
- Not "Budget" → "Decide whether to move the £40k contingency to Q4 (decision, 15 min, Priya)"
- Not "Roadmap" → "Agree which two of the five proposed features go into the next release (decision, 20 min, Sam)"
- Not "Customer feedback" → "Review the three themes from last month's interviews and decide whether any change the plan (discussion, 15 min, Alex)"
Each item gets four things: the outcome, the type, the time, and the owner.
The type matters because it sets expectations about how the item runs:
- Decision — a choice will be made in the room. Options should be circulated beforehand.
- Discussion — input is needed; the decision comes later, and by whom should be stated.
- Information — something must be told. This should be rare, because information is what documents are for. Anything on the agenda as "information" is a candidate for deletion.
Writing "information" next to an item is a useful embarrassment. If half your agenda is information items, you are holding a broadcast.
Timing that is honest
Assign minutes to each item, and make them add up to less than the meeting length. Two consequences follow, both good: you cannot fit ten items into an hour, so you have to choose; and the timings expose which item actually matters.
Two practices worth adopting:
- Put the most important item first, not third. Meetings run out of time at the end, and the item that was going to matter most gets four rushed minutes. The convention of warming up with small items is how important decisions get made badly.
- Leave the last five minutes for actions. Explicitly. Not "any other business" — a slot for confirming who is doing what by when, which is the only part of the meeting that produces anything. See tracking action items after meetings.
Pre-reading, and the discipline it needs
If a decision needs context, that context should be read before, not presented during. Presenting information to a room of people who could have read it faster themselves is the most common way meeting time is wasted.
For this to work:
- Send materials at least 24 hours ahead, and say explicitly that they are pre-reading rather than reference.
- Keep it short. A one-pager gets read; a 30-page deck does not. See writing a one-page summary.
- Handle the people who did not read it. The approach that actually works, borrowed from Amazon's practice, is silent reading at the start of the meeting — ten minutes, everyone reads, then discussion. It feels strange once and then becomes obviously correct, because it guarantees a shared basis without punishing anyone.
- Do not present the pre-read. If you summarise it aloud, nobody will read it next time, and you have taught the room that reading is optional.
The recurring meeting problem
Recurring meetings accumulate a fixed agenda that ossifies, and they persist long after their reason has gone.
- Write a fresh agenda every time. A standing agenda that is identical each week is a signal that the meeting has become a ritual.
- If there is no agenda by the day before, cancel it. State this as a rule, and hold to it. Nothing reduces pointless meetings faster, and it costs nothing.
- Review the meeting itself quarterly. Is it producing decisions? Could it be a written update? Could it be half as long or half as frequent? Are all these people needed? See running a productive retrospective.
Who is in the room
The invitation list is part of the agenda decision, and it is where meeting cost multiplies. An hour with ten people costs ten hours.
- Invite people who will contribute to an outcome, not people who might want to know. The latter get the notes.
- Say why each person is there if it is not obvious, especially for one-off meetings. "Jo for the compliance question in item 3" tells Jo what to prepare and lets them leave after item 3.
- Make attendance optional explicitly where it genuinely is. People treat every invitation as mandatory unless told otherwise.
- Stagger attendance for long agendas so people attend only their items. It looks fussy and saves hours.
The agenda after the meeting
An agenda written as outcomes becomes the skeleton of the notes almost for free. Each item has a stated intended outcome; the notes record what was actually decided against it, and the gap between the two is itself informative.
Keep the notes short and decision-focused — meeting notes that get read — and put the actions where work is actually tracked rather than in the document. The record of what was decided and why belongs somewhere durable: writing a decision log.
A template
Meeting: Pricing review
Date: 12 Aug, 14:00–14:45
Purpose: Decide the Q4 list price for the Pro tier.
Pre-reading (sent 10 Aug): pricing analysis one-pager [link]
1. Decide Q4 Pro tier list price decision 20 min Priya
Options in the pre-read; recommendation is Option B.
2. Agree the migration approach for
existing annual customers decision 15 min Sam
3. Confirm actions and owners 5 min all
Not covering: enterprise pricing (separate session, 19 Aug).
Attending: Priya, Sam, Alex, Jo (item 2 only).
The "not covering" line is worth stealing. It prevents the meeting sprawling into the adjacent topic everybody wants to discuss, and it reassures people that the topic is not being ignored.
Summary
Write agenda items as outcomes with a type, an owner and a time, put the most important one first, and reserve the last five minutes for actions. Circulate pre-reading and do not present it in the room — or read it silently together at the start. Invite people who will contribute rather than people who want to know. And if you cannot write down what will be different when the meeting ends, cancel it: the agenda's most valuable function is telling you the meeting is unnecessary.
