The root cause of many team conflicts stems from beyond the people.
The most obvious cause is often not the root of the issue. A conflict looks personal. It sounds personal. Two people who used to work well together are barely in the same room. A team that once moved quickly is now stalling on decisions it should handle in an hour. A senior leader who used to challenge ideas constructively goes silent, or airs the disagreement in the corridor instead of the meeting.
It looks like a people problem. But what looks personal almost always has a system underneath it.
That does not let anyone off the hook. How people behave in conflict matters, and they are responsible for it. But address only the behaviour, and you treat the symptom while the cause stays intact. The conflict resurfaces, in a different form, between different people, and the leader who tried to resolve it the first time has less credibility to try again.
We have worked with leadership teams for over two decades, and one pattern holds true more often than not: by the time a conflict reaches us, it is already toxic, and it did not have to get this far. The tension was visible earlier. It just was not named.
In my twenties, my husband and I hiked the Grand Canyon in the height of summer. We were used to hiking in Canada, where the cool air meant fresh vegetables lasted for days, so we always packed chopped green peppers to spruce up our dehydrated meals. In the canyon heat, the chopped pepper fermented within hours. Canyon rules stipulate that nothing can be left behind, so I had to carry the fermenting pepper in my backpack for four more days! The nauseating smell infiltrated everything in my pack and assaulted my nose every time I opened it. It took well over a year before I was able to eat green pepper again.
The heat did that. The same pepper, in a cooler climate, would have stayed good for days. A team is no different. A healthy culture gives an issue room to be named before it turns. A toxic one speeds up the fermentation. Either way, the lesson holds: address it while it is still fresh, and it is a conversation. Let it sit, and it festers into something a conversation can no longer fix.
This blog gives you a framework for telling the difference: when a team can still work through conflict on its own, and when it has gone far enough that outside help is now needed to turn it around.
Why Most Conflict Diagnoses Get It Wrong
When something breaks down in a team, the instinct is to look for the source. Who started this? Who escalated it? Who is the difficult one?
That instinct is understandable, and it is also why conflicts persist. Sometimes leaders simply do not know how to address what they are seeing, so they leave it and hope it resolves on its own. That is sometimes the right call. Often it is not, and the gap just keeps widening while nobody names it.
An interpersonal diagnosis produces an interpersonal solution: a conversation, clearer expectations, maybe a structural separation. Things settle for a while. Then something shifts, and the conflict is back, or it has moved somewhere else in the team.
Whole systems thinking asks a different question: “What in the system produced this?” Not instead of looking at individual behaviour, but alongside it. Most team conflicts have three layers, and a leader who sees only one will fix what is visible and leave the rest intact.
The micro layer: individuals. What each person brings into the room: their wiring, their history, their read on events. A perception can harden into a “fact” about someone, and once it does, every new interaction gets filtered through that lens. This layer also covers whether people understand that they are simply wired differently, and that the approach that makes one person effective can genuinely limit someone else’s. That is not a flaw in either person. It is information.
The mezzo layer: dynamics between teams. Not within a team, but between them. How budgets get decided, and which teams have to fight for theirs. Whether some functions are quietly ranked above others: strategic versus support, credentials versus years on the job, head office versus the field. Nobody says this out loud, but everyone knows where they stand in it, and that shapes how much good faith people extend across the divide.
The macro layer: culture, systems, and processes. When accountability is unclear, two people can each believe they own a decision, and the collision that follows looks personal but is not. When compensation and promotion reward the competent jerk, or let arrogance slide as long as the numbers hold, the system is telling everyone that results excuse behaviour, and resentment builds underneath. When a policy assumes everyone can be fully available outside work hours, or requires a driver’s licence for a role that does not actually need one, it quietly disadvantages the single parent, the caregiver, the person without a car, anyone who does not fit the mould the policy was written for. And the people disadvantaged by it notice long before anyone else does. When a benefit or a leave policy is withdrawn in a way that feels transactional, people stop trusting leadership’s intent, and that distrust resurfaces later as conflict that looks unrelated to its actual cause. And when leaders model the very behaviour they are trying to correct, the system undermines its own message every day. This is the layer most leaders are not looking at, and usually the most important one.
A good conflict diagnostic looks at all three.
The Three Cs as a Conflict Diagnostic
We use the Three Cs throughout our work: Courage, Compassion, and Context. It is not the only lens for a conflict this layered, but it is a consistent one, and each C shows up twice, in how a person behaves, and in what the system rewards.
Courage. Was the issue named when it first appeared? Most conflicts that reach the point of needing outside help began as something small that nobody named. And it is not only a personal failing: does the system reward courage, or make it cost too much? If the people who avoid friction get ahead while the people who name hard things do not, the system is teaching everyone what to avoid.
Compassion. Was the person behind the behaviour seen? Escalation often has less to do with the issue itself than with someone feeling dismissed or invisible. Systemically: when someone reliable has an off day, does the system make room for that, or does one mistake erase the track record? Do we hold people accountable without belittling them?
Context. Was the environment understood? This is the macro layer: the structure, history, and pressure behind the conflict. Understanding context does not excuse behaviour. It determines where and how to intervene.
When a conflict is stuck, one or more of the Three Cs is missing, at the individual level, the systemic level, or both.
When the Team Can Handle It Internally
Not every conflict needs outside support. Some conflict is a sign that a team is doing exactly what healthy teams do: working through real differences toward a better outcome.
Teams that handle conflict well internally tend to have a few things in common.
They have a shared language. They can name what is happening in the room without it becoming an accusation. They can say “I think we are avoiding the real question” without the comment landing as an attack. Language creates a container for the conversation.
They have enough trust in the bank, not perfect trust, not agreement on everything, but enough of a track record of honesty and care that people believe the other person is not trying to undermine them, even when things are hard.
The power dynamics allow honesty. If the person most affected by the conflict is the most junior in the room, or if the leader is one of the parties, internal resolution becomes significantly harder. It requires a level of psychological safety that takes time to build, and we explored how that safety is created in our June and July blogs.
June Blog: “The Counterintuitive Foundation of High-Performing Teams“.
July Blog: “How to Build Psychological Safety in Your Leadership Team That Delivers Results“.
They understand that we are all wired differently, and that their way is not the only way. They have enough self-awareness to hold the possibility that the approach that makes them effective might actually limit someone else’s effectiveness.
The macro layer has been addressed or is not a significant factor. If the conflict is genuinely between individuals and not being sustained by structural or cultural conditions, internal resolution can hold, as long as it is addressed early enough. If those conditions are in place, the team does not need outside support. They need permission and structure. The Three Cs provide both.
One of our AMC Associates, Anita Bakker, shared a story from her Coaching practice about a team where the diagnosis shifted from a “difficult person” problem to a systemic issue. The breakthrough came when they mapped all three layers and discovered that the role had been designed in a way that put the identified individual in an impossible position. After the system was adjusted, the conflict dissolved, and the person once seen as “difficult” became one of the team’s strongest contributors.
Anita’s Story
A wastewater treatment plant asked me to work with a manager whose team had become openly hostile. Longer-tenured staff clashed with newer hires, respect had eroded on every side, and every move the manager made was read as one more negative, ineffective reaction. He was stretched thin, and none of it was working.
What changed was not a new policy or a reshuffled team. It was the manager’s own leadership. With coaching support, he learned to sit with tension instead of reacting to it immediately, and to ask non-judgemental questions instead of managing symptoms. He started asking himself what might be producing a person’s behaviour, and how his own actions might be landing from someone else’s seat. As he began to see the team through their eyes, trust started coming back the other way too.
One employee, who had returned from leave with almost no trust left to give, was slowest to come round. But as the manager kept listening and kept holding space for the team’s honest feedback, that employee re-engaged, and brought some of the most valuable perspective in the room.
Months later, sick time was down, energy was up, and the manager had more capacity for the work that actually mattered. The team got there themselves. What shifted first was how their leader saw them.
When You Need Outside Help
Sometimes, as in the wastewater story above, coaching support for the leader alone is enough to unlock a team’s own capacity to work through it. Other times the system has moved too far for that, and it needs a voice from completely outside of it.
The people involved almost always want things to change. But the conditions for honest conversation are no longer present, the people inside the system cannot see the root cause that is sustaining the conflict, or things have gotten so toxic that the neutrality of someone outside the system is what the moment now needs.
A leader who recognises that a situation has moved beyond what the team can resolve internally, and who has the insight and courage to bring in outside help, is not admitting failure. They are demonstrating exactly the kind of accurate self-awareness and open-handed leadership that makes teams stronger over time.
The clearest signals that outside support is warranted:
Trust has broken down to the point where the intent behind everything is being questioned. At this stage, every conversation gets filtered through a lens of suspicion. A well-intended comment becomes evidence of bad faith. Genuine attempts at resolution get interpreted as manoeuvring. An outside voice can create a pause in that cycle in a way an internal voice cannot, because they carry none of the history.
The conflict involves power dynamics that prevent honest conversation. If the leader is a party to the conflict, or if the conflict runs along a reporting line, the people involved may not be able to say what needs to be said to each other directly. Not because they lack courage, but because the stakes of honesty are not symmetrically distributed. The person with less power carries a different risk.
The team has tried to resolve it and the commitment to see it through was lacking. Repeated attempts that have not held are not always a sign that the wrong layer was addressed. Sometimes the commitment to address the root issue and follow it all the way through was absent, and that lack of follow-through deepens distrust and breeds complacency in ways that make the next attempt harder. Outside support can bring both the diagnostic clarity and the accountability structure that internal attempts often lack.
The systemic factors are invisible to those inside the system. The people inside the system have adapted to it so completely that they can no longer see it. They describe the conflict in entirely personal terms, and they are genuinely baffled that honest, well-meaning people keep ending up in the same place. An outside perspective can name what the system has made invisible.
The cost of not resolving it is now material. Talent is leaving. Decisions are stalling. The team’s performance has changed in ways that are showing up in results. At this stage, the discomfort of asking for outside help is considerably smaller than the cost of continuing to manage around the conflict.
To help leaders make this call with greater clarity, we have put together a short decision guide: three questions that walk you through whether internal expertise, bandwidth, and neutrality are sufficient, or whether outside support is the right move.
Internal or External Provider Decision Tool
What Good Outside Support Actually Looks Like
When we come alongside a team in conflict, the process is not about swooping in with answers. It is about creating the conditions for the team to find their own way through, with the right support around them.
A diagnostic phase. Before any facilitated session, we work to understand all three layers of the system. Individual conversations, confidential and honest, with the people involved, sometimes alongside 360-degree interviews or assessments, not as a witch-hunt, but to build an accurate picture of what each person is experiencing and what the system looks like from where they sit.
A shared read of the system. We bring what we have seen back to the team in a way that is honest and specific, holding everyone’s contribution while also inviting each person to own their part in the system. This is often the moment when the conflict begins to shift, when the team can see the micro, mezzo, and macro factors that have been producing the behaviour, rather than continuing to see each other as the problem.Facilitated conversations. We follow a specific process that moves a team from distrust toward a place where they are willing to suspend that distrust long enough to see a different vision, one that is genuinely theirs, both individually and as a team. Leadership goes first. Once they have taken personal ownership for their part in what got the team here, it becomes possible to invite everyone else to do the same, and the collective rebuild can begin. This is not one conversation. It is a sequence held over time that makes the journey possible, rather than simply naming what needs to change and hoping it holds. DISC profiles often become part of this stage, not as a label but as a shared language the team can use to understand how different wiring has contributed to the friction.
How DISC profiles can Leverage Team Strengths
Building internal capability. Outside support that creates dependency is not good support. What we equip a team with is shaped by what the diagnosis found. Sometimes that means more direct support for the leader. Sometimes it means moving the whole team forward together over time. Either way, the goal is to leave people with real tools: clarity on their vision, their agenda, and the alignment between what they have committed to and how they are actually working day to day. That usually includes coaching or training for the leaders specifically, so they can keep holding the process once we step back. Collectively, the team develops the capacity to name things earlier, before the next ripple becomes a wave, and to hold future conflict with more skill.
Find out more about our Systemic Team Coaching
A Note on Prevention
- The leader who knows their wiring is less likely to become the unwitting source of team tension. Blog 1
- The leader who delegates with development in mind creates ownership rather than resentment. Blog 2
- The leader whose own groundedness creates psychological safety makes it possible for people to surface issues early, while there is still time to act on them. Blog 3
- The leader who holds courageous conversations with the Three Cs catches the ripple before it becomes a wave. Blog 4
- And the leader who is building a life-giving culture is creating the conditions where people want to work through difficulty rather than around it. Blog 5
None of that prevents all conflict. It prevents conflict from going toxic, from becoming the kind of entrenched, multi-layered breakdown that absorbs leadership attention, costs the organization real performance, and requires significant outside intervention to untangle.
That capacity is something that can be built deliberately. It is the work we do alongside leaders every day, through coaching, through programmes like CS4L, and through the kind of team development that addresses all three layers of a system, not just the one that is most visible. If your team is facing a conflict that feels stuck, or if you want to build the internal capability to handle conflict before it escalates, we would welcome the conversation.
Book a free 40-minute exploratory meeting using the button below.
Or if you are not there yet and would simply like to keep thinking about these ideas, subscribe to our monthly Leadership Insights.