The Abilene Paradox

The meeting ends.

Everyone agrees.

The initiative moves forward.

Three weeks later, private conversations reveal something strange:

Several people had serious doubts from the beginning.

So why didn’t anyone say anything?

Organizational theorist Jerry B. Harvey described this phenomenon as the:

Abilene Paradox (Jerry B. Harvey, 1974)

The paradox occurs when:

A group collectively chooses an action that contradicts the private preferences of many, sometimes even all of its members.

The problem isn’t necessarily disagreement.

It’s the failure to manage agreement correctly.

People incorrectly assume others support a decision and suppress their own reservations to avoid:

• appearing difficult

• disrupting consensus

• challenging authority

• creating interpersonal conflict

The result?

Everyone agrees to something because they believe everyone else wants it.

Organizations often treat visible agreement as evidence of genuine consensus.

But silence is ambiguous.

Someone who says nothing may:

• genuinely agree

• have reservations

• believe disagreement is unwelcome

• assume everyone else knows something they don’t

That creates a dangerous feedback loop:

Perceived consensus → silence → stronger perceived consensus → collective commitment

The organization can therefore manufacture its own agreement.

Before interpreting consensus as genuine, ask:

Or did people react after hearing senior voices?

What concerns would people raise if disagreement carried no social cost?

Absence of opposition is not necessarily support.

Does collective agreement match individual judgment?

This shifts leadership thinking from:

“Does everyone agree?”

to:

“What does everyone actually believe?”

A famous corporate example is the Challenger Space Shuttle launch decision in 1986.

Engineers at contractor Morton Thiokol had serious concerns about how the shuttle’s O-rings would perform in unusually cold temperatures.

Before the launch, Thiokol engineers initially recommended not launching.

During discussions with NASA, however, organizational and managerial pressure intensified. Thiokol management ultimately reversed its recommendation, and Challenger was cleared for launch.

The shuttle broke apart shortly after liftoff.

The case is more complex than the Abilene Paradox alone, but it demonstrates an important organizational lesson:

information can exist inside an organization without being adequately represented in the final decision.

Through our practical lens:

1. Were concerns present?
Yes — engineers had explicitly raised technical concerns.

2. Were objections able to survive the decision process?
Ultimately, no. The recommendation changed under organizational pressure.

3. Did the final decision accurately represent all available judgment?
No. Important technical reservations were not reflected in the final launch decision.

4. What was the leadership failure?
The process failed to preserve and appropriately weight dissenting information before commitment.

Strong leadership isn’t about creating rooms where everyone agrees.

It’s about creating decision processes where:

important disagreement becomes visible before commitment becomes expensive.

Next time a major decision receives unusually easy consensus, ask:

Do we genuinely agree or have we simply failed to disagree?