Introduction
Most managers treat conflict as something to minimize or suppress, which trains teams to avoid surfacing disagreement — and the disagreement doesn't actually disappear when suppressed, it just goes underground, where it tends to do more damage over time. A more useful frame treats conflict, handled well, as a valuable source of information about where the team's understanding, priorities, or incentives genuinely diverge.
Distinguishing Productive Conflict From Destructive Conflict
Productive conflict is about ideas, approaches, or priorities — genuine disagreement over the best path forward, grounded in the substance of a decision rather than personal grievance. This kind of conflict, surfaced and worked through openly, tends to produce better decisions than an artificially harmonious process that never tests competing views.
Destructive conflict is personal, repetitive, and doesn't move toward resolution — it's characterized by recurring grievances that never get addressed constructively, or disagreement that shifts from the substance of an issue to attacks on character or competence.
Managers need to actively enable the first kind and interrupt the second — treating all conflict identically, either suppressing both or tolerating both, misses this important distinction.
Surfacing Disagreement Early and Explicitly
A team that never visibly disagrees is not necessarily a well-aligned team — it may simply be a team where disagreement has gone quiet, either due to social pressure, fear of the manager's reaction, or learned helplessness about whether raising concerns leads anywhere. Actively creating space for disagreement to surface — asking directly whether anyone sees it differently, rather than assuming silence means consensus — prevents this quiet suppression from becoming the team's default mode.
Modeling How to Disagree Well
Teams take their cues on acceptable conflict behavior directly from how their manager handles disagreement — particularly disagreement directed at the manager personally. A manager who responds to pushback defensively, dismissively, or punitively teaches the team that conflict is unsafe, regardless of what's said explicitly about valuing open disagreement. A manager who responds to challenge with genuine engagement and consideration teaches the opposite lesson.
Practical Steps for Using Conflict as Information
- Ask explicitly for a dissenting view in team discussions, rather than waiting for it to be volunteered
- Respond to challenges to your own view with genuine consideration, not just polite acknowledgment followed by no actual change in approach
- Address destructive conflict directly and promptly, rather than letting personal grievances fester unaddressed, since unresolved destructive conflict tends to worsen and spread over time
- Distinguish explicitly, in the moment, between disagreement about substance and personal attack, redirecting conversations that drift toward the latter back toward the former