A drive nobody wanted
In the summer of 1974, a management professor named Jerry B. Harvey told a small story that has outlived most of the theories of its decade. His family was sitting on a porch in Coleman, Texas, playing dominoes in the heat, when someone suggested driving fifty-three miles to Abilene for dinner. Nobody especially wanted to go. But each person, assuming everyone else was keen, agreed. They drove two hours round trip through dust and heat, ate a bad meal, and came home cranky. Only afterward, comparing notes, did they realize the truth: not one of them had wanted to make the trip. They had gone to Abilene to avoid the imagined disappointment of people who didn't want to go either.
Harvey called this the Abilene paradox, and once you have a name for it, you start seeing it everywhere—most reliably in meetings. A team commits to a launch date, a vendor, a reorg, a feature nobody is excited about, and the decision sails through without a single objection. Months later, in hallways and one-on-ones, the same people who nodded in the room admit they had doubts the whole time. The project failed not because the team disagreed, but because it couldn't manage its agreement.
Agreement is not the same as consensus
We tend to treat a quiet, frictionless meeting as a success. No arguments, no raised voices, everyone aligned—what could be wrong? Harvey's insight was that the inability to manage agreement is a more common and more dangerous failure than the inability to manage conflict. Teams are well-drilled in handling disagreement: they have facilitators, voting, debate. Almost no one is trained to detect the opposite problem, where the visible agreement is hollow.
The Abilene paradox is often confused with groupthink, but they are mechanically different. In groupthink, as Irving Janis described it, people genuinely talk themselves into a shared belief; the desire for cohesion warps their actual judgment. In the Abilene paradox, no one's private judgment changes at all. Each person still thinks the trip to Abilene is a bad idea. The failure is purely in communication—everyone privately disagrees and publicly consents. That distinction matters, because the fixes are different. You can't argue a team out of the Abilene paradox with better evidence; everyone already has the doubt. You have to make the doubt sayable.
The quiet engine: pluralistic ignorance
The psychological mechanism underneath the paradox has a name of its own: pluralistic ignorance. It's the situation where most members of a group privately reject a position but assume, incorrectly, that most others accept it. Each person uses everyone else's silence as evidence, and since everyone is silent for the same reason, the whole group ends up policing a norm that none of them actually holds.
The classic demonstration is a college classroom: a professor finishes a baffling lecture and asks if there are any questions. No one raises a hand. Every student reasons, "I'm the only one lost—everyone else seems fine, so I'll stay quiet rather than look foolish." The room is full of confused people each convinced of their lonely confusion. Meetings run on exactly this fuel. You glance around the table, see calm faces, and read those faces as endorsement. But a neutral face is not data. It might be someone reading yours the same way.
This is compounded by what psychologists call the illusion of transparency—our tendency to overestimate how visible our inner states are to others. You feel your skepticism so vividly that it seems obvious, so when no one acknowledges it, you conclude they must not share it. In reality your doubt was never visible at all. Three or four people can leave a room each believing they were the lone dissenter, when they were quietly a majority.
Why smart people drive to Abilene
It would be easy to chalk this up to cowardice, but the forces are subtler and more reasonable than that. Harvey pointed to a kind of action anxiety: a real fear of the consequences of speaking up—of being seen as not a team player, of derailing momentum, of being the one who made the meeting longer. Beneath that sits a deeper fear of separation, the very old human worry that breaking from the group will get you pushed out of it. Voicing a lone objection feels, at some pre-rational level, like risking exile.
There is also a self-fulfilling logic to it. Because you expect negative consequences for dissenting, you stay quiet, the bad decision proceeds, and you feel the private satisfaction of having been right—"I knew this would happen"—which quietly reinforces the belief that speaking up wouldn't have helped anyway. The silence justifies itself. Each trip to Abilene makes the next one likelier, because the team accumulates evidence that agreement is safe and dissent is dangerous, when the opposite was true the entire time.
Making the doubt sayable
The useful thing about understanding the mechanism is that the interventions become obvious, and most of them are small. The goal is never to manufacture conflict for its own sake. It's to lower the cost of honesty enough that private reservations make it into the room before the decision hardens.
The most direct tool is to ask the question that breaks pluralistic ignorance: not "Does everyone agree?" but "What would have to be true for this to be the wrong call?" The first question invites the nods that doom the team. The second gives everyone permission to voice a concern without owning it as a personal objection—they're just answering a hypothetical, which is far less socially expensive.
It also helps to separate the moment of generating opinions from the moment of sharing them. If you ask people to write down their honest read—on a scale, in a sentence—before anyone speaks, you defeat the cascade where the first confident voice sets the room's apparent consensus. Anonymous or simultaneous input works because pluralistic ignorance depends on people reading the silence in real time; remove the live audience and the doubt has nowhere to hide. Some teams formalize this by assigning a rotating devil's advocate, so that disagreement becomes a role someone is expected to play rather than a character flaw they're choosing to reveal.
The most important move, though, is cultural and slow: leaders have to visibly reward the person who says "I'm not sure about this." The single fastest way to fill a team with Abilene trips is to punish, even subtly, the first person who breaks ranks. The single fastest way to prevent them is to thank that person out loud, especially when they turn out to be right.
What the bad dinner was really about
What makes Harvey's story endure is that everyone involved was reasonable, considerate, and acting in good faith. That's the unsettling part. The drive to Abilene wasn't caused by a fool or a tyrant in the group. It was caused by four thoughtful people each trying, generously, to give the others what they imagined the others wanted. Good intentions, pointed in the dark, drove straight to a bad dinner.
Most teams don't have a conflict problem. They have an agreement problem, and they mistake the symptom—a smooth, quiet meeting—for health. The next time a decision passes without a single objection, it's worth treating that silence not as a green light but as a question: did everyone agree, or did everyone just assume?
That assumption is exactly what tends to evaporate the moment a meeting ends and there's no record of who actually said what, or what reservations went unspoken. This is the small problem meetingmortem is built to chip at—capturing not just the decision a meeting reached but the doubts that surrounded it, so the quiet "I wasn't sure about this" has somewhere to land before it becomes next quarter's post-mortem. If your team has driven to Abilene more than once, it might be worth seeing your meetings written down honestly: meetingmortem.lumenlabs.works.