How to Lead Your Team Through Conflict Without “Fixing” It

When conflict breaks out on your team, isn’t your first urge to “fix it”?

It’s an understandable impulse. You’re accountable for results. Tension slows things down. And you likely know your team long enough that stepping in feels natural — even satisfying. The trouble is, when you consistently take ownership of your team’s conflicts, you may be solving the immediate problem while creating a much larger one.

Teams that are rescued from their disagreements rarely learn how to resolve them. Over time, they stop trying. They escalate to you faster, engage with each other less, and become more dependent on your judgment rather than developing their own. The leader who solves everything doesn’t build a strong team. They build a team that can’t function without them.

Two Roles That Are Easy to Confuse

There’s a meaningful difference between two leadership approaches in conflict, and most leaders rarely choose between them.

The Decider steps in, hears both sides, renders a verdict, and moves the team forward. This can look like strong leadership. Sometimes it is. But it puts the outcome in your hands rather than theirs — and that has consequences.

The Guide commits to a different role: facilitating the team’s process rather than determining the team’s answer. The Guide names the conflict openly, creates structure for working through it, and holds the space while the team does the harder work of finding their own resolution. The Guide is still very much leading — just in a different direction.

One builds dependency. The other builds capability. Quite honestly, there are appropriate situations for both.

What the Guide Actually Does

Being a guide isn’t passive. It requires a specific set of moves, and it starts before you say a word about the conflict itself.

Name it. Don’t wait for conflict to become obvious before you acknowledge it. If tension is present, bring it into the open. Naming it — calmly and without judgment — is itself a leadership act. It signals that this is something you can handle together.

Clarify the real issue. Push the team past generalities. What, specifically, is the disagreement about? What does each party actually need? This is where the distinction between positions and interests becomes practical (see our previous article in this series). People often argue about what they want when the more useful conversation is about why they want it.

Establish what’s negotiable and what isn’t. Some things are genuinely open to discussion. Others — organizational values, legal requirements, firm strategy — are not. Being transparent about which is which prevents the team from spending energy trying to change things that aren’t available to change.

Explore before evaluating. Encourage the team to generate options without immediately judging them. Premature evaluation shuts down creativity and tends to entrench positions. Let ideas breathe before you assess them.

Ask what the team has learned from similar situations. If you’ve navigated this terrain before — as a team — that history is useful. What worked? What didn’t? What’s different this time? Revisiting similar conflicts can be quite informative.

When It’s Right to Step In — and When It’s Not

There are times when the Decider role is genuinely appropriate, and a good guide knows the difference.

If the conflict involves a violation of values, ethics, or firm policy, the leader must decide. This isn’t a situation to facilitate — it’s one to resolve with clarity and appropriate consequence.

If the team is stuck in a loop and the cost of continued impasse is greater than the cost of a top-down call, stepping in can be the right move. But it’s worth asking honestly: are they actually stuck, or are they just uncomfortable? Think about how you can treat each.

For most team disagreements — about priorities, approaches, resources, working styles — the guide role produces better outcomes. The team owns the resolution, which means they’re more likely to honor it. And the process itself builds the relational muscle to handle the next disagreement more effectively.

The Question That Closes the Loop

After a team conflict resolves — whether cleanly or messily — there’s one conversation worth having that many leaders skip: What did we learn?

Not just about the issue. About the process. About how the team handled pressure and disagreement. About what each person discovered about themselves and their colleagues. This debrief is where real team culture gets built. It turns a difficult experience into a shared reference point — something the team can draw on the next time tension surfaces.

The leaders who do this consistently find that their teams become progressively better at working through conflict on their own. And that’s the point.

Reflection: Think about the last conflict you resolved for your team. Did the team walk away more capable of handling the next one — or more reliant on you to handle it for them? That distinction is worth sitting with.

Gary McClure is Managing Director of Strategy at Thrivence, a consulting firm specializing in strategy, leader development, organizational performance, and technology. For more than 20 years, Gary has led organizational transformation initiatives and taught leaders how to navigate successful change. He can be reached at gary.mcclure@thrivence.com. To learn how Thrivence develops leaders who build high-performing, self-sufficient teams, visit thrivence.com.