Abilene Paradox

The Abilene Paradox comes from a 1974 article by Jerry B. Harvey. The setup is simple: a group reaches a collective decision that nobody actually wanted. Nobody objects. Nobody raises a hand. Everyone assumes the group has spoken, and quietly goes along with something they privately disagree with.

Harvey named it after a real trip to Abilene, Texas, where a family drove 50 miles in summer heat to a restaurant nobody enjoyed, and discovered afterward that none of them had wanted to go in the first place. Each person had agreed because they thought everyone else wanted to.

That’s the paradox. The group “agrees” on something no individual in the group would have chosen alone.

How it differs from groupthink

The two get conflated, but they’re different. In groupthink, members genuinely convince themselves the group’s decision is correct. In the Abilene Paradox, members know they disagree but don’t say so. The outcome can look the same from the outside. The internal experience is opposite.

Both are problems worth solving. A team can fall into either trap, and managing for one doesn’t automatically fix the other.

Why it happens

The short answer: people don’t want to be the one who derails things.

Nobody wants to create friction. Nobody wants to look difficult, pessimistic, or like they’re blocking the group’s momentum. So when someone floats an idea and nobody objects, silence gets interpreted as agreement. It isn’t. It’s just silence.

Harvey’s observation was that the fear isn’t really about the decision itself. It’s social. People are protecting their standing in the group, or they genuinely believe their private hesitation is the problem, that everyone else must see something they don’t.

How to prevent it

The fix is structural, not motivational. Telling people to “speak up” doesn’t work if the environment punishes speaking up.

A few things that actually help:

Give everyone a turn before the group reacts. If people state their view individually before a group discussion starts, they’re less likely to anchor on what the most senior person said first.

Separate feedback from identity. Anonymous input, written responses before a meeting, or dedicated devil’s advocate roles give people a way to register disagreement without it feeling like a personal confrontation.

Ask explicitly whether anyone has reservations, not just whether everyone agrees. The questions sound similar. They produce very different responses.

Follow up after decisions get implemented. If people felt pressure to agree with something that didn’t work, they’ll often say so after the fact. That feedback is worth collecting, and it tells you whether the decision process is creating false consensus.

Slow things down when a decision comes together too easily. Unanimous quick agreement on a complex issue is a flag, not a win.

The underlying point

Good teams don’t require everyone to agree. They require everyone to actually say what they think. Those are very different things, and conflating them is exactly how a group ends up in Abilene.

If you’re the manager: your job isn’t to build harmony. It’s to build the conditions where people will tell you what they actually think, including when they think you’re wrong.