What the research says about agendas
Meetings take up a large share of a leader's week. Leslie Perlow, Constance Noonan Hadley and Eunice Eun, writing in Harvard Business Review in 2017, point to research showing that executives spend nearly 23 hours a week in meetings, up from less than 10 hours in the 1960s1. An agenda is the cheapest tool for making those hours count.
The evidence that agendas help is real, but narrower than most advice suggests. In a 2011 study in Group Dynamics, Melissa Cohen, Steven Rogelberg, Joseph Allen and Alexandra Luong surveyed 367 working adults within 48 hours of their last staff or team meeting2. Using an agenda was one of the features linked to how good people rated the meeting. So were starting on time, the quality of the room, who ran it, and how many people came2.
Two things that study does not show. First, it measured how people rated the meeting, not what the meeting produced. Second, it asked whether an agenda was used, not what was on it. A list of topics such as "Q2 update" and "Budget" counts as an agenda, and it still leaves everyone guessing what the meeting is for. The sections below are about writing one that does more than exist.
How to write a meeting agenda that works
Start with what the meeting must produce. Write one sentence at the top: "By the end, we will have decided X" or "we will leave with Y." If you cannot write that sentence, the meeting may not need to happen. A status update can go out in writing instead.
Write each item as a question. "Budget" is a topic. "Do we move $20,000 from events to hiring?" is a question the group can answer. A question tells people what to think about beforehand, and it tells the room when the item is done.
Give each item a time and an owner. The time says how much the item is worth. The owner is the person who opens it and closes it. If the times add up to more than the meeting, cut an item now, not at minute 50.
Send it ahead with anything people need to read. Group discussion tends to stick to what everyone already knows. In a classic 1985 experiment by Garold Stasser and William Titus, groups given all the facts picked the best option 83% of the time. When the same facts were split among members, only 18% of groups found it3. A short pre-read, and a request that each person bring their own view in writing, puts the missing facts on the table.
Save the last minutes for owners and next steps. In a study of 92 videotaped team meetings, published in Small Group Research in 2012, Simone Kauffeld and Nale Lehmann-Willenbrock found that teams whose meetings had more problem solving and action planning were more satisfied with them. Constructive meetings were linked to company success two and a half years later. Complaining and criticizing others hurt more than the good behaviors helped4.
A weak agenda and a stronger one
This is the Q3 planning kickoff example shown above, rewritten. The team and its details are generic, for illustration. Both versions run 60 minutes.
| Weak | Stronger |
|---|---|
| 5 min: Welcome and goals for the session | 5 min: Read the goal aloud: "We leave with three Q3 priorities, each with one owner." (Chair) |
| 15 min: Review Q2 results and learnings | 10 min: What did Q2 teach us that should change Q3? (Results sent as a one-page pre-read two days ahead; the room discusses questions only.) |
| 20 min: Draft Q3 priorities together | 25 min: Which three priorities for Q3, and what are we choosing not to do? (Each person sends their top three in writing the day before.) |
| 15 min: Assign owners and next steps | 15 min: Who owns each priority, and what is the first step by Friday? |
| 5 min: Wrap-up and decisions recap | 5 min: Read back each decision, owner and date. Anything undecided gets an owner and a deadline. |
The weak version names subjects. The stronger one says what each block must produce, who leads it and what people do before they arrive. The time moved from reporting to deciding.
Common mistakes
- Too many items. Eight topics in an hour leaves about seven minutes each once people settle in. Three to five real questions is plenty.
- Updates on the agenda. Anything people could read on their own should be a pre-read, not a speech.
- The hardest item last. Put the decision that matters most where energy is highest, near the start.
- No closing slot. Without time set aside to name owners, the meeting ends on the clock and the decisions drift.
A kickoff meeting agenda
A kickoff is the first meeting of a project or a new team. Its job is not to share a slide deck. It is to make sure everyone leaves with the same answer to five questions: why this work matters, what done looks like, what is out of scope, who decides what, and what could sink it. Here is a sample 60-minute project kickoff agenda.
| Time | Question | What it produces |
|---|---|---|
| 5 min | Why this project, and what does done look like? | The goal and the finish line, said by the sponsor |
| 10 min | What is in scope, and what is out? | A written in and out list everyone has heard |
| 10 min | Who does what, and who makes which calls? | Named owners and decision rights |
| 15 min | It is six months from now and the project failed. Why? | The top risks, each with an owner |
| 10 min | How will we work together? | Check-in rhythm, where updates live, how to raise a problem |
| 10 min | What happens this week? | First steps, each with an owner and a date, read back aloud |
The fourth block is the pre-mortem, described by Gary Klein in Harvard Business Review in 20075. The team imagines the project has already failed and lists plausible reasons, in silence first. People with doubts can voice them at the start, so the plan can be improved rather than examined after it fails5.
Write the answers down where the team can find them. A project charter holds the goal and scope, a RACI matrix holds who does what, and a risk register holds what came out of the pre-mortem.
What an agenda will not fix, and what to use next
An agenda shapes one meeting. It does not answer:
- Whether the meeting should happen. If nothing needs to be decided or worked out together, send a written update instead.
- Whether the right people are in the room. Invite the people who must decide or do the work. Others can read the notes.
- What happens after. Decisions are only as good as their follow-through. Turn the notes into owned tasks with the meeting action items tool.
- Longer sessions. A day or more away needs a different shape, with breaks, pre-work and a clear output. See the offsite agenda generator and the leadership offsite guide.
For one-to-one meetings, use the one-on-one agenda tool. For looking back at the end of a project, try the retrospective generator.
Frequently asked questions
- How do you structure a meeting agenda?
- Start with a quick opener, work through the key topics with a time budget for each, and end with decisions and next steps. Allocate time so the topics fit the total length.
- Why send an agenda in advance?
- It lets people come prepared, signals respect for their time, and gives anyone the standing to ask "is this meeting necessary?" before it happens.
- How long should a meeting be?
- As short as the agenda allows. Default to 25 or 50 minutes instead of 30 or 60 to build in breaks, and cut any topic that does not need the whole group.
- What makes a good meeting agenda?
- A good agenda says what the meeting must produce, lists three to five items written as questions, and gives each one a time and an owner. It goes out ahead with any pre-reads and saves the last minutes for owners and next steps. A 2011 study in Group Dynamics linked agenda use to how highly people rated their meetings2, but a list of topics alone still leaves people guessing what each item is for.
- What should be on a kickoff meeting agenda?
- Five questions: why the project matters and what done looks like, what is in scope and what is out, who does what and who makes which calls, what could make it fail, and what happens this week. A 60-minute kickoff can give each one 10 to 15 minutes, with a short opening and a read-back of owners and dates at the end.
- How do you run a kickoff meeting?
- Send the goal and any background a few days ahead so the meeting is spent on questions, not slides. Have the sponsor open with why the work matters. Run a pre-mortem: everyone imagines the project has already failed and writes down why, in silence first, a method Gary Klein described in Harvard Business Review in 20075. Close by reading back each owner and first step, then write it all down in a project charter.
Sources
- Leslie A. Perlow, Constance Noonan Hadley and Eunice Eun, "Stop the Meeting Madness," Harvard Business Review, July to August 2017. hbr.org
- Melissa A. Cohen, Steven G. Rogelberg, Joseph A. Allen and Alexandra Luong, "Meeting design characteristics and attendee perceptions of staff/team meeting quality," Group Dynamics: Theory, Research, and Practice 15(1), 2011, pp. 90 to 104. doi.org
- Garold Stasser and William Titus, "Pooling of Unshared Information in Group Decision Making," Journal of Personality and Social Psychology 48(6), 1985. doi.org
- Simone Kauffeld and Nale Lehmann-Willenbrock, "Meetings Matter," Small Group Research 43(2), 2012, pp. 130 to 158. doi.org
- Gary Klein, "Performing a Project Premortem," Harvard Business Review, September 2007. hbr.org
Written by Tom Olajide, Founder. Last reviewed September 24, 2026.