Abilene Paradox

The original story: a family on a hot Sunday afternoon ends up driving 53 miles in a car with no air conditioning to eat average food in Abilene, Texas. On the way home, they discover that nobody actually wanted to go. Each person had agreed because they assumed the others wanted to, and going along with it felt more polite than objecting.

The product version of this happens in roadmap reviews, steering committees, and 'alignment' meetings constantly. A decision emerges that nobody in the room actually thinks is a good idea, but everyone assumes everyone else wants it, and pushing back feels like being difficult.

The mechanism is social, not strategic. People read others' silence as agreement. Objecting feels costly. And the resulting group decision ends up worse than any individual would have chosen alone.

The defence is structural: anonymous pre-reads, written positions submitted before the meeting, an explicit 'what are we worried about?' slot on the agenda, and a senior person whose known role is to ask 'wait — does anyone actually want this?'

A product review ends with the team agreeing to add three new features to the Q3 scope.

After the meeting, the PM has 1:1 hallway conversations with four attendees over the next two days. Every single one of them says a version of 'I didn't really think we should add those, but it seemed like everyone else wanted to.' Each one had seen the others nodding along and inferred consensus.

The room collectively committed to a scope increase that nobody in the room individually supported, and the engineering team now has to ship it on an unchanged deadline.

This is the Abilene Paradox in its exact form, and it happens in some version of it most weeks in most companies.

Naming it out loud — 'before we commit, let's do a quick round where everyone says what they'd change' — breaks the spell roughly 70% of the time, because the first person who admits reservations gives everyone else permission to.