Skip to content
Situations

Meetings That Produce Nothing

Why most meetings end with everyone agreeing and nothing changing, and three documented approaches, from Bezos, Lencioni, and Parker, for meetings that actually decide something.

By Gareth Hoyle·Updated 11 October 2026·8 min read

Everyone nods. Everyone agrees the plan sounds good. The meeting ends on time, feels productive, and three weeks later nothing has actually moved, because nobody disagreed with anything out loud and nobody was assigned to do anything specific. The meeting wasn't badly run. It just wasn't designed to produce a decision in the first place.

Why does the generic advice about meetings fail?

"Have an agenda" is the most repeated meeting advice and the least sufficient. An agenda lists topics; it doesn't force disagreement into the open, assign ownership, or distinguish between a meeting meant to inform and one meant to decide. A meeting can follow a perfect agenda and still produce nothing, because the agenda never specified what a good outcome looked like.

Generic AI prompting has the same gap. Ask an assistant to "write an agenda for our strategy meeting" and it will produce a clean list of bullet points with time allocations, structurally sound and functionally useless, because it has no visibility into which topics on that list are actually contested and which are settled. The format looks organized. The actual disagreement, the thing a meeting exists to surface, never gets built into the design.

The underlying failure is treating a meeting as a container for information transfer when its actual job, in most of the cases that justify gathering people in real time at all, is to surface and resolve disagreement that doesn't survive an email thread. A list of topics with time slots next to them says nothing about which of those topics has three people quietly holding three different opinions.

What do the documented approaches say to do instead?

Jeff Bezos: why start with a memo everyone reads?

Colin Bryar and Bill Carr's Working Backwards (2021) documents how Amazon's senior team replaced slide presentations with written narrative memos, up to six pages, read in silence at the start of the meeting. Discussion only begins once everyone has finished. The claim behind it is that full sentences force the author to show the reasoning, and that a silent read gives every person the same information before the loudest voice sets the frame.

Applied: For a meeting meant to decide something, replace the presentation with a one- or two-page written narrative that states the decision, the options, and the author's recommendation. Open the meeting with ten minutes of silent reading. Start the discussion only when the last person has finished.

The mechanism works because most meeting time is spent catching people up, and most of the catching up is done by the most confident speaker. A silent read removes the head start. Everyone arrives at the discussion having formed their own view, which is where disagreement has a chance to show up.

Patrick Lencioni: what happens when a team avoids productive conflict?

Lencioni's The Five Dysfunctions of a Team (2002) identifies absence of trust leading to fear of conflict as the foundational failure beneath most unproductive team meetings. Without visible disagreement, a team defaults to artificial harmony, where everyone nods along in the room and the real disagreement surfaces later, privately, after the decision is supposedly made.

Applied: If a meeting ends with unanimous, immediate agreement on something genuinely consequential, that's a signal to probe rather than celebrate. Ask directly: "who in this room sees this differently, even slightly?" Naming the expectation that disagreement is normal, even welcome, does more to surface it than any amount of encouraging body language.

The deeper issue Lencioni points to is that artificial harmony is often mistaken for a healthy team culture, when it's actually evidence that the real decision-making is happening somewhere other than the meeting, in side conversations, in hallway chats, in private messages sent after the fact. A meeting with no visible friction is rarely a meeting where the hard thinking happened in the room.

Priya Parker: define what a good outcome looks like before the meeting starts

Parker's The Art of Gathering (2018) argues that most meetings fail at the design stage, before anyone enters the room, because the actual purpose was never specified beyond a vague category like "sync" or "check-in." A gathering without a specific, stated purpose defaults to whatever the most senior or most vocal person wants it to be about.

Applied: Before sending the invite, write one sentence: "this meeting succeeds if we leave having decided X" or "this meeting succeeds if everyone understands Y well enough to act on it alone." If that sentence can't be written, the meeting likely doesn't need to happen, or needs to be redesigned until it can.

Parker's broader point is that the purpose should shape everything downstream of it, who's invited, how long it runs, even the physical or virtual layout, rather than being an afterthought squeezed into the first line of an agenda template. A meeting designed backward from a one-sentence purpose tends to look structurally different from a meeting that starts from a recurring calendar slot and works forward to find something to fill it with.

Where does each approach fit best?

