Five Steps to Effective Conflict Resolution

Core idea

Conflict at work is not the problem — unaddressed conflict is. When two people see the same situation differently and one of them quietly absorbs the hurt, the resentment doesn't dissipate; it metastasises into withdrawal, passive-aggression, or a public blow-up later. The five-step model is the disciplined alternative: a sequenced, repeatable process that takes a felt disagreement and walks it to a shared agreement without either party having to win.

The five steps are ordered, and the order is the point. Think first before you speak, so emotion doesn't drive the meeting. Gain a better understanding by asking and listening before you conclude. Define the problem explicitly, in words everyone can sign on to, before proposing any fix. Offer your best solution — and stay flexible when the other person counter-offers. Agree on the resolution out loud, so commitments are mutual and visible.

Author's argument: Effective conflict resolution gets people back on track, opens the door to creative thought processes, and paves the way to open, honest, and effective communication.

Skipping a step does not save time — it guarantees a second meeting. Most failed workplace conversations skip step 3 (define the problem) and jump straight from "we have feelings about this" to "here's what we should do," which is why the other person resists a solution they never agreed needed solving.

Why it matters

What it prevents

The model is best understood by what it makes impossible. A conversation that follows all five steps cannot devolve into a public shaming (because step 2 happens in private), cannot end with a vague "let's just move on" (because step 5 names the next concrete commitment), and cannot leave one party feeling ambushed (because step 1 includes choosing the time and place). The five steps function as a chain of small safety rails — each step constrains the next so that escalation has no easy purchase.

Why ignoring it costs more than confronting it

The opening cautionary tale in this topic is a team leader, Dave, who senses his colleagues are hurt by his promotion and decides to wait it out. A week later, the team is barely civil; Dave silently absorbs the work of two people; the relationship cools further. The cost of avoidance compounds — not linearly, but in cascade. By contrast, a single 20-minute meeting on day two would have surfaced the actual grievance (workload, not the choice of leader) and produced a workable agreement.

Why it scales beyond individual disputes

The same five steps work for a one-on-one disagreement, a three-person team frustration, or a cross-functional escalation. The number of people changes how you facilitate — more parties means more time on step 2 (gain understanding) and step 4 (offer solutions, take counter-offers) — but the sequence does not change. Once internalised, the model becomes a lens you can apply to any disagreement you are in or mediating.

Key takeaways

Mental model

Copy sourceZoom

The five steps in detail

1. Think first. Before you speak, regulate the emotion. Take the deep breaths, walk the block, sleep on it — whatever it takes to drop your heart rate and recover objectivity. Then identify the specific behaviour that bothered you, not the person ("Chad threw the paperwork on his desk", not "Chad is being a jerk"). Finally, decide what outcome you actually want from the conversation. If you cannot answer that question, you are not ready to have it.

2. Gain a better understanding. Get the parties together. Open with a non-accusatory framing using an "I" phrase. Then ask, and listen. Pay attention to nonverbal cues — folded arms, broken eye contact, terse answers — and resist the urge to interrupt or rebut. If the other person becomes emotional, lower your voice; speak softly enough that they have to calm down to hear you. If tempers spike, postpone. Listening longer than feels comfortable is usually the right move.

3. Define the problem. Recap what you have heard, then assertively state how you see the issue: "This is how I see it…" Invite agreement or correction: "How do you see it?" The goal is a single sentence both parties can sign on to before any solution is proposed. If anyone is confused or disagrees with the framing, go back to step 2. Solutions proposed before this step are rejected reflexively, because the other person has not yet agreed there is a problem to solve.

4. Offer your best solution. Once the problem is named, propose your preferred fix and ask if the other party agrees. If they don't, invite their counter-offer. Stay flexible — name the meeting purpose ("we are here to find a solution, not assign blame") if the conversation drifts toward who is at fault. Analyse the consequences of each proposal together. If discussion stalls, postpone rather than force a bad agreement; if a stalemate persists, escalate to someone with authority to make the call.

5. Agree on the resolution. Restate the agreement explicitly and give everyone the chance for one last objection. Name the next concrete step, the new commitment, and what happens if it slips. Write it down where the stakes warrant. If consensus is impossible, fall back to vote-or-decide — but explain why, so even dissenters can buy in. The conflict is only resolved when every party has heard the resolution in their own words.

What happens when you skip a step

Copy sourceZoom

Practical application

The model is simple to describe and surprisingly hard to execute when you are the one who feels wronged. Use the following playbook the next time a workplace conflict surfaces.

Example

Note: this example is original and does not appear in the source book.

Imagine: your coworker Sara missed a Tuesday deadline that you depended on for your Wednesday client deliverable. You worked until 11pm Tuesday night to cover, and you are angry. Walking through the five steps:

Step 1 — Think first (Wednesday morning, before you say anything). You take ten minutes with coffee. The specific behaviour is "Sara delivered the spec file at 9am Wednesday instead of 5pm Tuesday" — not "Sara is unreliable" or "Sara doesn't respect my work." The outcome you actually want is not an apology (though one would be nice); it's a working agreement that prevents the next late delivery from blowing up your week again. You note that Sara has been working on a hard launch this month — she may have had a genuine fire, not carelessness.

Step 2 — Plan the meeting. You message Sara: "Hey, do you have 20 minutes after standup? I want to talk through the deadline yesterday so we can adjust for next week's deliverable." Time: 10:30am, after the team coffee dust settles. Place: the small conference room, door closed — not at your desks, not in the open. Opening: "I want to share what happened on my side yesterday and hear what was happening on yours, because I think there is something we can change for next week." Examples to cite: just one — yesterday's specific deadline and the 11pm consequence.

Step 3 — Talk it out and listen. You open with the prepared sentence. You describe the impact on your Tuesday night — concrete, not catastrophising. Then you stop. Sara explains that the launch had a Sev1 issue at 3pm Tuesday that absorbed her afternoon, and she didn't message you because she assumed you knew about the incident. You paraphrase: "So the spec slipped because the Sev1 ate your afternoon, and from your side you assumed I had context on the incident."

Step 4 — Define the problem together. You say, "So the issue isn't the missed deadline itself — those happen — it's that I didn't know it was at risk until it was already late, so I had no time to adjust. Does that match how you see it?" Sara nods: yes. That is the problem statement you'll solve, not "Sara is unreliable" and not "Marcus is high-maintenance about deadlines." Both of you sign on.

Step 5 — Offer the solution and agree. You propose: "When something puts a shared deadline at risk, let's both message before end of day, even if the answer is 'I'm still trying.'" Sara counter-offers: "And when you need something for an early-morning client review, can you tell me the night before so I know it's pinned?" You agree to both. You restate: "So — same-day message if a shared deadline is at risk, night-before pin if you need it before 9am the next day." Sara confirms. You add: "If I miss it again, just tell me that day — don't sit on it." Sara says she'll do the same. You leave the room in less time than the deliverable cost you to redo.

The relationship is now stronger, not weaker, than it was before the missed deadline — because you ran the loop instead of absorbing the cost and quietly resenting her for it.

Related lessons