The Abilene Paradox. Why smart teams agree to decisions that ruin projects and how to stop it

False consensus in your organization – recognize and stop the Abilene paradox before bad decisions make it too late

“I didn’t like this solution from the start. I knew it wouldn’t work. But everyone else seemed so enthusiastic…so I thought maybe I was wrong. Too bad none of us said out loud what we really thought at the time.

These were the words of a friend of mine from an IT company as we discussed a project that had just collapsed spectacularly after six months of work and considerable financial investment.

What was most striking about his story was that in subsequent one-on-one conversations with members of the project team, everyone (from the project manager to the junior specialists) admitted that they had serious doubts from the beginning.

As I listened to him, I wondered how it was possible that in the world of technology we are able to implement systems that communicate effectively and without error, and at the same time teams still lack the communication architecture that allows them to freely share real information and opinions.

Why are companies’ IT systems sometimes more developed and better designed than our own interpersonal systems?

I bet most of us have been in a situation where we agreed to something even though we knew it was a bad idea. For example, new solutions, strategies, courses of action, or someone else’s decision.

If you’ve ever watched your team or people close to you nod unanimously in agreement with a proposal, only to admit later – over coffee – that they didn’t really support the idea, you’ve just discovered the Abilene Paradox. It’s a phenomenon that is potentially ruining the quality of decisions in teams and organizations around the world.

When silence becomes louder than words

The Abilene paradox was first described by Jerry B. Harvey in 1974 in the article “The Abilene Paradox: The Management of Agreement,” published in Organizational Dynamics. There, Harvey tells the story of a family reunion in Texas, during which all family members agreed to make the grueling 53-mile trip to Abilene in the summer heat, even though, as it later turned out, no one really wanted to go there. Everyone thought the others wanted the trip, and didn’t want to spoil their fun.

In our organizations, similar scenarios play out every day. The difference is that instead of a strenuous Texas trip, we go for failed projects.

From my 20 years of experience working with IT teams, I know that the vast majority of professionals have found themselves in a situation at least a few times in their careers where they have refrained from objecting to team decisions even though they saw potential problems with them.

The study, “An Exploratory Study of Employee Silence: Issues that Employees Don’t Communicate Upward and Why,” reveals that 85% of employees have concealed significant concerns from their supervisor at least once.

These problems are not unique to the business world.

Another study of nurses found that as many as 91.2% had experienced organizational silence, and 61.6% admitted that they had refrained from reporting significant problems at work.

Research by Amy Edmondson, a professor at Harvard Business School, suggests that the problem of organizational silence is particularly acute in technologically complex environments where the consequences of poor decisions can be severe. In such organizations, a lack of psychological safety (i.e., the belief that one can freely express opinions, report mistakes, and ask questions without fear of negative consequences) leads employees to refrain from voicing concerns or criticisms. This, in turn, can lead to serious project failures due to a lack of constructive team thinking and the phenomenon of false consensus.

Edmondson emphasizes that in such environments, leaders should actively promote a culture of openness, encourage the sharing of ideas and concerns, and respond constructively to issues raised. Such an approach can help avoid mistakes that result from a lack of communication, as well as foster innovation and efficiency in teams.

The Abilene Paradox is a classic case of collective concern for maintaining harmony and avoiding conflict leading to dysfunctional group dynamics. It is a special kind of decision problem. This is because it does not arise from conflict, but from mismanaged consent.

It is a situation in which a group makes decisions that are contrary to the preferences and interests of its members because each member mistakenly believes that his or her own concerns conflict with the supposed consensus of the group.

However, you should be able to distinguish between the Abilene Paradox and the related phenomenon of groupthink. In both cases, the team is unanimously moving in an undesirable direction, but the motivations are somewhat different.

