Why the Best Leaders Don’t Eliminate Conflict—They Turn Differences Into Better Decisions
By Dr. Phạm Hà
Most leaders say they want people to speak up. We ask employees to challenge assumptions, contribute new ideas, and tell us when they disagree. Yet when disagreement actually arrives—especially when it challenges our own judgment—the experience can feel very different. What we welcomed in principle can suddenly feel like resistance.
That tension lies at the heart of Disagreeing Productively and Collaborating Well. The course makes an important distinction: collaboration is not the absence of disagreement. In many cases, productive disagreement is evidence that collaboration is working.
For leaders, the challenge is therefore not to create organizations in which everyone agrees. It is to create organizations in which people can disagree without damaging trust, examine opposing information without becoming defensive, and eventually make a decision and move forward together.
That is not simply a communication skill. It is a leadership discipline.
1. Disagreement Is Not Conflict
The first distinction leaders need to make is between agreement, disagreement, and conflict.
Agreement creates alignment, but too much of it can create complacency. Disagreement introduces competing information and perspectives, which can improve decisions. Conflict emerges when differences become personal, emotional, or adversarial enough to damage collaboration.
The objective is therefore not maximum agreement.
Nor is it maximum debate.
The goal is the productive zone between the two.
This becomes especially difficult when three conditions are present: information is unevenly distributed, the decision matters greatly, and people depend heavily on one another for the outcome. These are precisely the conditions surrounding many important executive decisions.
Ironically, the decisions where disagreement feels most uncomfortable may be the decisions where it is most valuable.
The leadership question changes from “How can I get everyone aligned?” to:
“How can we disagree enough to improve this decision without allowing disagreement to damage our ability to work together?”
2. Beware the Certainty of Naive Realism
One psychological obstacle makes this particularly difficult: naive realism.
We naturally experience our own interpretation of reality as objective. If another intelligent person sees the same information and reaches a different conclusion, it is tempting to assume that they are uninformed, biased, emotional, or simply wrong.
But the other person may be making exactly the same judgment about us.
This creates a dangerous escalation. We stop examining the disagreement and start diagnosing the person.
A more productive question is:
“What might this person be seeing that I am not?”
This does not require abandoning conviction. Leaders still need judgment. They must eventually decide.
But conviction without curiosity easily becomes rigidity.
Intellectual humility begins with accepting a simple possibility: I may have relevant information that you lack, and you may have relevant information that I lack.
Disagreement can then become an exchange of information rather than a contest of identities.
3. Receptiveness Is More Than Listening Politely
The course introduces receptiveness as a multidimensional capability. It involves emotional composure, curiosity about opposing views, maintaining respect for counterparts, and openness around difficult or taboo issues.
All four matter.
A leader may remain outwardly calm while having no genuine curiosity about another position. Another may ask questions but subtly lose respect for someone who disagrees. A third may be open-minded until the discussion reaches an issue tied closely to identity or deeply held beliefs.
True receptiveness requires us to access, consider, and evaluate information we dislike with something approaching the seriousness we give information that confirms what we already believe.
This is difficult because disagreement is rarely purely intellectual. Status, experience, ego, history, and organizational power enter the room with us.
Receptiveness therefore begins internally.
Before asking “How can I convince them?”, the better question may be:
“What could I learn from them?”
That shift seems small. Its effect on the conversation can be profound.
4. P.A.L.: Make People Feel Heard
Thinking receptively is not enough. The other person must be able to observe it.
One practical technique is the P.A.L. cycle: Paraphrase, Ask, Listen.
First, paraphrase what the other person has said. This is not parroting their words. It is demonstrating that you have understood the substance of their argument.
Second, ask an elaboration question.
Instead of:
“Don’t you realize how risky that is?”
try:
“Could you explain which risks concern you most?”
Instead of:
“But what about the budget?”
ask:
“How does the budget affect the way you’re evaluating these options?”
The distinction matters. Interrogation questions are designed to expose weakness. Elaboration questions are designed to reveal information.
Finally, listen to the answer.
This is harder than it sounds. We frequently listen only long enough to prepare our response. Productive listening requires temporarily suspending that instinct.
Then repeat the cycle:
Paraphrase → Ask → Listen → Repeat.
P.A.L. embodies a powerful leadership principle:
Before asking to be understood, demonstrate that you understand.
5. H.E.A.R.: Disagree Without Creating Resistance
Listening well does not mean leaders should suppress their own views. The challenge is expressing disagreement in a way that allows the argument to be evaluated without unnecessarily provoking defensiveness.
The H.E.A.R. technique provides another useful framework.
H — Hedge your claims.
“I think it is possible that…” leaves more room for dialogue than “This is clearly…”
E — Emphasize agreement.
“I think we both want the project to succeed” reminds people that disagreement about means does not necessarily imply disagreement about ends.
A — Acknowledge other perspectives.
“I understand why the timing concerns you” signals recognition without requiring agreement.
R — Reframe to the positive.
Rather than focusing exclusively on what should not happen, articulate the outcome worth pursuing.
Hedging is particularly interesting for leaders. Executives are often rewarded for certainty, and consequently we can mistake qualification for weakness.
But there is a difference between indecision and intellectual humility.
“I may be missing something, but based on the evidence I currently see, I favor Option A” can communicate both conviction and openness.
That combination is often stronger than certainty alone.
6. Facts Change Minds; Stories Change Perspective
Another lesson concerns storytelling.
When disagreement becomes intense, leaders often respond by adding more evidence. Sometimes that works. Sometimes it causes each side to search for additional evidence supporting its existing position.
Personal narratives can operate differently.
Facts answer: What is true?
Stories help answer: Why does this matter to you?
Suppose I argue that companies do not need to become the largest in their industries to become great. I can support that position with research on differentiation, specialization, and competitive advantage. But I can also explain how experience building a business taught me the value of remaining focused, agile, culturally distinctive, and close to customers.
The evidence provides credibility. The experience provides meaning.
The strongest arguments often combine both:
Experience + Evidence + Meaning.
Storytelling should never substitute anecdote for evidence. But when used responsibly, it can help another person understand not merely our conclusion, but the journey that led us there.
7. Strong Teams Design for Disagreement
The most important implication may be organizational rather than interpersonal.
Leaders often tell teams to “speak freely.” But hierarchy does not disappear because the CEO says everyone has an equal voice.
Productive disagreement must be designed into the process.
Teams can solicit written views before meetings so that the first senior person to speak does not anchor everyone else. Anonymous voting can reveal hidden disagreement. A devil’s advocate or red team can deliberately challenge the preferred proposal. Quieter participants can be invited directly into the discussion.
Leaders themselves can sometimes speak last.
Teams can even ask participants to present someone else’s position before defending their own. Doing so forces people to understand an opposing argument well enough to articulate it fairly.
Most importantly, the decision rule should be clear.
Is the group deciding by consensus? Majority vote? Recommendation to one accountable executive? Who has input? Who has the final decision? When will it be made?
Ambiguity about decision rights often turns healthy disagreement into frustration.
A leader can say:
“I want everyone to challenge this proposal. I will listen to every perspective, and I will make the final decision on Friday.”
That is not a contradiction between openness and authority.
It is receptiveness combined with accountability.
8. From Winning Arguments to Improving Decisions
Taken together, the course offers a compelling progression.
Receptiveness changes how we think about disagreement.
P.A.L. changes how we listen.
H.E.A.R. changes how we express our position.
Storytelling helps people understand the experiences behind our beliefs.
And team processes transform individual disagreement into collective intelligence.
For leaders, the implication is significant.
The objective of disagreement should not be to demonstrate that I was right and you were wrong. Nor should collaboration require artificial consensus.
The better standard is:
Did our disagreement allow us to see more of the problem than either of us could see alone?
This is particularly important for senior leaders because organizational power creates a paradox. The higher we rise, the easier it becomes to speak—and the harder it becomes to hear what people really think.
Employees learn quickly what leaders prefer. Silence can begin to resemble agreement. Agreement can begin to resemble evidence. Eventually, leaders may become surrounded by confirmation precisely when they most need challenge.
The antidote is not weaker leadership.
It is leadership confident enough to invite disagreement.
The strongest team, then, is not the team that agrees most often. It is the team that can challenge assumptions without attacking people, listen without surrendering judgment, debate without destroying trust, and decide without demanding unanimity.
That gives us a simple leadership sequence:
Be curious before being certain.
Listen before responding.
Disagree without disrespect.
Decide with clarity.
Then move forward together.
Because the purpose of productive disagreement is not to win the argument.
It is to make the decision better.
