Why Did Your Whole Team Agree to a Plan Nobody Wanted?


landscape photography of empty road

When was the last time your team pushed back on something you proposed, in the room, before it was decided? If you have to think hard about the answer, the quiet is not a sign that everyone agrees. More often it is a sign that several people disagree and each one assumes they are alone.

That failure has a name, and it is one of the least understood problems in leadership. It is not conflict. It is agreement that nobody actually holds. The questions below are the ones I get most often when I describe it to managers, answered as plainly as I can.

What is the Abilene paradox, exactly?

In 1974 Jerry Harvey, a management professor at George Washington University, published an article in Organizational Dynamics called “The Abilene Paradox: The Management of Agreement.” He opened it with a story from his own family.

They were sitting on a porch in Coleman, Texas, on a hot afternoon, playing dominoes. His father-in-law suggested driving about 50 miles to Abilene for dinner. His wife said it sounded great. Harvey had doubts, but assumed he was the odd one out, so he said it sounded good to him and he hoped her mother wanted to go. His mother-in-law said of course she wanted to go. They drove through the heat and dust, ate a poor meal at a cafeteria, and got home four hours later, worn out.

Then the truth came out. The mother-in-law said she would rather have stayed home and only went because everyone else seemed keen. Harvey said he went to keep the others happy. His wife said she went to keep him happy. The father-in-law said he only suggested it because he thought the others might be bored. Four people took a trip that not one of them wanted.

Harvey’s point was that organizations do this constantly, and they misdiagnose it. Leaders are trained to manage conflict. The harder problem, he argued, is managing agreement: a group publicly endorsing a course of action that most of its members privately believe is wrong.

Isn’t that just groupthink with a better story?

No, and the difference matters because the fixes are different.

In groupthink, people come to actually believe the group’s position. Cohesion and pressure bend their private judgment until the doubts fade. In the Abilene paradox, the private judgment stays intact. Each person still thinks the plan is a bad idea. What breaks is their read on everyone else. They misjudge what the room believes, and they act on the misjudgment.

Psychologists call that misread pluralistic ignorance. Deborah Prentice and Dale Miller documented it cleanly in a 1993 study of drinking at Princeton: across four studies, students consistently believed they were more uncomfortable with campus drinking than the average student was. Almost everyone felt like the outlier, which means almost no one was. Worse, the students who felt most out of step reported more alienation from campus life, even though the gap they felt was imaginary.

Swap “campus drinking” for “the reorg,” “the vendor we picked,” or “the deadline we committed to in March,” and you have a description of a lot of teams.

Why does it seem worse the more senior the people in the room?

Because the cost of being wrong in public goes up with seniority, and so does the habit of reading the room instead of speaking into it.

James Westphal and Michael Bednar tested this on the most senior room most companies have. In a 2005 study in Administrative Science Quarterly, they surveyed outside directors at more than 200 midsized public companies. When a company was performing poorly, directors who doubted the strategy tended to underestimate how many of their fellow directors shared those doubts. So they stayed quiet, the silence reinforced itself, and boards kept strategies that individual members privately thought were failing. Westphal summed it up in one line: “Each individual doesn’t want to be the first to speak up, and so nobody speaks up.”

The same pattern runs further down the org chart. In an exploratory study published in 2003, Frances Milliken, Elizabeth Morrison and Patricia Hewlin interviewed 40 employees about times they had stayed silent. Most of them had sat on a concern they never raised with a supervisor. The most common reason was not fear of being fired. It was fear of being seen or labeled negatively, and damaging relationships they valued. That is precisely the fear that keeps someone from being the first to say “I’d rather not go to Abilene.”

What does it look like on a real team?

Running IT operations at a large telecom, I once watched my own leadership team commit to moving our on-call paging to a new platform two weeks before a holiday change freeze. I proposed the date because I assumed the team wanted the old tool gone before the busy season. Nobody objected. One person asked a mild question about training, I answered it, and we moved on in under ten minutes.

The cutover was rough. Pages went to the wrong people for most of a weekend, and we spent the freeze period cleaning it up instead of resting. In the review, I went around the table and asked each person when they had first thought the date was a mistake. Every one of them had thought so in that original meeting. Two of them had said as much to each other in the hallway afterward. Each assumed the rest of the group, and I in particular, wanted it badly enough that objecting would look like foot dragging.

The part that stung was that I had my own doubts about the timing. I proposed it because I thought they wanted it. That is the father-in-law’s role in Harvey’s story, and it is the role a manager is most likely to play, because your suggestions carry weight you do not feel from the inside. I have written before about how your team reads your behavior far more closely than you think; a casual proposal from the boss lands as a preference.

How do I find out what people actually think before we commit?

You have to make private views visible before the public position forms. A few habits that work in practice:

Speak last on anything you have an opinion about. Once the most senior person signals a direction, everyone else starts reading that signal instead of their own judgment. Ask for views first, then give yours.

Collect positions in writing before the discussion. Westphal’s own suggestion for boards was to gather anonymous written pros and cons and have the chair read them aloud. On a team, a two-line note sent to you before the meeting does the same job. The point is that each person commits to their view before they can see anyone else’s.

Ask the question that makes dissent normal. “Does anyone object?” invites silence. “If we decided not to do this, what would be the best reason?” or “Who here is lukewarm on this?” gives people a socially safe way in. A premortem does this formally, by asking the group to assume the plan already failed and explain why.

Tell the group the gap probably exists. This sounds too simple to work, but the research says otherwise. In a follow-up study, Christine Schroeder and Deborah Prentice ran discussions with first-year students that explained pluralistic ignorance and how widespread private discomfort really was. Four to six months later, those students reported drinking significantly less than students in a comparison group. Naming the misread changes behavior. “I suspect at least a couple of us have doubts about this date” can unlock a room.

Go back after the meeting. Some people will never object in front of peers. A quick one-on-one (“you were quiet on the vendor decision, what’s your real read?”) catches what the meeting missed, as long as you react well to what you hear. The first time you punish an honest answer, you have taught the whole team to say “sounds good to me.”

What if I’m the one who already suggested the trip?

Then you have the most power to end it, because the team is waiting on your signal. Say plainly that you are not attached to the idea, and that you would rather hear the doubts now than in the post-incident review. Then ask each person directly, starting with the most junior, and wait through the silence that follows.

Harvey’s family could have saved their afternoon with one honest sentence on the porch. Your team usually needs the same thing, and it almost always has to come from you first.

Ty Sutherland

Ty Sutherland is an operations and technology leader with 20+ years of experience. He is Director of IT Operations at SaskTel, founder of Ops Harmony (fractional COO and EOS Integrator), and former COO at WTFast. He writes Management Skills Daily to share practical management frameworks that work in the real world.

Recent Posts