Stop Running Bad Meetings: How to Use an Agenda That Actually Works

The default meeting in most organisations is a standing time slot with a vague title. "Weekly sync." "Project catch-up." "Team meeting." These titles tell attendees nothing about what they need to prepare, what decisions need to be made, or what success looks like for the 60 minutes they are about to spend.

When people arrive at a meeting without knowing its specific purpose, they fill the time with what they do know: status updates, tangential discussions, and loosely related concerns. The meeting becomes a container for whatever is on people's minds, rather than a focused effort to achieve a specific outcome.

An agenda is not a formality — it is the mechanism that converts meeting time into output. Without one, you are gathering people in a room and hoping something useful emerges.

Before you list agenda items, write a single sentence that completes this prompt: "By the end of this meeting, we will have _______________."

This is not the meeting topic — it is the specific, concrete output required. Compare these two statements:

Topic: "Discuss Q3 priorities" — this could mean anything and end anywhere.

Objective: "Decide which three features go into Q3, with owners assigned to each" — this is a statement that can be true or false at the end of the meeting. Either you achieved it or you did not.

The objective determines everything else about the agenda: what needs to be covered, in what order, how much time each item gets, who needs to be in the room, and what people should prepare in advance. Get the objective right first. The rest follows.

Different meeting types need different structures. A template that works for a decision meeting will fail as a brainstorm, and a retrospective format will frustrate a client presentation. Here are the core structures for the most common types:

Decision meetings: Open by stating the decision criteria (not the options — that comes later). Present relevant data. Discuss options against the stated criteria. Make the decision. Assign owners and next steps. The facilitation trap here is presenting options before criteria — it anchors the group to whatever is presented first.

Standups: Three questions, one person at a time, strict time limits. What did I complete? What will I do today? What is blocking me? Standups fail when they become status reports to management rather than coordination between peers. If the information is only flowing one direction (up), it is a status call, not a standup.

Retrospectives: Give people time to write anonymously before discussing. Group similar themes. Vote on the most important to address. Commit to one specific change — not five. Retrospectives that produce only discussion and no committed action are performance rather than improvement.

Brainstorms: Separate generation from evaluation — never judge ideas during the generation phase. Use prompts and constraints to push past obvious answers. Quantity before quality. Evaluation comes after, in a separate phase or meeting.

One of the most common agenda failures is allocating insufficient time to the items that actually require discussion. A meeting on a contentious topic with 30 people affected by the decision cannot be resolved in the same slot as a routine status update.

A useful rule: identify the single most important agenda item — the one where the meeting fails if this is not resolved. Allocate roughly 40% of your total time to this item. Everything else fits around it. If you cannot fit everything else around it, the secondary items should either be moved to a follow-up meeting or handled asynchronously before the main meeting.

Build in 5 minutes at the start for alignment (confirm the objective, confirm everyone has the context they need) and 5 minutes at the end for next steps (who owns what, by when). These bookends are not wasted time — they are what convert discussion into action.

An agenda sent 10 minutes before a meeting is a formality, not a tool. For the agenda to change attendee behaviour — to prompt preparation, pre-reads, and advance thinking — it needs to arrive at least 24 hours before the meeting.

Include with the agenda: the objective (the one-sentence completion from above), any documents or data people should review in advance, and what you expect from each attendee (a decision, a perspective, a piece of information). When people know what is expected of them, they show up differently.

In the meeting itself, open by reading the objective out loud and confirming everyone agrees that is the goal. This takes 30 seconds and prevents the common drift where different people have different ideas about what the meeting is for. At the end, do not end until you have an explicit summary of decisions made and next steps assigned, with names and dates.

The best meeting productivity tool is the question: does this need to be a meeting at all? Many meetings exist because scheduling a call is the path of least resistance, not because it is the right format for the task.

A decision that requires input from three people can often be made with a short document circulated for comment, with a 48-hour deadline for objections. A status update can be an async message. A brainstorm can be a shared document where people add ideas over 24 hours before a shorter, more focused discussion.

Use meetings for the things meetings are genuinely best at: real-time debate on a complex topic, building shared understanding through discussion, and decisions that require multiple people to commit in the moment. For everything else, consider whether a different format would be faster and less disruptive.