Quick take: Most meetings fail not because people are disorganized, but because the meeting was called before anyone was clear on what decision needed to be made or what outcome would make the time worthwhile. The fix isn’t better facilitation — it’s better design before the calendar invite goes out.
There’s a calculation that almost nobody does before scheduling a meeting: multiply the number of attendees by their average hourly cost, then multiply by the meeting duration. A 90-minute strategy meeting with 8 senior employees can easily represent $3,000–$5,000 in salary cost alone, before you factor in the opportunity cost of whatever those people aren’t doing instead. Most meetings don’t get anywhere near that value. Many produce none at all.
Microsoft’s research on workplace patterns found that meeting time nearly tripled after the shift to remote and hybrid work, with the average employee spending roughly 57% of their work time in meetings or on email. The meetings multiplied; the value per meeting didn’t. Something went badly wrong, and most organizations are still fumbling toward a fix.
The Real Problem With Meetings Isn’t What You Think
The conventional wisdom about fixing meetings focuses on execution: keep them shorter, start them on time, send agendas, don’t let people monologue. These are all fine suggestions, and none of them address the root problem. The root problem is that most meetings are called to avoid making a decision, not to make one.
When an individual or team isn’t sure what to do, convening a meeting feels like progress. It distributes the uncertainty, creates the appearance of collaboration, and defers the discomfort of being the person who decided. Organizations that have chronic meeting problems usually have chronic decision-clarity problems — and until the second is fixed, the first won’t get better no matter how many meeting guidelines you publish.
Fact: Research from MIT Sloan found that the number one cause of ineffective meetings is the lack of a clear decision to be made. When the purpose of a meeting is vague — “align on the project” or “discuss the strategy” — attendees have no shared frame for when the meeting is done or what success looks like.
Design Before You Schedule
The most effective thing you can do to improve meeting quality happens before anyone opens their calendar. It requires answering three questions honestly: What specific decision or output does this meeting need to produce? Who actually needs to be in the room (or on the call) to produce it? And could this be resolved faster and better through a document, a quick Slack thread, or an async video?
The third question deserves more attention than it typically gets. Status updates, information sharing, and one-directional briefings are almost always better handled asynchronously — through a shared doc, a recorded walkthrough, or a written summary. Pulling eight people into a room so one person can share updates they could have written in fifteen minutes is a spectacular misuse of collective time and attention.
Tip: Before scheduling any meeting, write one sentence that completes this prompt: “This meeting is done when we have _____.” If you can’t complete it clearly, you’re not ready to schedule the meeting yet. Send a document instead and ask for asynchronous input.
The Two Types of Meeting Worth Having
Decision Meetings
A specific decision needs to be made, options have been pre-shared in writing, the decision-maker is in the room, and the meeting ends with a clear choice and documented owner. These are worth having and worth protecting. They should be as short as the decision requires and no longer.
Connection Meetings
Team rituals — weekly standups, retrospectives, one-on-ones — that build the relational infrastructure work actually runs on. These matter even when no decision is made. The mistake is treating them like decision meetings and adding agenda items they can’t carry.
The Pre-Read: The Most Underused Meeting Tool
Amazon’s famous “no PowerPoint” policy replaced slide decks with written memos that attendees read silently at the start of every meeting. The reasoning was elegant: presentations compress nuance and encourage passive reception, while written documents force precise thinking from the author and active engagement from the readers. The first 10–15 minutes of Amazon meetings is people reading, in silence, before the discussion begins.
Most organizations don’t need to go that far. But circulating a written pre-read — a one-page summary of the situation, the options, and your recommended direction — 24 hours before a meeting changes the conversation dramatically. People arrive with opinions formed, context already absorbed, and the meeting can spend its time on the high-value work of debate and decision rather than the low-value work of bringing everyone up to speed.
Insight: When people receive meeting materials in advance and come prepared, meeting duration typically drops by 30–50% with no loss in quality of outcome. The preparation time is recovered many times over in the meeting itself.
The Invitation List Problem
Meeting bloat is frequently an invitation problem. People get added to meetings defensively — to avoid them feeling left out, to cover political bases, to “keep them in the loop.” The result is meetings where half the room has nothing to contribute and no real stake in the outcome, but everyone still speaks because they feel obligated to justify their presence.
A useful framework: for any decision meeting, the invite list should include only people who have information essential to the decision, or who have authority over it. Everyone else can receive the decision outcome in a brief written summary. Being excluded from a meeting and informed of the output is not a slight — it’s a gift of time. Treating it that way, and communicating it that way, is part of building a healthier meeting culture.
“The best meeting you ever attend is often the one you weren’t invited to — because someone trusted the people in the room and gave you back the hour.”
Running the Meeting Itself
Assuming the design work has been done — clear purpose, right people, pre-read circulated — the facilitation becomes much more straightforward. The facilitator’s job is to keep the conversation focused on the decision, draw out quieter voices before louder ones dominate, name when the group is going in circles, and know when enough has been said to make the call.
The hardest facilitation skill is ending the meeting. Not at the scheduled time — that’s the easy part — but at the natural decision point, even if time remains. Meetings don’t end when the clock runs out; they end when the purpose is met. A 30-minute meeting that resolves in 18 minutes should end at 18 minutes. This sounds obvious and almost never happens in practice.
Warning: Parkinsonian expansion is real in meeting rooms: discussion expands to fill the time available. Scheduling 60 minutes for a decision that takes 30 doesn’t make the decision better — it just adds 30 minutes of tangents, rehashing, and diminishing-returns conversation. Schedule tight and end early.
End every meeting with explicit documentation of what was decided, who owns what, and by when. This takes two minutes and eliminates the enormous amount of energy spent after meetings on “wait, what did we actually decide?” A brief, shared summary — even just in the meeting chat — is the difference between a meeting that generated momentum and a meeting that generated a follow-up meeting.
The Short Version
- Most meetings fail because they’re called to avoid decisions, not to make them — fix decision clarity first
- Before scheduling, complete this sentence: “This meeting is done when we have ___” — if you can’t, send a doc instead
- Pre-read documents circulated 24 hours in advance cut meeting time by 30-50% without reducing quality
- End every meeting with a documented decision, owner, and deadline — two minutes that prevent three follow-up meetings
meeting facilitation, decision-making, async communication, agenda setting, time management, organizational efficiency, remote meetings, meeting culture
Frequently Asked Questions
How do I get my team to actually read pre-reads before meetings?
Make the pre-read worth reading — tight, specific, and actionable, not a 20-page deck. Then hold the norm: start the meeting by asking what people thought of the pre-read, not by summarizing it. If people know they’ll be expected to engage with the content rather than just absorbing a repeat presentation, compliance increases rapidly.
What do I do when someone dominates every meeting?
Address it structurally first, before individually. Round-robin contributions, written input before verbal discussion, and breaking into smaller groups all reduce dominance without requiring a difficult confrontation. If structural fixes don’t work, address it directly with the person in a private one-on-one — not publicly during the meeting.
How long should a typical meeting be?
Schedule to the minimum necessary, not to conventional blocks. Most decisions that take an hour could be made in 30 minutes with proper preparation. The 60-minute default meeting is a calendar artifact, not a reflection of how long things actually take. Try 25-minute and 50-minute defaults to build in transition time and respect cognitive limits.
Should every meeting have a designated facilitator?
For meetings of four or more people on non-trivial decisions, yes. The facilitator doesn’t have to be the most senior person — often it’s better if they’re not, since senior leaders can anchor discussion rather than open it. The facilitator’s job is to protect the process, not to drive the conclusion.
How do I push back on being invited to unnecessary meetings?
Reply with a question rather than a refusal: “What would you like my contribution to be in this meeting?” or “Would it work for me to review the output afterwards rather than attend?” This surfaces the real reason for the invitation and often reveals that your presence wasn’t actually necessary — without creating conflict.