Conflict gets a bad reputation it doesn't always deserve.

In most organisations, conflict is treated as a problem to be resolved as quickly as possible — or, more often, avoided entirely. Managers smooth things over. Teams develop elaborate workarounds to avoid confronting real disagreements. HR gets called in when things have already escalated too far.

But conflict itself isn't the problem. The problem is what organisations do with it.

The cost of avoidance

When conflict is suppressed rather than addressed, it doesn't disappear. It goes underground.

It shows up in passive behaviour — the person who agrees in the meeting and then doesn't follow through. In triangulation — two people venting about a third rather than speaking to them directly. In the slow accumulation of resentment that eventually surfaces in a resignation, a complaint, or a blowout at the worst possible moment.

Ironically, avoidance tends to make conflict more damaging, not less. Because unaddressed conflicts don't stay static — they calcify. The longer they're left, the harder they become to shift.

Not all conflict is the same

It's worth distinguishing between types of conflict, because they call for different responses.

Task conflict — disagreement about how to approach a problem, which priorities to pursue, what counts as a good solution — is generally healthy. It surfaces different perspectives and can lead to better decisions, provided it's conducted in an environment where challenge is safe.

Relationship conflict — tension that's personal, that touches on status, respect or identity — is more corrosive. It's harder to address because it activates self-protective responses and makes productive conversation difficult.

Process conflict — disputes about roles, responsibilities and procedures — often looks like relationship conflict but is usually more tractable: it can be addressed by clarifying structure rather than repairing relationships.

The first step in handling any conflict more effectively is understanding which type you're dealing with.

What managers can do differently

The manager's role in conflict isn't to be the judge or the peacemaker. It's to create the conditions in which honest conversation becomes possible.

That starts with modelling: if the manager avoids difficult conversations, the team learns that conflict is not safe to surface. If the manager handles disagreement with curiosity rather than defensiveness, the team learns that challenge is acceptable.

It continues with structure: regular 1:1 conversations that create space for concerns before they escalate. Team retrospectives that surface process tensions. Clear agreements about how disagreements will be handled.

And it involves skill: the ability to hold a direct conversation about a difficult topic without it becoming a personal attack. To separate the behaviour from the person. To ask questions before drawing conclusions. To stay in contact with discomfort long enough for something useful to emerge.

The team coaching perspective

In team coaching, conflict is often the most important signal available. Not a problem to solve — a window into how the team actually functions.

Where is the conflict concentrated? Who is avoiding whom? Which topics never get discussed openly? Which decisions keep getting relitigated? These patterns reveal the team's real dynamics, far more accurately than any survey or formal assessment.

Working with conflict in a team context requires creating enough safety for honest conversation — which is rarely the starting condition — and then using that honesty productively, rather than letting it become an outlet for accumulated frustration.

The goal isn't harmony

A team without conflict isn't necessarily a healthy team. It may simply be a team where the stakes are low, or where people have learned not to say what they think.

The goal is a team where conflict can be expressed constructively — where different views are heard, where disagreements are addressed rather than avoided, and where the team has enough trust to stay in difficult conversations until they lead somewhere useful.

That kind of team handles complexity better. Makes better decisions. And sustains performance over time, rather than burning through it in periodic blow-ups followed by fragile silences.