TL;DR
- Conflict resolution is a situational decision. You match the right conflict-handling mode to the conflict in front of you, not a fixed personality style.
- The five strategies (competing, collaborating, compromising, avoiding, and accommodating) are tools, and collaborating is not always the right one.
- Diagnose the conflict type first (task, relationship, or process), because misreading the type is why resolutions don't stick.
- Run a repeatable conversation: name it, surface what each side actually needs, propose an option, and agree a check-back.
- Conflict resolution stops being optional at the step from individual contributor to manager.
What is conflict resolution
Conflict resolution is a situational decision. It's choosing which of the recognized conflict-handling modes fits this specific conflict, and then running the conversation that follows. The five modes come from the Thomas-Kilmann model: competing, collaborating, compromising, avoiding, and accommodating. They're tools, not a diagnosis of who you are. It isn't a fixed conflict style you're stuck with, and it isn't always about collaborating.
Here's each mode in a line:
- Competing is pushing for your own position.
- Collaborating is working the problem together for an option that serves both sides.
- Compromising is splitting the difference when a fair-enough answer beats a perfect one.
- Avoiding is choosing not to engage, at least for now.
- Accommodating is giving way when you're wrong or the relationship matters more than the point.
The trap the internet sets is treating this like a personality quiz, where you find out you're a "collaborator" and that becomes your brand. It doesn't work like that. The skill is knowing which mode this conflict needs, which is a decision you make fresh each time. I'll show you when each one is the right call in the how-to section below. Here, the only point is that they're situational tools, not a diagnosis.
Why conflict resolution matters at work
Conflict handled badly is expensive in ways nobody puts on a dashboard. Decisions stall. The same argument runs on repeat. Good people quietly disengage, and then they leave. And the opposite failure is just as real: dodge every conflict, and small problems you won't name fester into big ones.
That's the part the "just be more collaborative" advice misses. Both directions cost you. Over-fighting burns trust, and chronic avoiding lets the rot spread.
Most of the people who come to us in recent MentorCruise application data are asking for a structured method they can follow, not encouragement. That's why the rest of this is a method rather than a pep talk. Conflict resolution is one of the soft skills that sounds fuzzy until you realize it's just a set of moves you can practice.
Conflict resolution examples
You can't resolve a conflict until you've named which kind it is, because the repair for a task disagreement is nothing like the repair for a personality clash. Workplace conflict sorts into three types that the researcher Karen Jehn mapped: task conflict, relationship conflict, and process conflict. Most advice skips this step and jumps straight to tactics. Diagnose first.
Here are the three types, with the situation you'd recognize, the reason each one is easy to misread, and the move that actually repairs it:
| Conflict type | What it looks like at work | Why it's easy to misread | The move that actually repairs it |
|---|---|---|---|
| Task conflict | Two coworkers disagree on the technical approach or which thing to prioritize | People defend ideas hard, so it looks like a grudge when it's really about the work | Pull both sides back to the goal. "What outcome are we each optimizing for?" usually surfaces that you want the same thing |
| Relationship conflict | Two reports won't work together, and it's personal, about tone, history, or trust | You assume it's about the task, so you keep re-explaining the work and it never lands | Name the relationship directly and set behavior expectations. You can't logic your way out of a trust problem |
| Process conflict | The team keeps fighting about who decides, in what order, and by when | It disguises itself as task conflict, so you re-litigate the decision instead of the decision-making | Fix the process, not the instance. Agree who owns the call and how it gets made, once, so you stop having the same fight |
The reason this matters: if you treat a relationship conflict like a task disagreement, you'll present more evidence and watch it change nothing, because evidence was never the problem. Naming the type is what makes the resolution hold.
How to improve your conflict resolution
You get better at conflict resolution on two axes. You pick the right strategy for the conflict in front of you, and you run a repeatable conversation once you've picked. Most people are short on one or the other. They know the five strategies but freeze in the actual talk, or they can talk fine but always reach for the same move. Below is both: the strategies with a stance on when each fits, plus a script to rehearse.
The five conflict resolution strategies, and when each is the right call
The five conflict resolution strategies are competing, collaborating, compromising, avoiding, and accommodating. That's the Thomas-Kilmann model again, and here's the part most articles won't say out loud: they're situational tools, not a ranking, and collaborating is not automatically the best one. Sometimes avoiding is the correct call. Sometimes you should give way on purpose.
| Strategy | What it is in one line | When it's the right call | Worked workplace example |
|---|---|---|---|
| Competing | You push for your position | The stakes are high and you're confident you're right, or a fast, firm call is needed | A security flaw ships Friday unless someone overrides the timeline. You override it, and you own the decision |
| Collaborating | You work the problem together for an option that serves both | The issue matters to both sides and you have the time to get it right | Two teams want the same engineer. You dig in and find a rotation that unblocks both roadmaps |
| Compromising | You split the difference | A fair-enough answer now beats a perfect one later, and both sides can live with less | You want the launch in two weeks, marketing wants four. You land on three and move on |
| Avoiding | You choose not to engage, for now | The issue is trivial, emotions are too hot to be productive, or it genuinely isn't yours to resolve | A colleague snaps in a brutal week. You let the comment go instead of turning it into a thing |
| Accommodating | You give way | You're wrong, or the relationship matters more than winning this point | A teammate feels strongly about a naming choice you don't care about. You concede and bank the goodwill |
The two the internet is scared of are avoiding and accommodating, because they sound like weakness. They're not. Refusing to fight a pointless fight is a skill, and conceding a point you don't care about to keep a relationship you do is a trade, not a loss. The failure mode is doing either one by default, on every conflict, instead of choosing it on purpose.
A repeatable script for the hard conversation
Once you've picked a strategy, the conversation itself is where people freeze. So run the same four steps every time, and you stop improvising the hardest part in the moment. The idea underneath all four is one distinction: people argue positions, but resolution comes from interests, which is what each side actually needs underneath the thing they're defending.
- Name it. State the conflict plainly and without blame. "We're not aligned on who owns the release, and it's costing us. Let's sort it." No accusation, no throat-clearing, just the thing on the table.
- Surface the underlying interest. Ask what each side actually needs under the position they're holding. When that first mentor told me the platform wasn't worth their time, the position was a flat no. The interest, once I asked, was legacy: they wanted to be remembered for the people they'd developed. I rebuilt the pitch around that, and the no became a yes.
- Propose. Put a concrete option on the table that serves both interests where it can. Not "let's find something that works," which is a stall, but an actual proposal the other person can say yes or no to.
- Agree a check-back. Set a specific time to confirm it's holding. "Resolved" has a way of quietly unraveling two weeks later, and a scheduled check-back is what stops a patched conflict from reopening.
Conflict resolution for managers and leaders
Conflict resolution gets harder the moment you manage people, and the reason is worth being blunt about. Individual competence is what got you promoted, but whether you can run the hard conversation is what determines whether you can actually lead. As an individual contributor you mostly manage your own conflicts. As a manager, you give feedback that stings, you mediate between two reports, and you disagree with your own boss.
The step from individual contributor to manager is one of the most common transitions we see people ask us for help with, and it's the exact moment conflict resolution stops being optional and becomes the job.
It's why management coaching and leadership coaching spend so much time here. Ivan Novak, a MentorCruise mentor who has led engineering teams through hypergrowth, coaches the individual-contributor-to-leader jump himself. That's senior technical leadership rather than a conflict-resolution course, but it's the same shift: the point where handling people, not just handling the work, becomes what you're actually paid for.
If you manage a team: the conflict you avoid becomes the culture. A manager who won't run the hard conversation teaches the team to route around problems instead of raising them.
How to build conflict resolution faster
Reading about conflict resolution gets you the map. Building it needs reps with feedback, because you can't rehearse a hard conversation alone, and you can't see your own blind spots in a live one. The moment your tone tipped from firm to combative, the interest you talked right past, the concession you should have made and didn't: those are invisible from the inside.
That's what a structured, expert-led workshop gives you that solo practice can't. You run the conversation on real people, in real time, with someone who has had hundreds of these conversations telling you exactly what you missed. We accept fewer than 5% of mentor applicants, so the person running your reps has been through a multi-stage screen before they ever coach you. If you want to build the skill faster than trial and error allows, start with the conflict resolution workshop.
FAQs
What are the five conflict resolution strategies? Competing, collaborating, compromising, avoiding, and accommodating. Competing is pushing for your position, collaborating is solving the problem together, compromising is splitting the difference, avoiding is choosing not to engage, and accommodating is giving way. They come from the Thomas-Kilmann model, and the point is to match one to the situation rather than defaulting to the same move every time.
Is it ever okay to avoid a conflict? Yes. Avoiding is the right call when the issue is genuinely trivial, when emotions are too hot for anyone to be productive, or when it isn't yours to resolve. The mistake isn't avoiding, it's avoiding on autopilot, so that every conflict gets dodged and the real problems never surface. Choose it deliberately for the right conflict and it's a strength, not conflict-avoidance.
How do you resolve a conflict with a coworker? Run four steps. Name the conflict plainly and without blame, ask what they actually need underneath the position they're taking, propose a concrete option that serves both of you, and agree a specific time to check it's holding. Most peer conflicts unstick at step two, because you're usually arguing about positions when the real fix is in the interests underneath them.
What's the difference between conflict resolution and conflict management? Conflict resolution aims to settle a specific conflict, so it has an endpoint: this disagreement, handled. Conflict management is the ongoing skill of keeping conflict productive over time, so a team can disagree well without it turning toxic. You resolve one argument. You manage a working relationship. Most jobs need both, and managing people leans harder on the second.
How do you handle conflict as a new manager? The one shift that matters most is that you now own conflicts that aren't yours, between two reports who won't cooperate, and upward with your own boss. Start by naming the conflict directly instead of hoping it settles itself, because a new manager's instinct to keep the peace is exactly how small problems calcify. Address it early, plainly, and in private.