In groupthink, members unconsciously censor their own views and succumb to the illusion of unanimity, often out of fear of conflict or isolation. In the Abilene Paradox, on the other hand, the problem is misreading the attitudes of others and failing to communicate openly. Everyone thinks he or she is different from the supposed majority, so they keep quiet. In other words, the Abilene Paradox is the result of pluralistic ignorance, a situation in which someone privately opposes an idea but publicly supports it, mistakenly believing that the majority approves of it.

Anatomy of team self-destruction

My friend’s example is not an isolated one. When I was mentoring a team at a tech startup some time ago, I was invited to one of the presentations where the founder was presenting a plan to implement a new feature that would “revolutionize” the user experience. The meeting, during which everyone in the startup nodded in agreement, went very smoothly. No one asked any difficult questions, and the project was approved unanimously.

Three months later, when the functionality was already partially implemented, it turned out that the team had encountered unforeseen technical difficulties, and initial tests with users showed an unenthusiastic reception. Interestingly, during the retrospective, one of the developers admitted that he had expected problems with the solution’s architecture, and the lead analyst said that in his opinion, these measures were completely pointless. After he said this, the UX designer also spoke up, admitting that she had doubts about the usability of the feature, but didn’t want to undermine the decisions of others because she thought the others agreed with her.

It turned out that almost everyone on the team had legitimate doubts, but no one was voicing them out loud, even though they had the opportunity to do so.

I find that in the technology industry, where knowledge tends to be asymmetric (specialists know more about the details than product managers), this effect can be particularly strong. If one of the team members notices that the rest of the people in the meeting are silent, he or she may think that this is mainly because he or she is the only one who disagrees with the given assumptions. Unfortunately, the truth is that everyone may be thinking the same thing at the same time, leading to a collective error.

Team members may also feel that their reaction or opinion could make someone else uncomfortable. Kim Scott, in her book “The Discerning and Forbearing Boss,” describes the concept of ruinous empathy. It occurs when too much emphasis on being nice and “not offending” others results in avoiding sincere reactions. Because of this, many teams fall into the trap of false politeness – everyone is nice to each other at the expense of the truth. If the same is true in your company, remember that the role of a leader is to encourage sincerity combined with respect. Show that it is possible to nurture relationships and challenge them at the same time, saying difficult things with care.

When apparent consensus kills innovation

“The greatest threat to innovation is not a lack of ideas, but a lack of courage to express them.”

In addition to the paradox discussed above, what makes smart, experienced professionals likely to go against their own beliefs? Research suggests several mechanisms:

1. Misperception of group preferences (conformism) – Solomon Asch’s 1951 experiments showed that people have a strong tendency to conform to majority opinions, even when they are obviously wrong. In one study, about 75% of participants agreed at least once with the wrong answer from the group, even though the correct answer was obvious.
2. Fear of social rejection – Amy Edmondson, in her research on psychological safety, reveals that the fear of being perceived as incompetent or “difficult” can effectively deter employees from voicing objections or reporting problems. This mechanism is particularly strong in organizations with a culture of conflict avoidance.
3. Pluralistic ignorance – this phenomenon is when each member of a group privately rejects a norm or belief, but publicly accepts it because he or she believes that others also accept it. This can lead to the persistence of undesirable norms. This mechanism creates a powerful feedback loop that can keep groups in a state of dysfunctional consensus.
4. Diffuse responsibility (bystander effect) – research by John Darley and Bibb Latané in 1968 showed that the more people who witness an event requiring intervention, the less likely anyone is to intervene. In one of their experiments, participants were placed in a room where smoke was introduced through ventilation to simulate an emergency situation. When the participant was alone, 75% reported a problem; when there were other people in the room who ignored the smoke, the percentage of reports dropped to 10%. Perhaps this is why we had the tragic events at Warsaw University in May 2025.

Returning to the Abilene paradox, it can be said that it preys on our best intentions – the desire to be part of a team, to respect hierarchy, the desire for harmony. But in reality, it leads to a situation where the team makes decisions that are contrary to the knowledge and experience of its members. This is especially ironic when, in your industry, the basis for success should be drawing on collective intelligence and expertise.

