Write an agenda that shortens the meeting

An agenda shortens a meeting when it lists questions to answer instead of topics to discuss. "Q3 roadmap" fills an hour. "Do we cut feature A or push the date?" can be answered in nine minutes, and everyone can feel when it has been.

Topics are the standard format, and topics are the problem. A topic has no finish line. Nobody can tell when "marketing update" is done, so it is done when the clock says so, and the clock always says the full hour.

Turn every item into a question

Each agenda line should be a question specific enough that the group will recognize its own answer.

The rewrite is mechanical once you start doing it:

• "Hiring" becomes "Do we open the second support role now or after the busy season?"
• "Website feedback" becomes "Which of the three homepage drafts ships?"
• "Budget" becomes "Whose line item covers the conference?"
• "Project status" becomes nothing, because status is a message, not a meeting.

Something useful happens while you do this rewrite: items die. Half the topics on a typical agenda cannot be turned into a question, and an item that cannot be phrased as a question is an item with no decision in it. It is there to perform activity. Deleting it is not rude; it is the agenda doing its job before the room fills.

I hold myself to this when building Unvent. Before any sizable piece of work, the plan starts as a written question with options under it, because "think about the onboarding" produced a week of circling and "does onboarding happen before or after the first rewrite?" produced an answer in an afternoon. Rooms full of people work the same way as one stubborn builder.

Put the decision owner on every line

A question without a named decider defaults to being decided by whoever talks longest.

The format that works is question, owner, time: "Which homepage draft ships? (Dana decides, 10 min)". The owner is not the person who talks most; they are the person who ends the item. When the ten minutes run out, they choose, and the meeting moves.

This feels autocratic to people used to consensus, so it is worth saying what it actually changes. The discussion still happens. Dissent still gets aired. What disappears is the fourth lap around the same disagreement, the one that exists because nobody in the room had the authority to stop it. Most meeting fatigue is not too many opinions; it is laps.

If you cannot name an owner for a question, you have found a different problem, and the meeting will not fix it. Take that one to whoever assigns ownership, separately.

Send it early enough to do damage

An agenda sent the night before does half the meeting's work before anyone joins.

Questions have a property topics lack: people start answering them the moment they read them. Send "do we cut feature A or push the date?" a day ahead and attendees arrive having already thought, or having already replied "push the date, A is half done anyway" in the thread, at which point the item is settled and the meeting shrinks by ten minutes.

An agenda sent two minutes before the call is a seating chart. For it to shorten anything, it needs:

• A real head start: half a day minimum, more across time zones.
• Any pre-reading attached to the question it serves, not dumped in a folder.
• An invitation to answer early in writing, said outright: "If you have a clear answer to any of these, reply before the call and we'll skip it."

That last line is the one people skip, and it is the one that deletes meetings. Some weeks every question gets answered in the thread, and the calendar invite quietly dies. This should be counted as the agenda succeeding, not the meeting failing.

The agenda is also the recap

A question-shaped agenda turns into the meeting notes by having its answers written under it.

When the agenda was "marketing, hiring, misc", writing the recap afterwards is a reconstruction job, which is why it rarely happens. When the agenda was five questions, the recap is those five lines with the decisions filled in. Same document, sent twice: once with holes, once without.

The answers want the same discipline as the questions. "We aligned on next steps" is a hole wearing a suit. "Draft B ships; Dana tells the agency Friday" is an answer, and a recap of decisions written that plainly is what makes them stick past the weekend.

Keep the answered agendas in one running document per meeting series, newest at the top. That file becomes the cheapest institutional memory your team owns: every decision, dated, with its question still attached, findable by anyone who wonders "wait, why did we cut feature A?" eight months later.

The recurring meeting test

A recurring meeting whose agenda is empty two days out should be cancelled that week, out loud.

The empty agenda is information. No questions means no decisions are waiting, and a meeting with no decisions waiting is a status ritual that a written update covers in four minutes of nobody's shared time. Cancelling publishes a small, healthy precedent: this meeting exists for its questions, not for its slot.

People worry the slot will die entirely. Good. A slot that dies from lack of questions was already dead; you have just stopped catering it. The weeks that matter, when there are five real questions and a named owner on each, the meeting comes back sharp, and people show up on time for it, because time in that room has started meaning something again.