Why Meetings Fail (and What a Good One Requires)
The meeting paradox
The meeting is the most-used communication tool in organizations — and the most criticized. Researcher Steven Rogelberg (University of North Carolina), author of The Surprising Science of Meetings, finds from his surveys that a large share of meeting time is judged ineffective by participants themselves, and that managers spend a considerable part of their week in meetings. The cost is not only time: it is wasted energy, attention and motivation.
Yet the problem is not the meeting itself, but the communication that takes place in it: vague objective, monopolized airtime, decisions that aren't really decisions. A successful meeting is, above all, a structured act of communication.
"A bad meeting doesn't cost one hour: it costs one hour multiplied by the number of attendees." — a principle Rogelberg stresses when urging us to compute the real cost.
The five most common causes of failure
| Cause | Typical symptom | Consequence |
|---|---|---|
| No objective | "Let's meet to check in" | Nobody knows when it's done |
| Too many people | 12 attendees, 3 speak | Dilution, passivity |
| Monopolized airtime | 1-2 voices dominate | Lost ideas, disengagement |
| No decision | "Let's revisit this" | Recurring meetings |
| No follow-up | No action log | Nothing happens afterward |
Parkinson's Law applies to meetings
Cyril Northcote Parkinson stated in 1955 that "work expands to fill the time available for its completion." Meetings are no exception: block an hour and it will take an hour, even if twenty minutes would have done. Hence a first communication rule: announcing a short time and a precise objective usefully compresses the discussion.
Meet — but for what?
Before any meeting, one question decides everything: what type of meeting is this? Because you don't communicate the same way depending on the goal.
- Inform / align: convey top-down information (often replaceable by a written message).
- Decide: choose between options.
- Solve / produce: generate ideas, build together.
- Connect: strengthen team cohesion.
Confusing these types is the leading source of misunderstanding. An information meeting treated as a debate drags on; a decision meeting treated as mere information decides nothing.
Group size: the "two-pizza" rule
At Amazon, Jeff Bezos popularized the two-pizza rule: a team (or a meeting) should never gather more people than two pizzas can feed — about 5 to 8 participants. Beyond that, communication degrades: speaking turns become rare, responsibility dilutes (the social loafing effect), and consensus becomes unreachable.
Rule of thumb: if someone has no clear reason to speak or decide, they probably don't need to be in the room. They can receive the minutes.
Say / don't say (in the invitation)
| Don't say | Say |
|---|---|
| "Project meeting — 1 hr" | "Decide the v1 scope — 30 min" |
| "Team check-in" | "Align on 3 priorities for the week" |
| "Brainstorm" | "Produce 10 title ideas, then keep 3" |
Practical exercise
Take the next meeting you organize. Before sending it, write in a single sentence: "By the end of this meeting, we will have [decided / produced / aligned on] ___." If you can't, the meeting has no purpose yet — postpone it or replace it with a message.
Summary
- The meeting problem is not the meeting, but the poorly structured communication within it.
- Five recurring failure causes: no objective, too many people, monopolized airtime, no decision, no follow-up.
- Parkinson's Law: a short time and a precise goal usefully compress the discussion.
- Identifying the meeting type (inform, decide, produce, connect) drives the communication mode.
- The two-pizza rule (Bezos): 5 to 8 people maximum to preserve quality of exchange.