Charlotte Sweeney Associates

Thought Leadership Article

You Can't Build Real Psychological Safety Without Conflict. Here's Why That Matters.

Image for Part 3/3: Charlotte challenges a common myth: psychological safety isn’t the absence of conflict; it’s the ability to work through it without losing trust.

This is the third in a short series on psychological safety — what it really is, and what gets in the way of building it.

There's a question I've been reflection on for a while, a topic that comes up a lot in the leaders sessions I facilitate, and I want to share it wider for reflection and debate:

Can you have genuine psychological safety without ever having conflict?

My answer is no, and this links back to my first article on this subject related to superficial psychological safety.

We treat conflict as the enemy of psychological safety ... something to be managed down, smoothed over, minimised. But the research, and 25 years of watching teams in action, tells a different story. Conflict isn't what breaks psychological safety. Conflict avoidance is.

 

The numbers are uncomfortable

Let's start with what's actually happening in workplaces right now, and I want to use UK data here, because too much of the conversation defaults to American research as if it were universal.

Acas's 2025 report ... the largest study of its kind into conflict in Great Britain ... found that 44% of working-age adults experienced workplace conflict in the past twelve months. That is the highest level ever recorded, exceeding all previous estimates. Over two in five workers also say they believe workplace conflict is rising. Acas estimates the annual cost of conflict to British businesses at £28.5 billion, with the largest share of that cost coming from resignations and dismissals, not legal claims.

The CIPD's Good Work Index 2024, which surveyed more than 5,000 UK workers, found that a quarter of UK employees (around eight million people) experienced workplace conflict in the past year. Among those who did, job satisfaction dropped sharply: only 54% of those who experienced conflict said they were satisfied with their jobs, compared to 77% of those who didn't.

And yet: only a third of employees who experienced conflict felt it had been fully resolved. 70% of employers said they had effective procedures for resolving conflict, but that confidence simply wasn't borne out in employee experience. There is a significant gap between leaders believing they are handling conflict well and employees experiencing it as handled at all.

The pattern is consistent: conflict is prevalent, the cost is enormous, and avoidance ... by individuals and by organisations ... is the default. The problem accumulates in the background while the surface looks fine.

 

Why conflict avoidance and psychological safety cannot coexist

Here's the problem. We often build psychological safety programmes designed to help people speak up, take risks, share ideas, and then, when genuine conflict arises, the instinct of leaders and teams alike is to shut it down. Smooth it over. Call it resolved before it is.

What that does is teach teams something very specific: that safety is available for low-stakes contributions, but not for real ones. Challenge is welcome, as long as it doesn't actually challenge anything important. This is exactly the superficial psychological safety I wrote about previously ... the version that looks functional right up until it matters.

Patrick Lencioni's work is useful here, and a book I loved reading. In The Five Dysfunctions of a Team, he identifies fear of conflict as the second of five fundamental dysfunctions ... sitting directly above the absence of trust. His argument is simple and hard to argue with: if we don't trust one another, we won't engage in open, constructive conflict. And without conflict, we settle for artificial harmony. Meetings become performances, decisions get made in corridors and the real debate never happens in the room. I'm sure many of us have experienced one, if not all of these.

What Lencioni calls "artificial harmony" is indistinguishable from psychological safety to a surface-level observer. The team looks cohesive, nobody's arguing, the culture survey results comes back decent, and underneath it, nothing genuinely difficult is being said.

Research on leader-member relationships reinforces this. A 2025 review published on ResearchGate found that conflict avoidance in leaders ... treating it as a peripheral coping strategy rather than a systemic problem ... stabilises relationships in the short term while simultaneously generating psychological strain, suppressed voice, and inequity over time. Psychological safety, in this framing, is not an automatic outcome of good relationships. It is a contingent outcome, and conflict competence is one of the conditions it depends on.

 

The stress moment is the real test

I've written before about how psychological safety tends to collapse precisely when it's most needed - under pressure, during restructures, when something goes publicly wrong. And it's not a coincidence that those are also the moments when conflict is highest.

Research consistently shows that 34% of workplace conflict is caused by stress. The two peak together. When the organisation is under pressure, stress rises, people revert to self-protective behaviours, and both the likelihood of conflict and the temptation to avoid it increase simultaneously.

A leader who hasn't built the muscle of productive conflict during calm times has no experience or habit to draw on when things get hard. They either avoid the conflict entirely, which breeds resentment and reduces trust, or they manage it badly, which can undo months of carefully built safety in a single conversation. There is no third option that appears from nowhere at the moment of crisis.

 

Not all conflict is the same

This distinction matters enormously, and I think it gets lost when organisations treat "conflict" as a bad thing. Let's take a few examples:

  • Task conflict - this can manifest as disagreement about approaches, priorities, decisions, ideas ... this can improve team performance when handled well. It forces multiple perspectives to the surface, prevents groupthink, and produces better decisions. It is, done right, exactly what psychological safety is supposed to enable.
  • Relationship conflict - this can manifest as personal attacks, contempt, status battles ... these can damage wellbeing, causes burnout, and corrodes trust. It is what happens when task conflict is either avoided for too long and festers, or handled without the appropriate skills (I guess, those 'soft' skills that so many talk about).

 

