The Unopposed Mind: Why Leaders Need People Who Disagree with Them

There is a particular silence that happens in meeting rooms after a senior person says, "I think we should do X."

It is not agreement. It is something softer and more dangerous. People nod, someone says "great point," and a decision that nobody actually examined walks out of the room wearing the costume of consensus.

In my essay Who Was the Unabomber? Ted Kaczynski and the Unopposed Mind, I wrote about what happens to a brilliant mind when nobody is left to disagree with it. Kaczynski is an extreme case, of course. He chose isolation. Most leaders don't. They simply get promoted into it.

The unopposed mind is rarely built by arrogance. It is built, one polite nod at a time, by everyone around it.

Why do leaders end up surrounded by yes men?

Not because they hire sycophants on purpose. Almost nobody writes "must agree with me" in a job description.

It happens through small, rational choices. The person who challenged you last quarter was a little exhausting, so next time you invite someone easier. Your team learns which ideas get a warm reaction and which get a long pause. Nobody lies. They just edit. And over months, the information reaching you becomes curated, filtered and quietly flattering.

Psychologists have a phrase for one side of this. In 1951 Solomon Asch asked people to judge which of three lines matched a reference line, a task a child could do. When the people around them (actors, in on the experiment) confidently gave the wrong answer, participants went along with the group on roughly a third of the critical trials. Line lengths. Imagine what happens with budget forecasts, strategy decks and a boss who controls your bonus.

The other side is what power does to the person holding it. Lord David Owen, a former British Foreign Secretary who trained as a neurologist, and psychiatrist Jonathan Davidson described what they called "hubris syndrome" in the journal Brain in 2009: a pattern seen in some leaders after prolonged power, including excessive self-confidence, contempt for advice and a loss of contact with reality. Their point was not that power makes people bad. It was that power, held long enough and unchallenged, changes how people process information.

So the room goes quiet, and the person at the head of the table becomes a little less able to hear what the silence means.

What is groupthink, really?

The word comes from the psychologist Irving Janis, who in his 1972 book Victims of Groupthink studied disasters like the Bay of Pigs invasion. His uncomfortable finding was that the advisers around President Kennedy were not stupid. They were highly intelligent, cohesive and loyal. That was the problem.

Janis described groups that feel invulnerable, explain away warnings, pressure doubters and develop what he called "self-appointed mindguards," people who protect the leader from information that might disturb the mood. Many of the doubts existed. They just never made it into the room.

There is a beautiful counterexample in the same story. After the Bay of Pigs, Kennedy reportedly changed how his advisers worked during the Cuban Missile Crisis, sometimes leaving the room so people could argue without performing for him. Same people, different conditions, very different outcome.

Intelligence does not protect a group from groupthink. Sometimes it just makes the rationalizations more elegant.

Psychological safety: what does it actually mean?

This is where Amy Edmondson's work matters. In a 1999 study published in Administrative Science Quarterly, the Harvard researcher looked at hospital teams and noticed something counterintuitive: the better teams appeared to report more errors, not fewer. They weren't making more mistakes. They were more willing to talk about them.

She called the underlying condition psychological safety, which she defined as:

"a shared belief held by members of a team that the team is safe for interpersonal risk taking." Amy Edmondson, 1999

Later, Google's internal research project known as Project Aristotle, which studied what made its teams effective, reported that psychological safety was the most important of the factors they found.

I want to be careful here, because "psychological safety" has become one of those phrases that gets printed on posters and then ignored. It does not mean everyone is comfortable. Edmondson herself has repeatedly said it is not about being nice.

Psychological safety is not the absence of discomfort. It is the presence of permission.

Permission to say "I think this is wrong." Permission to say "I don't understand." Permission to bring bad news to the person who least wants to hear it.

In Creative Solutions for Ordinary Problems, I suggest treating disagreement itself as a small experiment. Try it in your next meeting: before you share your view, ask one person to argue the opposite for two minutes, and thank them for it. You will be surprised how quickly permission spreads once a leader models it.

