CIPD’s 2024 survey found that 75% of employers believe their line managers would resolve conflict effectively. Ask the employees who actually went through a conflict in the past year, and 36% say it was fully resolved.
That gap is not a knowledge gap. Most managers can name the five conflict resolution styles and describe what good listening looks like. What they cannot do is open their mouth in the first thirty seconds of a live dispute and say something that does not make it worse.
Scenarios fix that, if you use them properly.
How to practice a conflict scenario so it actually helps
Reading a scenario and nodding at the advice underneath it changes nothing. Two steps do the work.
Write your first line before you read the answer. Not your plan for the conversation. The literal sentence you would say when you sit down. Most managers find theirs is a question, usually “so, what happened?” or “walk me through it.” Those hand the conversation to whoever tells the better story, and the better story is generally the one that got rehearsed on the drive in.
Then write the decision in dispute, in one sentence, with no history in it. “Who signs off on a scope change after the brief is locked.” Not “why the launches keep slipping.” If you cannot write that sentence, the conflict is not ready for a meeting yet, and the meeting will only produce another meeting.
Run both steps against each scenario below. Each one gives you the situation, the move most managers reach for, and the one that shifts it. If you want a baseline read on your own habits first, Risely’s conflict resolution assessment is free, and the conflict resolution worksheets give you somewhere to write both answers down.
7 conflict resolution scenarios at work
Scenario 1: Two departments blaming each other for the same slipped launch
“Marketing keeps changing the brief.” James, a senior manager in product development, has said a version of that sentence in four separate meetings. Sarah runs the marketing team at the same mid-sized software company, and her version is that product ships changes without telling anyone, which is why the brief keeps changing.
They are describing the same handoff from opposite ends.
The move most managers reach for: get everyone in a room and let each side explain its position. This produces a two-hour meeting in which nine people relitigate a launch nobody can go back and change.
What shifts it: name the decision in dispute before anyone tells their story. Open with “we are here to decide one thing: who signs off on a scope change after the brief is locked. Not why the last three slipped.” Then hold that line every time someone reaches for history.
Conflict between departments is usually a governance question wearing an interpersonal costume. Two teams are competing for the same resource, or nobody ever wrote down who decides. State the undecided question in one sentence and you can decide it. Fail to state it and more discussion will not produce it.
The uncomfortable part: sometimes the answer is that one department loses. Someone gets less headcount, or their date moves. A neutral mediator can make that conversation civil. Nothing can make it mutual.
Scenario 2: A handoff that keeps changing and nobody says so
Anna manages a commercial building project at an architectural firm. Tom leads the design team. Anna’s project managers believe Tom’s designers keep deviating from the agreed scope without telling them, which moves timelines and costs. Tom’s designers believe Anna’s team passes on client feedback so vaguely that they have to guess, then get blamed for guessing wrong.
Neither team is lying. This is what miscommunication looks like after it has been running for a quarter: two accurate accounts of the same events that cannot both be acted on. Communication training helps a team that has not yet built two competing records. It does very little for one that has.
What this one needs is not a conversation. It is a document. Ask both leads to write down separately what they believe the last three scope changes were and who approved each one, then compare the two lists in the room. The disagreement stops being about character within about four minutes, because you are looking at two documents instead of two memories. Where the lists match, you have facts. Where they diverge, you have found the broken step in the handoff.
Scenario 3: The remote engineer who hears about decisions after they are made
David manages a hybrid software team across three time zones. Maria, a senior developer, works remotely from another country. Maria’s complaint is that decisions get made in the office and announced to her. The on-site team’s complaint is that Maria is slow to respond and hard to pull into anything.
Both complaints are true, and each one causes the other. Proximity bias means the people in the room get consulted because they are in the room, and the person who is consulted last stops volunteering.
The move most managers reach for: more check-ins with the remote person. That treats the symptom, which is that Maria feels excluded, and leaves the mechanism alone, which is that decisions happen in hallways.
What shifts it: change where the decision happens, not how often you talk. Any decision that affects the whole team gets written in the channel before it is final, with a stated deadline for objections. Nobody has to be awake at the same time. The on-site team loses the hallway shortcut, which they will not enjoy, and that is the real cost of running a distributed team rather than a co-located one with some people missing.
One caution. If Maria is genuinely unresponsive, the written channel will show that too, and then you have a performance conversation rather than an inclusion one. Do not decide which of the two you are holding before you have the record in front of you.
Scenario 4: One manager wants speed, the other wants the process followed
Emily runs operations at a retail company on aggressive deadlines. Daniel, a senior manager on her team, wants more time to think things through. Emily overrides him regularly. Daniel’s team has said they feel micromanaged and rushed. Emily thinks Daniel is slow and does not push his people hard enough.
This gets labeled a leadership style clash, which is where it usually goes to die. Style is not actionable. You cannot ask two adults to become different people by Friday.
What shifts it: turn style into a threshold. Emily and Daniel do not need to agree on how to lead. They need one written rule about which decisions move fast and which get the longer process. Anything reversible inside a week, Daniel decides alone and goes. Anything that touches a customer commitment or costs more than an agreed number, they discuss first, and Emily has 24 hours to object or it proceeds.
The disagreement now has a boundary. It will still surface, but at the edges of the rule rather than in every conversation. Note what the threshold does not fix: Daniel’s team still feels rushed, because the pace is a real business constraint and not a misunderstanding. Tell them that directly rather than presenting the rule as a fix.
Scenario 5: Two people who genuinely do not get along
Karen and Mike are mid-level managers in the finance team of a manufacturing company, assigned to a budget restructuring project together. Karen works from a plan and checks the detail. Mike works from whiteboards and thinks out loud. Six weeks in, Karen has started copying her director on her emails to Mike. Mike has started missing their working sessions.
The standard advice is to celebrate their complementary strengths. Try saying that out loud in front of two people who have stopped being able to sit in a room together.
Here is what the evidence says about the version of this you are actually holding. De Dreu and Weingart’s 2003 meta-analysis in the Journal of Applied Psychology pooled the available studies on team conflict and separated two kinds. Task conflict is disagreement about the work itself: the numbers, the approach, the sequence. Relationship conflict is friction about the people: irritation, dislike, perceived disrespect. Going in, both the academic literature and the textbooks predicted that task conflict would help performance. It did not. Both kinds correlated negatively with team performance and with satisfaction, and the negative effect was larger on complex work, which is exactly the sort of work you hand to two managers jointly.
The finding that matters for Karen and Mike is the second one. Task conflict hurt less when it stayed only weakly correlated with relationship conflict. Put plainly: arguing about the depreciation model is survivable. Arguing about the depreciation model while believing the other person is careless or obstructive is not. Your job is not to stop them disagreeing. It is to stop the disagreement converting from one type into the other.
So what do you say. Not “you two need to work on your relationship.” Take the loudest live disagreement and make it technical again. “You disagree on whether the depreciation schedule gets rebuilt or adjusted. Karen, write the case for rebuilding in half a page. Mike, write the case for adjusting. Bring both on Thursday and we pick one.” You have moved them from a standing grievance to a decision with a date, and you have made it possible for one of them to be right about a thing rather than right about a person.
Both of them are partly in the wrong here, and it is worth saying so to both. Karen copying her director was a real breach: she went around Mike rather than to him. Mike skipping the sessions was a real breach too, and finding them tedious does not make it less of one. Address only one and the other reads the whole intervention as you picking a side, at which point you have added yourself to the conflict.
Expect a partial result. In most versions of this the two people do not end up liking each other. What changes is that the work stops routing through the friction: the depreciation question gets decided, the next question gets decided, and the escalation emails stop because there is nothing left to escalate. Sometimes what finally settles it is not your intervention at all. The project ends, or one of them moves to another team, and everyone quietly agrees the problem is solved. That happens often enough that you should not claim the credit.
The one approach that reliably fails is waiting. Friction left alone does not hold at the same level. It recruits. Karen explains to one person on her team why Mike is impossible, Mike explains to one on his, and a quarter later you are managing two camps instead of two people.
When to stop treating it as a personality problem. If one person’s behavior is crossing into bullying, exclusion, or discrimination, the frame changes completely. That is not a clash to be balanced. It is conduct, it goes to HR, and the even-handed treatment that makes the rest of this section work will actively cause harm if you apply it there.
Scenario 6: A deadline nobody can hit, and the person on the ground says so
Alex directs a construction project running behind because of supply delays and a regulatory change. Rachel manages the site day to day. Alex is pushing for recovery. Rachel says the crew is tired, materials are short, and pushing harder is how somebody gets hurt.
“You are asking me to make up eleven days with the same crew and half the steel.” Rachel is not resisting Alex. She is reporting a constraint, and Alex is hearing an attitude.
Conflict under pressure is mostly this category error. Someone reports a limit; someone else hears refusal.
What shifts it: split the two questions and answer them in order. First, what is actually possible, stated as a number, by the person closest to the work. Second, who tells the client. Managers collapse these two, which is why the conversation turns into an argument about commitment. Ask Rachel for an honest recovery figure with no negotiation attached to it, then carry the shortfall to the client yourself. The tension does not disappear, but it stops sitting between you and Rachel.
Stress techniques get recommended a lot at this point. Breathing before a hard conversation is fine, and it will not fix a schedule that cannot be met. Neither will active listening on its own, though it is what stops Rachel deciding there is no point telling you next time. There is a step-by-step version of it if that is the habit you need.
Scenario 7: The person who knows the old system best and does not want the new one
John is CTO at a financial services company moving off legacy systems onto cloud infrastructure. Linda has run IT there for fifteen years and knows the current stack better than anybody. She is also the loudest objector to the migration.
The reflex is to read Linda as resistant to change. Look instead at what she is protecting. Fifteen years of expertise is about to be worth less, and nobody has told her what she is worth afterwards. That is not resistance to change. It is an unanswered question about her job.
What shifts it: answer the question she has not asked out loud. “In the new stack you own the migration sequencing and you own the runbook. Nobody else here can do that part.” If you cannot say something true in that shape, then you have a staffing decision to make, and you should make it rather than run a persuasion campaign around it.
Then treat her objections as a checklist rather than an obstacle. Linda’s list of what will break is the most useful change management document in the building, and it exists whether or not she comes round.
What not to do: promise the migration will go smoothly. Over-promising during a change is how managers spend trust they do not get back. Say what will be hard, say when you will know more, and say it on a fixed schedule so people stop having to ask.
Where practicing scenarios stops helping
Scenario practice has a failure mode, and it is worth naming before you spend a weekend on it.
It assumes you are the neutral party. Every scenario above puts you outside the conflict, holding the room. A large share of what a manager actually experiences has them inside it: your report thinks you are the problem, or your peer does, or your boss does. The moves change completely once you are a party to it. You cannot name the decision in dispute neutrally when you are one of the people who wants a particular answer.
It assumes the conflict is about people. Often it is not. Two teams fighting over a shared engineer are not miscommunicating. There is one engineer and two roadmaps that each need a full one. No amount of listening produces a second engineer. In the same CIPD survey, 49% of employers acknowledged that managers themselves can cause conflict in their teams, and a fair share of that is managers who set two incompatible goals and then mediate the collision they created.
Rehearsal can make you worse before it makes you better. A manager who has practiced a full script tends to deliver it on cue regardless of what the other person just said. Once the script is running, listening has stopped. Rehearse the first sentence only. Leave the rest genuinely unplanned.
And some conflicts are not yours to resolve at all. Harassment, discrimination, safety, anything with a real power imbalance running through it: those go to HR, and they go early. Your opening line is not the relevant skill there, and using it delays the thing that should have happened on day one.
Practicing the conversation before you have it
The hard part is rarely knowing what to do. It is saying the sentence out loud for the first time to the actual person, with their actual face in front of you, and having no second take.
That first take is what Merlin, Risely’s AI coach, is there to absorb. Managers use it three ways for conflict:
- Role play. Describe the dispute, name who you are about to talk to, and Merlin takes their side of the conversation, pushback included. You get to fail at your opening line somewhere it costs nothing.
- Situational discussion. For the ones where you cannot yet tell what you are holding. Describe what happened and work out whether this is a handoff problem, a governance problem, or a conduct problem, before you book anything.
- Skill work. The conflict resolution assessment gives you a starting read, and Merlin follows it with daily prompts aimed at whatever came back weakest.
Merlin runs natively inside Slack and Microsoft Teams, so the rehearsal happens where the work already is, in any of 40 languages. It has 5,000+ users coached across 40+ organizations, and anything you start yourself stays private. If you would rather structure the conversation than rehearse it, the conflict management toolkit covers the same ground on paper, and our guide to handling conflict at work sets out the approach underneath all seven scenarios.
Start a free conflict role play with Merlin
The version you have not written yet
Go back to Scenario 1. You have James’s account: marketing keeps changing the brief. Sarah has an account too, and in hers, product is the team that ships changes and tells nobody, which is the whole reason the brief moves.
Every scenario on this page is told from one side. That is not a flaw in how they were written. It is how conflict arrives at your desk. One person reaches you first, and their version becomes the shape of the problem in your head before the other person has said a word. The move that fails in all seven scenarios is the same one, and it happens before the meeting starts: you form a working theory from the first account you heard, then run the conversation to confirm it.
So the practice worth doing is not the one you would expect. Pick the scenario closest to something live on your team right now. Do not draft your opening line for it. Draft the other person’s account of the same events, in their words, including the part where you are the obstacle. Two hundred words is enough.
If you cannot write it, you are not ready to have the conversation, and finding that out takes about ten minutes.