Why Conflict Avoidance Is More Damaging Than Conflict Itself

The Problem Isn’t Conflict

When leaders talk about wanting a harmonious workplace, what they often mean — without realising it — is a workplace where nothing uncomfortable ever gets said. Where disagreements are smoothed over quickly, tension is managed down before it surfaces, and difficult conversations are quietly deferred in the name of keeping the peace.

It sounds reasonable. It’s not.

Conflict avoidance is one of the most quietly damaging patterns in organisational life, precisely because it looks like good leadership. The manager who steps in to calm things down, who keeps conversations positive, who doesn’t want to “create drama” — they often believe they’re protecting their team. In reality, they’re protecting themselves from discomfort, and their team pays the price.

The research is unambiguous on this. Teams that learn to navigate conflict well — where disagreement is surfaced, heard, and worked through — consistently outperform teams where conflict is suppressed. Not because conflict is pleasant, but because the alternative is worse.

What Happens When Conflict Goes Underground

Avoided conflict doesn’t disappear. It relocates. It moves from the meeting room to the corridor, from the team discussion to the private message thread, from the open disagreement to the slow withdrawal of trust.

You’ll recognise the signs if you’ve seen them. A team that seems fine on the surface but where nothing quite moves forward. Decisions that get made and then quietly unmade. People who agree in the room and undermine outside it. A persistent sense that the real conversations are happening somewhere else.

This is what unresolved conflict looks like in practice. It doesn’t manifest as shouting or confrontation — it manifests as disengagement, passive resistance, and the kind of low-level friction that drains energy without ever being named. And because it’s never named, it’s very hard to address.

The longer it continues, the more entrenched it becomes. People build their positions. They collect evidence. They align with others who share their frustrations. What began as a difference of opinion about a project direction can calcify, over months, into something that shapes the entire culture of a team.

Why Leaders Avoid Conflict

It’s worth being honest about why this happens, because it’s rarely a lack of care. Most leaders who avoid conflict are doing so for reasons that feel, in the moment, entirely justified.

Some worry about damaging relationships — that raising a difficult issue will fracture something that’s working. Some have had the experience of a conflict that went badly, escalated, or left lasting resentment, and have drawn the reasonable but unhelpful conclusion that it’s better not to go there. Some simply weren’t taught how to have these conversations, and so they default to avoidance because they don’t yet have the skills to do otherwise.

And some — if they’re honest — find conflict deeply uncomfortable in a personal sense, and have built a management style designed, often unconsciously, to minimise their own discomfort rather than serve their team.

None of these are failures of character. They’re very human responses to genuinely difficult situations. But they have consequences, and those consequences compound over time.

Questions Worth Sitting With

Think about the last time someone on your team raised something difficult with you. How did you respond — and how do you think they experienced that response? Is there a conversation you’ve been putting off that you know, somewhere, needs to happen? And if you asked your team where the real conversations happen in your organisation, what do you think they’d say?

What Healthy Conflict Actually Looks Like

Healthy conflict is not the same as hostile conflict. This distinction matters enormously, because many leaders conflate the two and conclude that avoiding conflict means avoiding hostility. It doesn’t.

Healthy conflict looks like a team that can disagree openly about the best way to approach something, work through that disagreement with mutual respect, and arrive at a decision that everyone understands — even if they don’t all agree with it. It looks like a manager who can tell someone directly that their work isn’t meeting the standard, without it becoming a character assessment. It looks like a team meeting where a flawed idea gets challenged in the room rather than dismissed in the car park afterwards.

What makes the difference is not the absence of tension, but the presence of trust. When people feel confident that a difficult conversation won’t damage their standing, that their perspective will be heard even if it isn’t adopted, and that the other person is engaging in good faith — conflict becomes something a team can work with rather than something it needs to hide from.

This is why psychological safety and the capacity for conflict are connected, not opposed. Teams with high psychological safety don’t avoid conflict — they’ve built the conditions in which conflict can be productive rather than destructive.

Developing the Skill of Navigating Conflict Well

Conflict is a skill, which means it can be learned. But it requires practice, and it requires a willingness to tolerate the discomfort that comes with doing something unfamiliar before you get good at it.

The starting point, for most leaders, is learning to separate the issue from the relationship. Much of the anxiety around conflict comes from the fear that raising something difficult means damaging the connection with the other person. In reality, the opposite is usually true. Teams where people can be honest with each other — where problems get named rather than skirted — tend to have stronger, more durable relationships than those held together by managed politeness.

It also helps to get clear on what the conversation is actually about. Many conflict-averse managers avoid difficult conversations because they haven’t yet worked out what they want to say — and so the prospect of starting feels chaotic and uncontrollable. Clarity about the issue, the impact, and what you’re asking for doesn’t make the conversation easy, but it makes it possible.

And it’s worth paying attention to timing and context. Conflict conversations handled badly are often handled badly not because of what was said, but because of when and where it was said — in a moment of frustration, in a public setting, without adequate preparation or care. The same conversation, handled with deliberateness, tends to land very differently.

Building a Culture Where Conflict Is Workable

Individual skill matters, but culture matters more. A leader who has learned to navigate conflict well will still struggle in an organisation where the unspoken rule is that difficulties don’t get named. Culture shapes what feels possible in a way that individual intention rarely overrides.

Building a culture where conflict is workable means making it safe to disagree — publicly, and without consequence. It means leaders modelling the behaviour: naming tensions early, engaging with pushback with genuine curiosity rather than defensiveness, and being willing to change their position when someone makes a good argument. It means treating a team’s ability to work through disagreement as a capability to be developed, not a sign of dysfunction to be managed away.

This takes time and consistency. A single good conflict conversation doesn’t shift a culture. But a pattern of them — a team that learns, gradually, that difficult things can be said and worked through — creates something genuinely valuable: a group of people who trust each other enough to be honest.

That trust is not incidental to performance. It is the foundation of it.

If you’re ready to develop the leadership skills that make this possible — in yourself and in the managers around you — the Happy Workplace Leadership Programme is built around exactly this kind of work. Practical, grounded, and designed for the realities of leading people today. Find out more about the programme here.

Leave a Reply

Your email address will not be published. Required fields are marked *