The goal is not to eliminate conflict. It's to develop the capacity to have the right kind of conflict ... and to stop the wrong kind before it takes hold. As one piece of research puts it: the truest and most robust form of psychological safety is knowing that your team can fight and come out the other side intact. Not that fighting never happens, more that you survive it well.

There's a third dimension to this that gets almost no airtime in Western leadership development: what conflict looks, sounds, and feels like varies significantly across cultures.

In my previous article on psychological safety across global cultures, I explored how in high power distance cultures, where hierarchy is deeply embedded and deference to seniority is a social norm, what a Western leader reads as conflict avoidance may be a team operating entirely coherently within its own cultural frame. Equally, what registers as a robust but healthy debate in one cultural context may feel deeply unsafe in another. If you're leading a culturally diverse team, your working agreement about productive conflict needs to account for the fact that the team may not share a common baseline for what challenge looks like ... or what it means to be on the receiving end of it.

Conflict competence in a global team is more complex than most frameworks acknowledge, and it starts with understanding the cultural and individual lens each person is looking through.

 

The silence that poses as safety

One of the subtler dynamics I observe in teams is how silence gets misread as evidence that everything is fine.

When people are conflict-avoidant, they don't blow up, they withdraw. Concerns get aired outside of the meeting room, tensions accumulate quietly and because nothing is visibly wrong, no one intervenes. On the surface, the team looks cohesive.

This is the organisational equivalent of a pressure cooker ... and it means that when conflict does eventually surface, it does so with far more force than it would have had if it had been addressed early. The avoidance didn't prevent the conflict, it deferred it, and compounded it.

Research published in the Journal of Consulting and Clinical Psychology found that conflict avoidance is as detrimental to psychological adjustment as conflict itself, and that high conflict resolution is associated with significantly lower distress. The problem isn't conflict, it's unresolved conflict. The distinction matters enormously for how we build teams.

 

Three actions leaders can take

1. Normalise conflict as part of the team's working agreement ... before it's needed.

Most teams have no shared language for how they handle disagreement. They have values statements about respect and collaboration, but no actual conversation about what happens when people genuinely see something differently. This is work that teams need to do proactively, not reactively.

  • Name what productive conflict looks like in your team.
  • Agree how it gets surfaced, how it's handled, what the norms are.
  • Make it ordinary, so it doesn't feel like a crisis when it arrives.

 

Lencioni's framework suggests designating someone to play devil's advocate in key discussions ... not as a gimmick, but as a structural normalisation of challenge. When disagreement has a legitimate role in how the team operates, it becomes less threatening. I've seen this in action, and it does work.

2. Get curious about your own conflict avoidance ... and what it's costing the team.

Most leaders who are conflict-avoidant don't really know it. They believe they're keeping the peace, managing relationships, being politically astute. But the research on leader behaviour is clear: avoidance-oriented leadership generates psychological strain and suppressed voice in the people around them, even when relationships appear warm.

Ask yourself honestly:

  • What difficult conversations have you been putting off?
  • What tensions are you aware of but not naming?
  • Who in your team is carrying a concern they haven't felt safe to raise?

The cost of avoidance is rarely visible on the surface. It shows up in attrition, disengagement, and the gradual reduction of honest exchanges.

3. Treat the rupture-and-repair cycle as where real safety gets built.

Psychological safety isn't built in the workshop or the away day. It's built in the moment after conflict ... in how the leader responds, whether they acknowledge what happened, whether the person who raised the difficult thing was treated with dignity even if the answer was no.

Every time a team navigates conflict and comes out the other side with relationships intact, they learn that the team is safe for real issues. Every time conflict is avoided, or mishandled, and nothing is acknowledged, they learn the opposite. The repair doesn't need to be grand, but it does need to be genuine, and it needs to happen. That's the moment that determines whether safety is real.

 

The question to reflect on

The teams I've seen with the most robust psychological safety are not the ones where nobody ever disagrees. They're the ones where disagreement is unremarkable, where it happens, gets worked through, and the team moves forward. Where someone can share the hard messages, can say what others don't want to hear and still be respected. Where conflict is a sign of engagement, not failure.

The absence of conflict is not safety. It is, more often, its absence.

This is the third in a short series on psychological safety — what it really is, and what gets in the way of building it. If you missed the previous articles on how psychological safety looks different across global cultures, as well as superficial psychological safety, you can read them here: 

Part 1: You Don't Have Psychological Safety. You Have the Rehearsed Version.  What really happens to psychological safety when the pressure hits? Most teams discover it was only ever performative.

Part 2: Psychological Safety Looks Different Depending on Where You're Standing. Charlotte shares her thoughts on a blind spot in how we talk about psychological safety across global teams

References and further reading

On conflict prevalence and cost — UK research

 

On conflict avoidance and psychological safety

 

On productive vs destructive conflict

 

Monday, 13 July, 2026

Tags

psychological safety conflict avoidance Future of work Workplace Cultures

Share

Latest Articles