7 Conflict Resolution Techniques for Managers That Actually Work

Two of your best people stopped talking to each other three weeks ago. Not a fight, not a scene — just a silence that's now leaking into every meeting, every handover, every Slack thread where one of them answers a question the other was supposed to answer. You've noticed. Everyone has noticed. And you're about to make the classic manager mistake: calling them both into a room and asking them to "sort it out."

Don't. That move works maybe half the time, and when it backfires you've turned a manageable friction into a formal grievance. What follows are the conflict resolution techniques for managers that actually survive contact with real teams — the scripts, the sequencing, the moments where I got it wrong, and the ones where a single sentence defused an entire quarter's worth of resentment.

Conflict resolution techniques for managers that survive real teams

The first thing to get straight is what you're actually solving. Roughly a third of the conflicts I've been asked to handle in the past two years had nothing to do with the two people involved. One case: two engineers locked in a passive-aggressive standoff over code review comments. Turned out one had never been given a clear ownership boundary after a reorg, and every review felt like an encroachment. The "conflict" was a role ambiguity problem. Fixing the ambiguity took forty minutes. The two of them are fine now.

Why diagnosis beats action

Before you do anything, ask yourself a blunt question: is this a relationship conflict, a task conflict, or a process conflict?

• Relationship — personal friction, often driven by perceived slights or status. Emotional temperature high, content low.
• Task — disagreement over what to do. Usually healthy if kept civil. This is where innovation hides.
• Process — who does what, how decisions get made. Deadly boring, and the cause of most "personality clashes" I've seen.

Getting this wrong is expensive. I once treated a process conflict as a relationship one, sat both parties down for a heartfelt mediation, and made everything worse — because they both left thinking the other had complained about them personally. Two weeks of rebuilding trust after that. If I'd asked three diagnostic questions first, I'd have spotted the missing decision-rights matrix immediately.

The 5 C's as a pre-flight check

What are the 5 C's of conflict resolution? They're communication, clarity, consistency, curiosity, and commitment — and they make the most sense as a checklist you run before intervening, not as something you recite to your team.

1. Have both parties actually spoken to each other, or only about each other? (Communication)
2. Is the expected outcome of the disagreement defined anywhere? (Clarity)
3. Do I apply the same standard to both people, on record? (Consistency)
4. Am I asking questions or delivering verdicts? (Curiosity)
5. Will I follow up in two weeks, or is this a one-off conversation I'll forget? (Commitment)

That fifth one matters more than people admit. A conflict conversation without a scheduled follow-up is theater.

5 conflict management techniques and when to use each

What are 5 conflict management techniques? The standard five are avoiding, accommodating, competing, compromising, and collaborating — but the useful part isn't memorizing them, it's knowing which situation calls for which. Most managers default to collaborating because it sounds nicest. That's a mistake.

Technique	When it fits	When it backfires
Avoiding	Trivial issue, cooling-off period needed, or the other party genuinely needs to own it	Long-term resentment when you keep dodging
Accommodating	The relationship matters more than the outcome, and the cost is low	When you accommodate a status quo player and everyone else notices
Competing	Safety, compliance, or a clear-cut principle at stake	When it's really a preference dressed up as a principle
Compromising	Time pressure, both sides roughly equal, a temporary truce needed	When it splits a difference that shouldn't be split
Collaborating	Real stakes, both parties need to own the outcome, time exists	When you use it for a decision that should just be made

Honestly, most of my best interventions were competing decisions delivered with a clear rationale. "We're not doing this one collaboratively. Here's why, and here's what I need from you." That's not conflict avoidance. That's clarity, and teams usually respect it more than a fake consensus.

What are 7 effective strategies for resolving conflicts?

The seven I actually use, in rough order of escalation:

1. Ask a diagnostic question before assigning blame. "Walk me through what happened from your side" is almost always the right opener.
2. Separate the two conversations. Emotional first, operational second. Never both in one sitting.
3. Reframe from positions to interests. Ask why, not what. "What do you actually need here?" reveals interests; "what do you want?" reveals positions.
4. Make the disagreement explicit and specific. Vague conflict is unmovable. "I need the client-facing deck by Thursday, you need more design time" is workable.
5. Let the parties draft the solution. Managers who supply solutions get dependency. Managers who supply structure get resolution.
6. Document the agreement in writing. One paragraph, sent to both, referencing who does what by when.
7. Follow up in two weeks — non-negotiable. Conflicts reappear when the follow-up doesn't.

The script that does most of the work

When I sit down with one party first, the opening sentence matters. This has worked well enough that I now use it almost verbatim:

"I'm not here to decide who's right. I'm here to understand what's happening and make things workable. Tell me what's going on."

The "I'm not here to decide" line does the heavy lifting. It lowers the threat response, which is exactly what you want — otherwise you're talking to their defense mechanisms for the next fifty minutes. Then I ask two questions: "What do you need to make this work?" and "What would you need from the other person to feel okay about it?" Both force interest language rather than accusation language.

One mistake I made early on: I tried to summarize too fast. Summarizing within thirty seconds of the other person starting signals you've stopped listening. Wait. Let them repeat themselves. Then summarize.

10 ways to resolve conflict in the workplace

What are 10 ways to resolve conflict in the workplace? Here's my list, cleaned up over many iterations, with the ones I actually rely on more:

1. Name the conflict early — before the silence sets in.
2. Ask each party separately, "What does a good outcome look like?"
3. Distinguish facts from interpretations out loud.
4. Set a specific deadline for the next conversation.
5. Bring in a neutral third party for anything that touches performance ratings.
6. Use written communication as a cooling mechanism for the hot phase.
7. Change the setting — walking conversations work better than sitting ones for tense topics.
8. Escalate to HR when safety, harassment, or legal exposure is in play. Never mediate those.
9. Watch for cross-cultural and intergenerational defaults. What reads as respectful to one person reads as evasive to another.
10. Close the loop in writing, then actually follow up in two weeks.

Point eight deserves emphasis. I once spent two sessions mediating a conflict that I later learned was about a comment I'd made about someone's accent. It wasn't my place to mediate that at all. If boundaries are crossed or protected characteristics are involved, the formal process exists for a reason — using it isn't failure, it's competence.

What nobody tells you about manager mediation

The uncomfortable truth: conflict resolution technique is easy to read and hard to practice, because the real obstacle isn't methodology — it's your own discomfort. Most managers intervene too late because they're afraid of the conversation. I used to be. Then I noticed a pattern: the conflicts I avoided for weeks always ended up costing more time than the ones I addressed in the first three days.

And the two-week follow-up? That's the technique that separates managers who resolve conflicts from managers who seem to resolve conflicts. It's also the one nearly everyone skips. Every time you skip it, you're gambling on the other person's goodwill. Goodwill has a shelf life.

Here's the question I'd leave you with: if you knew, six months from now, which conflict you're currently avoiding would blow up — would you still avoid it this week?