Conflict Resolution at Work Guide

Resolving conflict resolution at work comes down to a repeatable process, not personality. The core steps: identify the real source, look beyond the surface incident, ask both sides for solutions, find one everyone can accept, and confirm the agreement. As UC Berkeley's People & Culture team puts it, the goal isn't deciding who's right or wrong — it's reaching a solution everyone can live with. In a small team, that job usually lands on you, the founder or manager who is also the entire HR function. This playbook gives you the steps, the strategies, and the missing piece most guides skip: how to track resolutions so the same fight doesn't return next quarter.

How to Resolve Conflict at Work, Step by Step

Adapted from the widely-cited five-step model (Canadian Management Centre / CMC), here is the process that works when you don't have a dedicated HR department to hand it off to.

Identify the source of the conflict. Get each person to describe the problem in their own words. You want the underlying need, not the loudest complaint. Often what looks like a personality clash is a resource or role problem.
Look beyond the incident. The blowup over a Slack message is rarely about the Slack message. Ask what's been building. In small teams, tension frequently traces back to workload imbalance or unclear ownership.
Request solutions. Instead of imposing a fix, ask both people what they'd need to move forward. This shifts them from defending positions to problem-solving.
Identify solutions both disputants can support. Look for the overlap. You're hunting for the option each person can genuinely commit to, not the one that silences the room fastest.
Reach agreement. Name the specific action, who owns it, and when you'll check back. Say it out loud, then write it down.

That last habit — writing it down — is where most small teams fall short. We'll come back to it, because it's the difference between resolving a conflict once and resolving it every quarter.

The 5 Conflict Resolution Strategies (Thomas-Kilmann)

Harvard Business School outlines five strategies drawn from the Thomas-Kilmann model. Each has a place; the trick is matching the strategy to the stakes and the time you have.

Strategy	What it means	When to use it on a small team
Avoiding	Sidestepping the issue	Trivial disagreements, or when emotions are too hot to talk productively right now. Not a long-term fix.
Competing	Pushing your position through	Emergencies or safety/legal calls where speed beats consensus. Use sparingly — it costs goodwill.
Accommodating	Letting the other side have their way	When the issue matters far more to them than to you, and preserving the relationship is worth more than winning.
Compromising	Each side gives something up	Deadlines are tight and both positions have merit. Fast and fair, but nobody leaves fully satisfied.
Collaborating	Working to a solution that fully satisfies both	High-stakes, recurring issues where you need real buy-in. It's the ideal — and the most time-intensive.

Collaborating is the gold standard because it addresses the root cause and both people own the outcome. The catch: it takes time and emotional energy you may not have mid-crunch. A practical rule for founders — compromise to get through the sprint, then schedule a collaborating conversation once the pressure lifts.

The 5 C's of Conflict Resolution

If you want a memory aid before a hard conversation, the 5 C's cover the behaviors that make resolution stick:

Communication — say the real thing clearly, and invite the other person to do the same.
Collaboration — treat the problem as shared, not a contest to win.
Compromise — be ready to give ground where it doesn't cost your core needs.
Composure — regulate your own reaction so the conversation stays productive.
Commitment — follow through on what you agreed, so trust rebuilds.

These map directly onto the skills below. The 5 C's are the mindset; the skills are the muscles.

Essential Conflict Resolution Skills

Southern New Hampshire University lists five skills that carry most workplace conflict resolution. Here's each one plus a micro-example you can practice this week.

Active listening. Reflect back what you heard before responding. Practice: "So what I'm hearing is you felt cut out of the launch decision — is that right?" Naming it defuses half the heat.
Assertiveness. State your view without attacking. Practice: swap "You always miss deadlines" for "When the design handoff slipped twice, it pushed my whole week."
Composure. Buy time when you feel reactive. Practice: "I want to give this a real answer — can we talk at 3 instead of right now?"
Empathy. Acknowledge the other person's experience even when you disagree. Practice: "I get why that felt dismissive. That wasn't my intent, and I see the impact."
Problem-solving. Move from grievance to options. Practice: "What would need to change for this to not happen again?"

None of these require a certification. They require reps — which is exactly why small-team managers who handle conflicts consistently get better at them fast. Many of these same muscles show up in activities to build teamwork, where trust and communication get practiced before a real conflict arises.

Conflict Resolution Examples for Small Teams

Abstract steps only get you so far. Here are three scenarios common in startups and small teams, walked through the process.

Example 1: Missed deadlines and blame

Your developer blames the designer for late handoffs; the designer says specs kept changing. Source: not laziness — an unclear change-control process. Beyond the incident: this has happened three sprints running. Solutions requested: the developer wants locked specs by Monday; the designer wants a freeze on mid-sprint scope changes. Agreeable solution: specs finalize Friday, changes go to next sprint unless flagged critical. Agreement: documented in your sprint doc, revisited in two weeks. The conflict was never interpersonal; it was a missing process.

Example 2: Overlapping role ownership

