How to Run a Meeting That People Actually Want to Attend
The bad meeting is among the most expensive, most avoidable, and most persistent inefficiencies in modern organizational life. The good meeting is a learnable skill.
A 2022 analysis by Steven Rogelberg at the University of North Carolina estimated the annual cost of unnecessary or poorly run meetings to the U.S. economy at approximately $37 billion in lost productivity. That number has almost certainly grown since. The estimate does not include the harder-to-quantify costs: the frustration that erodes engagement, the creative work that doesn't happen because a scheduled meeting broke the focus needed to do it, and the signal that poorly run meetings send about an organization's relationship to the time of its people.
The frustrating thing about this cost is how avoidable it is. A badly run meeting is not the product of complex organizational dysfunction — it is usually the product of a few specific, nameable problems: unclear purpose, wrong participants, no preparation, no decision, no record. Each of these has a clear and uncomplicated solution. The gap between knowing the solution and implementing it is, like most organizational gaps, primarily a matter of habit and accountability.
The good news is that meeting quality is a learnable, improvable skill, not a talent. The people who consistently run meetings that others describe as productive and worth attending are not blessed with some charismatic gift for facilitation. They have developed specific practices — around preparation, structure, facilitation, and follow-through — that they apply consistently. The practices are not complicated. They are just rarely taught.
Before the Meeting: The Decisions That Matter Most
The most important meeting decisions are made before the meeting begins, and most of them are made poorly or not at all.
The first decision is whether the meeting should happen at all. A meeting is justified when it requires real-time interaction between multiple people to accomplish its purpose — when the outcome depends on the back-and-forth of a conversation, the synthesis of multiple perspectives in the moment, or the social dynamics of a group making a shared commitment. A meeting is not justified when its purpose is to share information that could be read, to collect input that could be gathered asynchronously, or to maintain the appearance of collaboration without its substance. The proportion of organizational meetings that fall into the second category is large.
The second decision is who should attend. The research on group decision-making suggests that larger groups produce slower decisions, more diffuse accountability, and a higher proportion of time spent on social management rather than substantive progress. The effective meeting is the one with the minimum number of people required to achieve its purpose — not all the stakeholders who have an interest, not everyone who might feel excluded if not invited, but the specific people without whom the purpose cannot be accomplished.
The Amazon two-pizza rule
Jeff Bezos famously held that if a meeting required more than two pizzas to feed its participants, it was too large. The principle is directionally sound even if the specific unit of measurement is arbitrary: most working meetings are most effective with five to seven participants. Every additional person adds coordination overhead, reduces individual contribution, and dilutes accountability for outcomes.
The third decision — made even less often than it should be — is what the meeting must produce. Not what will be discussed, but what decision will be made, what alignment will be reached, what specific output will exist at the end of the meeting that did not exist at the beginning. A meeting whose purpose is defined as "discussing the Henderson project" is a meeting without a defined destination. A meeting whose purpose is "deciding whether to proceed with the Henderson project's Phase 2 implementation and identifying the resource requirements if yes" is a meeting from which there is something specific to walk away with.
The Agenda as a Contract
An agenda sent in advance of a meeting is not merely a list of topics — it is a contract between the meeting's organizer and its participants. It communicates what the meeting is for, what preparation is expected, how the time will be used, and implicitly, whether the meeting is likely to be worth the time it will require.
An effective agenda includes the purpose of the meeting in one sentence (not the topic, the purpose); the specific questions or decisions to be addressed; who is responsible for each agenda item; the time allocated to each item; and any preparation that participants should do before arriving. Sending this 24 hours in advance — not two minutes before the meeting — gives participants time to prepare, to flag if the agenda doesn't match their understanding of the meeting's purpose, and to contribute meaningfully rather than arriving cold.
The act of writing the agenda is itself valuable, independent of whether participants read it carefully. It forces the organizer to clarify the meeting's purpose in terms specific enough to be written down. A meeting that cannot be given a one-sentence purpose is a meeting whose organizer does not yet know what they are trying to accomplish — and a meeting that is likely, absent that clarity, to be unsatisfying for everyone in the room.
During the Meeting: The Facilitator's Job
Facilitation is the art of enabling a group to accomplish its purpose efficiently, which requires managing several competing forces simultaneously: the conversation that needs to happen versus the conversation that is happening; the person who speaks too much versus the person who says nothing; the tangent that is interesting versus the tangent that is eating the time; the decision that is being made versus the decision that should be made.
The facilitator's single most important tool is a visible record of the meeting's purpose, kept in front of the room throughout. When a conversation drifts into territory that doesn't serve the stated purpose — and this happens in every meeting — pointing to the purpose and saying "this is interesting, but let's make sure we address X before we end" is a legitimate and generally accepted redirection. Without a visible purpose, redirection feels arbitrary; with one, it feels like stewardship.
Parking lots are the facilitator's second most useful tool: a visible list (on a whiteboard or shared document) of topics that come up during the meeting that are worth addressing but don't belong in the current conversation. Parking lot items are acknowledged as real and important — not dismissed — and either addressed at the end if time permits, assigned to a follow-up conversation, or addressed asynchronously. This approach handles tangents without silencing the people who raise them.
“The facilitator's job is not to control the conversation. It is to serve the meeting's purpose while respecting the people in the room. Those two things are sometimes in tension.”— Tom Becker
The Decision Problem
The most common failure mode in organizational meetings is ending without a decision. The group discusses, explores, considers multiple angles, raises concerns, and then runs out of time — or the conversation simply decelerates without ever reaching a conclusion. Everyone leaves with a vague sense that more discussion is needed. A follow-up meeting is scheduled. The cycle continues.
This failure mode has several causes. The most common is that the decision-making authority in the room is unclear — everyone is discussing, but nobody knows who actually decides. A second common cause is that the options being considered are not clearly enough defined — the conversation circles around a problem space without ever arriving at specific, comparable alternatives. A third is that the group is trying to reach consensus when the appropriate decision mechanism is not consensus but a recommendation from one person or a vote among several.
The facilitator's job is to name these problems when they appear and propose a resolution. "It seems like we're at a point where we need to decide. I want to clarify: who in this room is the decision-maker on this question?" is a facilitation move that feels awkward and is almost always clarifying. "Let me see if I can summarize the two options we've been discussing" is another. "It's 2:45 and we agreed to end at 3:00. I want to make sure we walk away with a decision — can we take five minutes to converge?" is a third.
After the Meeting: The Follow-Through That Makes It Real
A meeting without follow-through is a conversation — potentially useful, but self-contained. The decisions made in a meeting become organizational reality only when they are documented, communicated, and acted upon. The follow-through is where most of the meeting's value is either realized or lost.
Meeting notes should be sent within two hours of the meeting ending, while memories are fresh and while the participants are still mentally proximate to the decisions made. Notes should record: the decisions made (stated clearly and specifically), the actions committed to (with owner and deadline for each), the questions or issues parked for later, and the date of the next relevant touchpoint. They should not record a detailed transcript of the discussion — nobody will read it — but a clear and actionable summary of what was decided and what happens next.
The accountability step that most meeting cultures lack is following up on action items at the next relevant gathering. If actions are assigned but never checked on, the assignment becomes performative — people learn that commitments made in meetings are not actually commitments. If actions are consistently tracked and followed up, the inverse pattern develops: people come to meetings knowing that what they agree to will be held, and they are more deliberate about what they commit to as a result.
The well-run meeting is not a pleasant conversation — it is a decision-making mechanism, an alignment instrument, and a coordination tool. Its value is not in the quality of the discussion but in the quality of the decisions produced and the reliability with which those decisions are implemented. That standard, applied consistently, is what separates the organizations where meetings are dreaded from those where they are genuinely useful.
Keep reading in Work & Productivity
The Attention Crisis at Work Nobody Wants to Fix
Knowledge workers report being in meetings or managing interruptions for more than half of every workday. The cost is staggering — and almost entirely self-inflicted.
The Email That Gets Read — and the One That Doesn't
The average professional sends dozens of emails a day. Most of them fail before the second sentence. Here is the discipline that separates communication from noise.
What Five Years of Remote Work Has Actually Taught Us
The great remote work experiment is old enough to have results. They are more complicated than either its champions or its critics predicted.