To avoid the trap of apparent consensus, it’s helpful to know the warning signs that suggest your team may be on a journey to Abilene. These include

• consensus reached too quickly on complex or controversial issues,
• lack of real debate or superficial discussion of important decisions,
• body language inconsistent with verbally expressed opinions (e.g., nodding while showing signs of uncertainty),
• intense backstage conversations after formal decision-making meetings,
• marked relief when someone finally expresses doubt,
• retrospective regrets when, after a decision is made, people begin to reveal that they never really supported it.

The difference between destructive and constructive conflict

An important distinction that helps to understand the dynamics of the Abilene Paradox was introduced in 1995 by Karen Jehn in her research on conflict in teams. She identified two main types of conflict:

• Relational conflict – people focus on interpersonal issues, personalities and emotions. More often than not, this is the type of conflict that is destructive to your team.
• Task (cognitive) conflict – deals with the substance of an issue, differences in ideas, interpretations of data or approaches to a problem. Properly managed, it realistically improves the quality of decisions in your team.

Helping your team members understand this difference is critical, because it helps tame fears about speaking up. When people know that challenging an idea will not be perceived as an attack on the person, it is much easier for them to speak up.

I have a simple rule. When I sit down with someone to discuss a problem, I imagine the problem lying on a table in front of us, like an object that we can touch and turn at will.

This makes it easier to understand that we are measuring ourselves against a tangible challenge, not against each other. You can also add the phrase, “I’m talking about the solution, not you,” which instantly shifts the conversation from a relational to a task-based track. This small change in optics takes the conversation off the people and, interestingly, works just as well around the dinner table when family misunderstandings need to be resolved.

Once you teach your team this approach, constructive exchanges will become the norm, and fears of task-related conflict will gradually disappear. Only then will you see how much the quality of decisions depends on your ability to consciously steer the conversation toward a dispute over ideas rather than people.

However, the data on decision making is unforgiving. Erik Larson, in his article “Don’t Fail at Decision Making Like 98% of Managers Do” reveals that after analyzing the decision-making processes of 500 managers and directors from various organizations, as many as 98% of them fail to use effective decision-making practices, leading to less effective and slower decisions.

It’s also worth looking at the study “The Liberating Role of Conflict in Group Creativity,” conducted in the US and France. The authors compared traditional brainstorming techniques with approaches that encourage debate and constructive criticism. The results showed that groups encouraged to debate generated more and more creative ideas than those using standard brainstorming principles. Charlan Jeanne Nemeth, the author of this study, emphasizes in another of her papers, “Minority Influence Theory,” that minority opinions – even if they are not accepted – stimulate more open and creative thinking in group work. People with differing opinions not only bring value through their opinions, but also encourage others to freely express their own.

I can safely say that even in IT teams where work is based on logic and facts, there is a paradoxical tendency to avoid substantive disagreement. This is largely due to the misconception that there should be no room for disagreement or discord in “rational” teams. Nothing could be further from the truth – it is the diversity of perspectives and constructive debate that leads to the best solutions, regardless of the profile of the organization.

If you’re wondering how to introduce constructive conflict into your teams without damaging relationships between team members, you can use a four-step model:

1. Establish rules of engagement. Make it clear that disagreements are about ideas, not individuals. Establish norms that protect everyone’s dignity while encouraging honest debate. In IT teams, for example, you can create a “team contract” that explicitly states: “We criticize ideas, not individuals.”
2. Separate observations from interpretations. Teach team members to distinguish between facts and interpretations. “Our sales are down 15%” is a fact. “Our product is losing appeal” is an interpretation that can be challenged. In the context of programming: “This code has high cyclomatic complexity” is an observation; “This code is badly written” is an interpretation.
3. Use techniques that structure conflict. Methods such as “devil’s advocate” (when someone is specifically designated to challenge consensus) or mini-groups set up to find gaps in proposed solutions can initiate healthy conflict. In development teams, for example, this may include rotating the role of “adversary” during planning meetings.
4. Celebrate valuable dissent. If someone steps forward and challenges the consensus of the group, and their input leads to a better decision, publicly acknowledge it.

