TemplateDocs

Meeting agenda

An agenda that earns the meeting: a decision-shaped goal, timed topics with owners, and pre-reading — or a reason to cancel discovered in advance.

Last updated

Fill in the blanks

Assembled in your browser — nothing you type is stored or sent anywhere.

Your document

MEETING: Q4 pricing review When: Tue 9 Sep, 14:00–14:45 IST · Length: 45 min Goal — we are done when: we have chosen one of the three pricing options and named an owner for rollout Before the meeting, please read/do: - Pricing options doc (10 min read) - Your team's churn numbers for Q3 Agenda: 1. (5 min, Asha) Where the current pricing is losing us deals 2. (20 min, all) Walk the three options — objections on the table 3. (15 min, all) Decide, name the rollout owner 4. (5 min, Ravi) Next steps and comms Not today (parked on purpose): enterprise custom contracts — separate session with legal Notes and decisions will be captured in the meeting doc and shared the same day.

How to use it well

  • →Write the goal as "we are done when…" — if you can't finish that sentence with a decision or an artifact, the meeting is a status update and could be a message instead.
  • →A topic without an owner and a time box expands to fill the meeting; the numbers force the trade-off conversation before the room does.
  • →The "not today" line is the cheapest facilitation trick there is — scope creep dies faster when the parking lot is printed on the agenda.

Part by part

Goal — we are done when: {{goal}}
A completion condition rather than a subject. It is the difference between a meeting that can end and one that runs to its scheduled length.
Before the meeting, please read/do:
Pre-work stated as a requirement. Reading a document together in the room is the most expensive possible use of the time.
Not today (parked on purpose)
Names what is deliberately excluded, which is what stops the meeting drifting into the adjacent topic everyone would rather discuss.
shared the same day
A commitment about the output. Decisions circulated a week later have already been acted on or forgotten.

Common mistakes

  • An agenda that is a list of topics.

    Topics have no completion condition, so the meeting ends when time runs out rather than when it is finished. Stating what done looks like changes how the conversation is run.

  • Sending the pre-read with the invite an hour before.

    Nobody reads it, so the first fifteen minutes are spent reading in silence or, worse, pretending. Pre-work needs enough notice to actually be done.

  • No parked section.

    The adjacent interesting topic will come up, and without somewhere to put it the meeting either follows it or someone has to refuse it in the room. A written parking space does that job impersonally.

Questions

What makes a good completion condition?

Something observable: a decision made, a plan agreed, three risks ranked. Discuss the roadmap is not one, because there is no state at which discussing is complete.

How far ahead should the agenda go out?

With the invite where possible, and at minimum a day before if there is pre-work. An agenda arriving on the morning is a description of the meeting rather than a chance to prepare for it.

What if there is no goal?

Then it probably should not be a meeting. Status that can be read, decisions that can be made asynchronously, and updates with no discussion are all cheaper written down.

Should the agenda have timings?

For anything over an hour or with several topics, yes — it forces a decision about relative importance before the room does it by accident. For a short focused meeting it adds ceremony without value.

Related in Templates