ApproachFromWhen it fitsWatch out for
Silent-read narrativeJeff Bezos, as documented in Working BackwardsPresentations dominate the room and the reasoning behind them never gets examinedNeeds an author willing to write the argument out in full sentences, and a room willing to wait for the slowest reader
Naming the absence of conflictPatrick Lencioni, The Five Dysfunctions of a TeamDecisions get unanimous, fast agreement that later turns out to be hollowOnly works if the person asking has enough trust in the room for an honest answer
Purpose-first designPriya Parker, The Art of GatheringThe meeting's actual goal was never clearly stated before it was scheduledRequires discipline to cancel or redesign meetings that fail this test, not just note the problem

What can you actually try this week?

1. The purpose test
"Here's the meeting I'm about to schedule: [describe it]. Help me write one sentence defining what success looks like, either a specific decision made or a specific understanding reached, and tell me honestly whether the meeting as currently planned is actually built to produce that outcome."

Why it works: forcing a single-sentence success definition before the invite goes out catches the most common failure, a meeting with no clear purpose, before it ever happens.

2. The silent-read narrative
"Here's the decision for an upcoming meeting: [describe it]. Turn my notes into a one-page narrative in full sentences, with no bullet points: the decision being asked for, the options considered, my recommendation, and the strongest argument against it. Then suggest a ten-minute silent-read opening and the first question to ask once everyone has finished."

Why it works: a written narrative exposes weak reasoning that slides let you skip, and the silent read puts the whole room on the same page before discussion starts.

3. The hollow-agreement probe
"We just reached what looked like unanimous, fast agreement on this: [describe the decision]. Give me two or three specific, pointed questions I could ask the group to test whether this is genuine agreement or avoidance of disagreement."

Why it works: having specific questions ready, rather than a generic "does anyone disagree," makes it meaningfully harder for quiet avoidance to pass as consensus.

What won't this fix on its own?

These three approaches redesign the structure a meeting runs on. None of them can force a room to actually use that structure honestly if the underlying trust isn't there, a team that's genuinely afraid to disagree with a senior voice in the room will find ways to perform agreement even inside a well-designed silent-read meeting. The structure helps. It doesn't substitute for the harder, slower work of building a room where disagreement is actually safe.

Lencioni and Parker both sit in the People & Culture category alongside Kim Scott and Amy Edmondson, the fuller bench for team dynamics work like this. Bezos sits in the Tech Visionary category, where his full framework lives. For running a structured pre-read before the meeting even starts, Meeting Pre-Read is a $39 tool built for exactly that.

To build the next one properly, Meeting Agenda is a $12.99 Playbook that starts from the decision the meeting exists to make.

All the copy-paste prompts from this guide, and the rest of the Situations series, live at /prompts too, free to copy without reading the guide first.

FAQ

Frequently asked questions

Is the problem usually the meeting format or the people in it?

Usually the format, or more precisely the absence of one. Most unproductive meetings have no explicit structure for how disagreement surfaces or how a decision gets made, so they default to whoever talks most or whoever outranks the room. Fixing the format changes the outcome far more reliably than trying to change how individual people behave in it.

Can't I just cancel most meetings and replace them with messages?

For status updates, usually yes. For anything requiring a real decision between people who see the problem differently, an asynchronous message tends to produce surface-level agreement without surfacing the actual disagreement, which then resurfaces later as confusion or rework. The frameworks here are for that second category, not for meetings that shouldn't exist at all.

What's the single biggest fix if I can only make one change?

Name the actual purpose of the meeting before it starts, and make sure everyone in the room knows what decision or output it's supposed to produce. Priya Parker's observation is that most meetings fail before they begin, because nobody actually defined what a good outcome would look like.

Do we need to write a six-page memo to use the Bezos approach?

No. The mechanism is that everyone reads the same written argument in silence before anyone speaks, so the discussion starts from shared understanding instead of whoever presents best. A one-page narrative works, provided it is written in full sentences and states the decision being asked for. Slide bullets let weak reasoning hide, which is the problem the written form is meant to remove.

How do you tell if a team's silence in meetings is agreement or avoidance?

Lencioni's diagnostic is to ask a pointed, specific question that requires a real opinion, not a yes-or-no, and watch whether the room's body language changes before anyone speaks. Genuine agreement tends to come quickly and casually. Avoidance tends to come after a pause, phrased cautiously, deferring to whoever speaks first.

Can AI run the meeting for me?

No. It can help you design the structure in advance, the agenda, the explicit purpose, the specific questions to force real positions into the open, but it has no presence in the room and can't read what's actually happening between people in real time. The design is where AI helps. The facilitation still has to be done by a person.

Written by Gareth Hoyle. Last updated 11 October 2026. Part of the authority.md guides library.

Keep reading

More guides.