The impact of hierarchy and leadership on the quality of decisions

I would also like to mention that the quality of decisions in your company is also influenced by hierarchy and leadership. The real responsibility of a leader is not to make all the decisions, but to create the conditions in which the best possible decisions can be made. Often this requires intentional stepping back, making room for other voices, and being willing to hear difficult truths.

Because leadership is not about being a person who knows everything. Leadership is care, responsibility and constant dialogue with those entrusted to us.

As a person living with a severe form of hemophilia, a complete lack of blood clotting, I feel this perspective particularly strongly.

I have learned that my body is constantly sending me signals that, if ignored, will have serious consequences. The same is true in our organizations, where people are constantly sending signals to their leaders. They may be weak, tentative, or indirect, but ignoring them can lead to “organizational outbursts” that are much harder to control than the original problem.

You should also keep in mind that not everyone in your organization will send even small signals. You’re bound to find a bunch of people who don’t want to talk about their insights, even indirectly. I found the answer to why this happens in the article “Why Employees Are Afraid to Speak” in which the authors describe the phenomenon of employee self-censorship.

Self-censorship is a situation in which people refrain from telling the truth because they mentally anticipate a negative reaction from their superiors. This is mainly caused by petty preliminary remarks such as: “Let’s not look for problems by force,” or the observation that only people who nod or create a climate of exaggerated optimism are rewarded, only to quickly close topics.

So if you notice that the team accepts all your ideas without constructive criticism, instead of enjoying easy leadership, you should consider it a problem.

You can solve this problem by proposing a rule that requires each team member to point out at least one potential problem with each of your ideas. You may be met with awkward silence at first, but when someone finally dares to speak up, and you don’t react negatively, but instead thank them for their input and engage the team in discussion, you will raise the morale of the team members. David Rock, in his book “Your Brain at Work, went a step further and wrote that when leaders express gratitude for constructive criticism, it activates circuits in team members’ brains that, over time, will transform the culture into one that values honesty over superficial harmony.

It’s also worth remembering that in organizations where both leaders and teams are accountable for delivering results quickly, there can be a temptation to stifle discussion and label it a “waste of time.

Remember, however, that short-term gain (no discussion at the meeting) means long-term loss: mistakes come to light later and cost much more time and money to fix than if they had been caught in the first place. In addition, and just as important, you lose access to valuable knowledge.

A model for building a culture of open and authentic communication in the decision-making process

If you want to transform your organization’s culture and reduce the likelihood of falling into the Abilene Paradox trap, you can use a five-step model:

1. Real Values Audit. In companies, it’s not about what we say on billboards, but about what behaviors are actually desired in the day-to-day life of the organization. Consider whether those who express constructive dissent are valued or marginalized.
2. Model desired behavior by leaders. It is the leaders who must actively seek dissent, publicly admit mistakes and demonstrate openness to different perspectives. Without deepened self-awareness and communication skills, this can be difficult.
3. Change decision-making processes. Introduce formal mechanisms that force consideration of alternative perspectives, such as a mandatory “critical analysis” phase before a final decision is made.
4. Invest in team communication skills. Developing team members’ social skills, such as techniques for effectively expressing dissent or constructively receiving criticism, is key.
5. Change your reward and recognition system. Systematically recognize individuals who have had the courage to challenge the status quo and speak up.

Finally, I would like to add that I believe that organizations that learn to manage compliance in an effective and predictable way will gain a disproportionate advantage.

They will make better decisions, implement more innovative projects, and attract and retain the best talent because of their culture and openness.