Meetings That Produce Nothing

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?

Edward de Bono: separate the modes of thinking instead of mixing them

De Bono's Six Thinking Hats, developed across his published work including Six Thinking Hats (1985), argues that most meetings fail because people argue from different modes simultaneously, one person raising risks while another pitches opportunities while a third just wants a decision, with nobody actually building on anyone else's point. Separating the modes, one at a time, for the whole group, produces far more usable output than unstructured debate.

Applied: Before opening a meeting to general discussion, run two explicit rounds: two minutes where everyone can only raise risks and concerns, then two minutes where everyone can only raise opportunities and upsides. No cross-talk between rounds. The group ends up with a genuinely fuller picture than the usual pattern of one person's risk being immediately countered by another person's optimism before either point is fully on the table.

The mechanism works because interruption is what kills most meeting contributions before they're fully formed. A risk raised and immediately countered never gets explored; it just gets argued down. Structuring the rounds so no countering is allowed yet means ideas survive long enough to actually be considered.

Patrick Lencioni: the real dysfunction is the avoidance of 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?

What can you actually try this week?

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.

Why it works: a written structure for the rounds makes it much easier to actually hold the no-crosstalk rule in the room than trying to improvise it on the fly.

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 hats round. 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. De Bono's full Six Thinking Hats and lateral thinking framework lives in the Educator category. For running a structured pre-read before the meeting even starts, Meeting Pre-Read is a $39 tool built for exactly that.

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.