Conflict has a poor reputation. For many managers the word suggests something to be contained or resolved as quickly as possible. But conflict in itself is neither good nor bad. It is unavoidable.
Wherever people with different views work closely together, disagreement arises. The question is not whether conflict occurs, but what happens when it does.
The difference between constructive and destructive conflict
The distinction matters. Constructive conflict concerns the issue: two people disagree about the right solution, and through the disagreement the decision improves because more perspectives come into play. Destructive conflict concerns the people: the disagreement becomes personal, positions harden, and energy goes into winning rather than into finding the right path.
This means a team that never disagrees is not necessarily a healthy team. An absence of conflict is just as often a sign that people do not feel able to say what they think, or that engagement is so low nobody bothers. Amy Edmondson describes psychological safety as precisely the precondition for disagreement surfacing at all.
We handle disagreement differently
One of the most useful insights about conflict is that people approach it in markedly different ways. Some go straight to the issue and say things plainly. Others withdraw and avoid the confrontation. Some reach quickly for compromise to restore calm. Others hold their position until they are proved right.
None of these approaches is wrong in itself. Each has a strength and a downside:
● The direct style
Gets things onto the table quickly, but can be experienced as blunt and can close the conversation down for others.
● The withdrawing style
Avoids escalation and preserves calm, but leaves problems unresolved so they resurface later.
● The compromising style
Restores cooperation, but risks choosing the fastest solution rather than the best one.
● The persistent style
Ensures important considerations are not lost, but can draw matters out.
When styles collide
Picture an employee with a direct style and a colleague who prefers to withdraw. When they disagree, one presses to get things said while the other closes down. The direct one experiences the withdrawing one as evasive. The withdrawing one experiences the direct one as overwhelming.
Neither is wrong about themselves, but they misread each other entirely. And here the decisive shift occurs: the conflict about the issue becomes a conflict about the people. It is rarely the disagreement that damages cooperation. It is the misinterpretation of what the other person is doing.
The answer is not uniformity
The solution is not to make everyone handle conflict the same way. That cannot be achieved in any case, and it would remove the very breadth that makes a team robust. The solution is to make the differences visible so the team can navigate them deliberately.
When a team knows who is direct, who withdraws and who reaches for compromise, the dynamic changes. The direct member learns to leave room for reflection. The withdrawing member learns that directness is not an attack. In practice this gives you a language for discussing how the disagreement is being handled, not only what it is about.
That insight does not arrive on its own. It requires actively mapping and naming how each team member responds to disagreement and pressure.
Better conflicts, not fewer
Conflict is not a sign of a poor team. Unprocessed conflict is. The difference lies in whether the team knows its own patterns well enough to handle disagreement constructively.
Teams that understand each other's conflict styles do not argue less. They argue better, and they reach better decisions on the other side. If you would like to explore what that could look like in your team, we are happy to talk.