In a 12-person startup, two people both think they own the customer onboarding flow, and they keep overruling each other. Source: role boundaries never defined as the company grew. Beyond the incident: the friction is a symptom of fast hiring without updated responsibilities. Solutions: split the flow — one owns pre-sale setup, the other owns post-sale activation. Agreement: write the boundary into both job descriptions and your OKRs so it survives the next hire. This is the classic small-team conflict: roles overlap because nobody drew the lines yet.

Example 3: Performance feedback disagreement

An employee pushes back hard on your review, saying the feedback is unfair. Source: a gap between their self-assessment and yours, often from thin documentation. Beyond the incident: you gave little real-time feedback all quarter, so the review felt like an ambush. Solutions: agree on specific, observable goals for next quarter. Agreement: log the examples you both discussed and set monthly check-ins so the next review holds no surprises. If the performance gap keeps widening, a structured performance improvement plan gives both of you clear goals and timelines. Notice how each example ends with something written down.

When Conflict Won't Resolve: Escalation and ADR

Sometimes the conversation stalls and the tension keeps flaring. That's your signal to bring in structure or a neutral party. The Oklahoma Bar Association groups the main alternative dispute resolution (ADR) methods — often used before anything reaches a courtroom:

Negotiation. The parties work it out directly, usually with your facilitation. Start here for most workplace friction.
Mediation. A neutral third party helps both sides reach their own agreement. Useful when you, the manager, are too close to the conflict — or are part of it.
Arbitration. A neutral third party hears both sides and makes a decision. Rare inside small teams, but relevant for formal disputes or contractor disagreements.

As a founder or HR manager, escalate when: the conflict recurs after a documented resolution, it starts affecting other team members' morale, or it edges toward a compliance or harassment issue. At that point, stop relying on memory. Document everything formally, and consider an outside mediator so no one can claim you weren't neutral. A single unresolved conflict can quietly sink morale across a small team, dragging down employee engagement — the cost of bringing in help is far lower than the cost of losing two good people to a feud you let simmer.

The Missing Piece: Tracking Conflicts So They Don't Recur

Most conflict resolution guides stop at "have the conversation." That's where small teams get burned. You resolve something in March, and by June the same two people are back in your office over a nearly identical issue — because nothing was recorded, no pattern was spotted, and the fix never made it into how the team actually operates.

The systematic layer looks like this:

Log every resolution. Keep a short, factual record: what the conflict was, what you agreed, who owns the follow-up, and the check-back date. Not a paper trail for punishment — a memory system so agreements survive busy weeks.
Connect recurring friction to performance reviews. If someone shows up in three conflict logs about missed handoffs, that's not a personality quirk — it's performance data. Surface it in the review with specifics, not vibes.
Tie interpersonal friction to OKR misalignment. A surprising share of "personality clashes" are really two people optimizing for competing goals. When you can see the OKRs side by side, you spot the structural cause instead of blaming the humans.
Look for patterns across the team. One conflict is an incident. The same conflict across three pairs of people is a process gap you can fix once.

This is exactly where an HR system earns its place on a small team. When you're weighing options, it helps to know which features actually matter for a team your size. HR HiFi keeps performance reviews, OKRs, and employee records in one place, so a conflict you resolved in Q1 shows up as context in Q2's review instead of vanishing. You can document resolutions cleanly, connect recurring friction to goals and performance, and use AI to flag patterns a busy founder would otherwise miss. The result: you stop re-litigating the same disagreement every quarter and start fixing root causes.

If your team is small enough that you are the HR function, that's precisely why you need the tracking layer — you don't have the bandwidth to hold it all in your head. See how HR HiFi turns one-off conversations into a system that keeps conflicts from recurring. Start with HR HiFi today.

Frequently Asked Questions

What are the 5 C's of conflict resolution?

Communication, Collaboration, Compromise, Composure, and Commitment. Together they describe the behaviors that make a resolution actually hold: talk openly, treat the problem as shared, give ground where you can, stay calm, and follow through.

How do you resolve conflict in the workplace?

Follow the five-step process: identify the real source, look beyond the surface incident, ask both sides for solutions, agree on one everyone can support, and confirm the agreement in writing with a check-back date. The aim isn't to declare a winner — it's a solution everyone can live with.

How do you resolve conflict in a relationship?

The same fundamentals apply outside work: listen to understand rather than to reply, accept the other person even when you disagree, and recognize the conflict exists because both people care. Focus on the shared problem, not on being right.

How do you deal with conflicts that won't resolve?

Move to structured help. Try direct negotiation first, then mediation with a neutral third party, and formal documentation when an issue recurs or affects the wider team. If you're personally involved, an outside mediator keeps the process fair.

What are the 5 methods of conflict resolution?

The five strategies from the Thomas-Kilmann model are avoiding, competing, accommodating, compromising, and collaborating. Collaborating produces the most durable outcome but takes the most time; compromising is the quick, fair option when deadlines are tight.

Conflict Resolution at Work: A Playbook for Small Teams