We like to repeat that a good leader « resolves conflict ». A reassuring phrase, but one that smuggles in a strange assumption: that conflict is always a problem to be eliminated. Yet teams with no visible conflict have usually just learned to keep quiet.
Patrick Lencioni, in The Five Dysfunctions of a Team, captures this in a distinction worth borrowing: a leader’s real job is to sort productive conflict—the kind that sharpens a decision—from the sterile kind, which sheds light on nothing and wears everyone down. Until you draw that line, you spend half your energy as a leader trying to put out fires that deserved to be fanned, and letting smoulder the ones that will eventually burn the whole thing down.
According to a widely cited CPP Global study, American employees spend on average 2.8 hours a week dealing with workplace tension. For a manager, that adds up to roughly a month and a half of work a year absorbed by friction. So conflict management is already happening on your team, at a loss, whether you intend it or not. The only thing still in your hands is which conflicts you take on, and how.
Productive Conflict vs. Sterile Conflict: The Distinction That Changes Your Stance
A conflict is productive when it bears on the substance of the work: two people disagree about how to prioritize a backlog, how to scope a deliverable, how to read a metric. The disagreement, here, carries information: it signals that there are at least two plausible readings of the situation, and that the final decision will be better for having seen both. A leader who defuses this kind of conflict by reaching for a soft consensus impoverishes the team under the appearance of keeping the peace.
A conflict is sterile, by contrast, when it bears on the relationship and no longer says anything about the work: a recurring personal grievance, a turf rivalry, a lack of recognition that has hardened into chronic irritation. That conflict sheds no light on the decision. It eats up time, damages the climate, and eventually pushes the best people toward the door. The leader who mistakes it for a substantive debate—« we’re not going to silence people’s opinions »—lets a situation rot that should have been arbitrated.
In practice, three signs let you tell the substantive case from the relational one as the tension rises:
- The verb being used: are people talking about ideas (« I don’t see how this schedule holds up ») or about people (« he always does that »)?
- The conceivable outcome: can you describe a factual result that would end the disagreement? If yes, the conflict is productive. If not, you’re probably in relationship territory.
- The scope: would a competent outsider grasp the stakes in five minutes? A productive conflict can be explained on its own terms, whereas a sterile one only makes sense once you’ve heard the whole back story.
Three Levers Leaders Underestimate
Separate Positions from Interests
Fisher and Ury, in Getting to Yes, popularized a simple idea: what people ask for (their position) is almost never what they want (their interest). Two people can defend strictly opposed positions while sharing a common interest that would make the decision obvious—if anyone took the time to spell it out. The leader’s analytical reflex: before arbitrating, ask twice « why does this matter to you? ». The second answer holds the real information far more often than you’d expect.
Clarify the Decision Matrix Before the Friction
A large share of sterile conflicts comes down to an ambiguity that has nothing to do with personalities: who decides what? When the decision boundary isn’t set in advance—what RACI methods try to formalize, what many teams assume they « know » without ever having laid it out—the slightest difference of opinion turns into a joust to claw back authority. The leader who invests two hours clarifying who arbitrates what recovers dozens of them in friction avoided.
Arbitrate Without Imposing
When a productive conflict has been worked through and the positions remain irreconcilable, the leader has to decide—and do it quickly. The worst stance, the one many adopt out of a misplaced concern for inclusion, is to let a decision rot for fear of upsetting someone. The common-sense rule: a clear ruling, justified in two sentences, is almost always better received than a consensus wrung out of exhaustion. Teams accept rulings; they don’t accept prolonged indecision.
The Classic Traps
Three pitfalls keep coming up in the published accounts on the subject, and a rushed executive falls into them with almost mechanical regularity:
- The false consensus—the meeting ends with « everyone agree? » and no one speaks. That silence, in Lencioni’s reading, reads as agreement while actually being a disagreement people have learned to suppress. It resurfaces at the next meeting, or worse, in the hallways.
- Mediation in the wrong order—trying to reconcile people before settling the issue. That amounts to asking two people to shake hands while they’re still fighting over a budget. Reconciliation, if it’s needed, follows the decision; it doesn’t replace it.
- Asymmetry of listening—systematically giving the last word to the same person (usually the most senior or the most vocal), which closes the discussion before it has happened. A simple protocol—a round table, two minutes each—is enough to correct this bias that goes unnoticed and costs dearly.
None of these levers calls for exceptional skill. They are routines, earned through practice. But they do assume something that isn’t culturally obvious in many teams: accepting that substantive friction is part of work done well. A team that never contradicts itself has probably stopped thinking as more than one.
Going Further
The question worth carrying out of all this isn’t how to avoid conflict on your team. Ask instead: which conflicts have I let die out for the sake of comfort, and which have I tried to stamp out when they actually held a pending decision? Framed that way, conflict resolution is less an emotional knack than a discipline of arbitration: separating substance from relationship, naming who arbitrates, and working at it like any other craft.
If the productive/sterile distinction makes you recognize a current situation in your team, we’d be glad to talk it through—we’re curious about the cases where it fits badly.