Why leaders need dissent (and why a devil's advocate isn't enough)

A lot of leaders, when they hear all this, reach for a familiar tool. "Fine, someone will play devil's advocate."

Charlan Nemeth, a psychologist at UC Berkeley who has spent decades studying dissent, tested exactly this. In a 2001 study in the European Journal of Social Psychology with Keith Brown and John Rogers, she compared groups exposed to an assigned devil's advocate with groups exposed to someone who genuinely held a different view. The genuine dissenter stimulated more original thinking. The role-played one was much less effective, partly because everyone knew it was a game.

Her broader research, summarized in her book In Defense of Troublemakers (2018), makes a point I find thrilling: dissent is useful even when the dissenter is wrong. Exposure to a minority view pushes people to consider more information, look at the problem from more angles and think more divergently. The value is not only in the answer the dissenter gives. It is in the thinking they force everyone else to do.

There is a story, told by Peter Drucker in The Effective Executive, about Alfred P. Sloan at General Motors. At a meeting where everyone seemed in agreement, Sloan is reported to have said:

"Gentlemen, I take it we are all in complete agreement on the decision here... Then I propose we postpone further discussion of this matter until our next meeting to give ourselves time to develop disagreement and perhaps gain some understanding of what the decision is all about."

I love that line because it treats unanimity as a symptom, not a success.

When everyone in the room agrees instantly, the decision hasn't been tested. It has only been applauded.

The AI version of the yes man

Here is the twist of our moment. Many leaders now have a new advisor available at 2 a.m., endlessly patient and impressively fluent. And it has a known tendency, which AI researchers call sycophancy, to lean toward telling people what they seem to want to hear.

Ask a chatbot "isn't my plan brilliant?" and you may get a very articulate yes.

This is why I keep coming back to one sentence: The machine gives answers. The human chooses the question. If the only questions you bring to your tools, your team and yourself are ones that invite agreement, you are building an unopposed mind with better software.

Abraham Lincoln is often held up as the opposite model. Doris Kearns Goodwin's book Team of Rivals (2005) describes how he brought into his cabinet the very men who had competed against him for the nomination, people with strong egos and no reason to flatter him. It was uncomfortable. It was also, Goodwin argues, part of his strength.

How to invite disagreement as a leader

I am not going to give you a ten-step framework. Disagreement does not survive frameworks very well. Instead, a few small experiments and questions.

Speak last. In your next decision meeting, ask everyone to share their view before you share yours. Notice how different the conversation feels when the answer hasn't been announced yet.

Ask a better question. "Any concerns?" almost always produces silence. Try "What would have to be true for this to fail?" or "If you were our competitor, how would you beat this plan?" You are not asking people to oppose you. You are giving them a role in which disagreeing is the helpful thing to do.

Count your challengers. Who, in the last month, told you something you didn't want to hear? Write down the names. If the list is empty or has one name on it, that is data.

Reward the messenger publicly. The first time someone brings you bad news, your reaction is being watched by everyone. Thank them in a way others can see. That single moment teaches the whole team more than any value statement.

Find one genuine dissenter. Following Nemeth, don't assign a devil's advocate. Find a person who actually sees it differently, from another function, another culture, another generation, and bring them in before the decision, not after.

Test your tools too. Next time you ask an AI to evaluate your idea, ask it to make the strongest case against it. Then ask yourself honestly which version you were hoping to read.

None of this is comfortable. That is rather the point.

The question to keep

Kaczynski's tragedy was a mind that became a closed room. Most leaders will never go anywhere near that darkness. But the mechanism, a mind that stops being contradicted and slowly mistakes its own echo for the truth, is quietly available to all of us.

The most useful person in your room might be the one who makes you a little uncomfortable.

So I'll leave you with one question. When was the last time someone changed your mind, and what did you do to make that possible?

With love,

Gizem

If this raised a question you'd like to think through, we can look at it together. Book a free 30-minute Discovery Call.