20 team conflict resolution activities, plus 25 scenarios to role-play
Exercises with steps and debrief questions, realistic scenarios for role-play and a script for the real conversation. Written for managers, team leads and trainers.

Good team conflict resolution is a skill a team can practice before it needs it. These 20 conflict resolution activities do that: role-plays, perspective swaps, agreements about how to disagree, and short drills for tense moments. Each lists the time, group size, materials, steps and two debrief questions. Then come 25 workplace conflict scenarios to role-play, each with the other side’s view, a 5-step framework for the real conversation, a 60-minute training session and a plain guide to when a manager should step in.
20 conflict resolution activities for teams
Run them on made-up or past conflicts, never on a live one between two people in the room. Numbered straight through, so a trainer can say number 12.
Role-play and scenario activities
Practice on made-up conflicts so the real ones feel familiar. Use the 25 scenarios further down as the material.
1. Scenario triads
20 minutes · Groups of 3 · Scenario cards from the list on this page · works on video
- In each group, one person raises the issue, one responds as the other side, and one observes.
- Pick a scenario card. The person raising it gets one minute to plan an opening line, then the pair talks for four minutes.
- The observer shares one thing that helped and one moment where it could have gone better.
- Rotate roles twice with a new card each time, so everyone plays every part.
Debrief
- Which role was hardest: raising it, responding or watching?
- What opening line got the conversation off to the best start?
2. Rewind and replay
20 minutes · 6 to 20 people · Two scenario cards
- Two volunteers act out a scenario the wrong way on purpose: defensive, vague, or sarcastic.
- Anyone watching can call rewind at the moment it starts to go wrong.
- The volunteers replay from that line while the person who called rewind suggests a better one.
- Run it twice with different scenarios and new volunteers.
Debrief
- What was the earliest moment someone called rewind, and why then?
- Which replacement line would you actually use?
3. Tag-in fishbowl
25 minutes · 8 to 20 people · Two chairs in the middle of a circle and a scenario card
- Two people sit in the middle and start a scenario while everyone else watches from the circle.
- Anyone in the circle can tap a player on the shoulder, take their seat and carry on with a different approach.
- Keep the scenario going through at least four swaps.
- Close by listing on a board every approach that moved the conversation forward.
On a call: Spotlight two speakers and let others tag in by raising a hand; the facilitator swaps them.
Debrief
- Which swap changed the direction of the conversation most?
- What did you notice from the circle that you miss when you are in it?
4. Cool the thread
15 minutes · Groups of 2 to 4 · A made-up chat thread that has turned heated, printed or shared · works on video
- Share a fictional thread where two colleagues have gone back and forth four times and the tone is sliding.
- Each group writes the one message that would cool it down, in three sentences or fewer.
- Groups read theirs aloud, and the room picks the one it would be glad to receive.
Debrief
- Did the best message move the talk off chat, and was that right?
- At which message in the thread should someone have picked up the phone?
5. Who should handle it?
15 minutes · Groups of 3 to 5 · Eight scenario cards per group · works on video
- Give each group eight cards: six everyday scenarios from the list below and two policy issues, such as a falsified timesheet or a threat made in anger.
- Groups sort each card into three piles: talk to the person directly, ask a manager to help, or take it to HR.
- Compare piles across groups and talk through every card the groups placed differently.
Debrief
- Which card did groups disagree on most?
- What would have to change about a scenario to move it to the next pile?
Perspective-taking activities
Most workplace conflict is two reasonable people seeing different parts of the same problem. These activities for conflict management show the other part.
6. Two truths of a disagreement
15 minutes · Pairs or two small groups · Paper and a pen each · works on video
- Pick a disagreement: a fictional scenario, or a past one both sides are comfortable revisiting.
- Each side writes one true thing about its own view and one true thing about the other side's view.
- Read them aloud, starting with the true thing about the other side.
- Look for where the two truths overlap and write that down as the starting point for a solution.
Debrief
- How hard was it to write something true about the other view?
- Did hearing your view described fairly change how you felt about the disagreement?
7. Swap the week
20 minutes · Pairs from different roles · No materials · works on video
- Each person describes the other's typical week, as they imagine it: the pressures, the deadlines, the requests.
- The other person then corrects it: what was right, what was missing, what is harder than it looks.
- Each names one thing they will do differently now that they know the other's week.
Debrief
- What surprised you most about the other person's week?
- Which of our recurring frictions makes more sense now?
8. Inbox swap
30 minutes · Two teams that work together · A board split down the middle · works on video
- Each team writes the requests it thinks the other team receives in a normal week, and from whom.
- Each team then writes its real list, and the two versions go side by side.
- Circle the requests one team didn't know the other was handling.
- Agree on one change to how the two teams ask each other for things.
Debrief
- Which invisible request explains a past conflict between our teams?
- How will we ask each other for things from now on?
9. Three witnesses
20 minutes · Groups of 3 · A short made-up incident, one paragraph long · works on video
- Read a short incident, such as a customer order that shipped late after a last-minute change.
- Each person in the group retells it as one person involved: the customer, the account manager, the warehouse lead.
- Compare the three versions and list what each witness knew that the others didn't.
Debrief
- Which witness had the most information, and which had the least?
- Who usually gets blamed in a story like this, and is that fair?
10. Value cards
20 minutes · 4 to 12 people · Cards with one value each: speed, quality, fairness, safety, cost, customer, autonomy, consistency · works on video
- Name a decision the team disagrees about, or use a scenario card.
- Each person picks the one or two value cards that drive their position.
- Lay the cards out together. Most disagreements turn out to be a trade-off between two good values.
- Discuss which value should win in this case, and what would make the other value feel respected.
Debrief
- Did seeing the values change the conversation from who is right to what matters most?
- Which value does this team tend to overlook?
Team agreements that prevent conflict
Run these while things are calm. A team that has agreed how to disagree argues less about how the argument went.
11. Team conflict charter
40 minutes · One team, 4 to 15 people · A shared doc or a large sheet of paper · works on video
- Answer five questions together: where we disagree (in the meeting, not after it), how we raise an issue with each other, when we move a heated chat to a call, how long we wait before replying when angry, and who we go to if two people are stuck.
- Write one plain sentence per answer.
- Everyone reads the charter and says whether they can live with it; reword anything someone can't.
- Pin it in the team channel and review it every six months or after a big conflict.
Debrief
- Which line will be hardest for us to keep under pressure?
- What would we have done differently in our last disagreement with this charter in place?
12. Disagree and commit practice
20 minutes · 4 to 12 people · No materials · works on video
- Pick a low-stakes decision with two real options, like the format of the weekly meeting.
- Everyone states their preference and one reason, in one sentence each, with no rebuttals.
- The decision owner decides and says why. Anyone who disagreed says out loud: I disagree, and I'm in.
- Agree what would make the team revisit the decision, such as a date or a result.
Debrief
- How did it feel to say I disagree, and I'm in?
- What do people need to hear before they can commit to a decision they argued against?
13. Handoff friction map
30 minutes · People from two or more roles · A board and sticky notes · works on video
- Draw the steps a piece of work goes through between the roles, from request to done.
- Everyone puts a note on each step where friction happens: waiting, missing details, rework.
- Pick the step with the most notes and redesign it: a template, a checklist, a clear owner.
Debrief
- How much of our conflict was about the process rather than the people?
- Who owns the fix, and when do we check it worked?
14. Hot topic meeting setup
10 minutes · Anyone in a meeting about a contested topic · No materials · works on video
- Before the topic starts, agree four rules: one speaker at a time, criticize ideas not people, questions before objections, and anyone can call a two-minute break.
- Name a timekeeper and a note-taker who are not the decision owner.
- Put a parking lot on the board for anything off-topic or too big to settle today.
Debrief
- Did we keep to the four rules, and which one slipped?
- What is in the parking lot, and when will we deal with it?
15. Working-together check-in
15 minutes · Pairs who work closely · No materials · works on video
- Each person answers three prompts: what helps me work well with you, what makes it harder, and one request.
- The listener only asks questions to understand; no defending.
- Each agrees to one request and both put a date in the calendar to check in again in a month.
Debrief
- Was the request you heard easy to agree to?
- What small friction did this catch before it became a conflict?
Conflict resolution games and skill drills
Short, repeatable practice for the moments that decide whether a disagreement cools down or heats up.
16. Agreement first
15 minutes · Pairs · Scenario cards · works on video
- Each pair takes a scenario card and plays the two sides.
- Before they argue anything, they race to find three points both sides agree on.
- Only then do they discuss the difference, starting from what they agreed.
- The first pair to agree on a next step wins the round.
Debrief
- Did finding agreement first make the difference feel smaller?
- Which kinds of points were easiest to agree on?
18. Apology rewrite
15 minutes · Pairs, any number · Four weak apologies on cards · works on video
- Hand out weak apologies, like "Sorry if anyone was upset" and "Sorry, but I was swamped."
- Pairs rewrite each in four parts: what I did, the effect it had, what I will do differently, and no but.
- Read the rewrites aloud and pick the one that sounds most like a real person.
Debrief
- Why do but and if take the force out of an apology?
- When is a short apology better than a long one?
19. Reset phrases practice
15 minutes · Groups of 3 or 4 · The phrase list below on a card · works on video
- Share six reset phrases: let me try that again; can we slow down; I think we want the same thing; what am I missing; I need a minute; let's write down what we agree on.
- One person plays a scenario heating up while another practices dropping in a reset phrase at the right moment.
- Swap so everyone tries at least two phrases, then each person picks the one that sounds most like them.
Debrief
- Which phrase felt natural, and which felt scripted?
- When in a real meeting would you use yours first?
20. After the storm review
30 minutes · The people involved, with a neutral facilitator · A board with three columns · works on video
- A few weeks after a conflict is resolved, meet to look back, not to reopen it.
- Fill three columns: what made it escalate, what helped it settle, and what we would do earlier next time.
- Turn the last column into one change to the team conflict charter.
Debrief
- What was the first sign of this conflict, and who noticed it?
- What would have settled it a week sooner?
These pair well with listening practice. Our active listening activities and communication activities cover paraphrasing, I-statements and clear requests, so this page leaves those out.
25 conflict resolution scenarios for role-play
Realistic, everyday and never personal: real-life examples of conflict to practice resolving. Each comes with the other side's view, so the person playing it has a real case to make. Change details to fit your workplace, but never base one on a live conflict between people in the room.

Workload and ownership
- After a reorg, you and a teammate both believe you own the same project.Their side: They were told by their manager that the project moved to them last month.
- A colleague's handoffs keep reaching you a day late, so your work starts late.Their side: They are waiting on approvals from another team that keep slipping.
- Two teammates want the same vacation week during the busiest month.Their side: Both booked travel before the busy period was announced.
- A peer keeps reopening a decision the team already made.Their side: They have new information they think the team never considered.
- A colleague left, and two people disagree on how to split their client accounts.Their side: Each believes their existing relationships make them the better fit.
- Your teammate rewrote your document without asking you first.Their side: They thought they were saving you time before a deadline.
- A senior colleague is frustrated that a new hire asks them every question.Their side: The new hire was told this colleague is the person to ask.
Communication and credit
- A coworker presented work you did together and didn't mention you.Their side: They were asked for a quick update and didn't think of it as a presentation.
- A peer's one-word replies to your messages feel curt.Their side: They answer on their phone between meetings and mean nothing by it.
- A colleague gave you critical feedback in front of the whole team.Their side: They thought the team needed to hear it, since it affected everyone's work.
- A teammate stays silent in a project thread for days, then objects at the deadline.Their side: They didn't realize they were expected to review until the final call.
- Your idea was dismissed quickly in a brainstorm and you felt shut down.Their side: The person who dismissed it knew of a similar idea that had failed before.
- Someone keeps posting urgent requests in the general channel instead of the request queue.Their side: Requests in the queue have gone unanswered for days.
Meetings, space and remote work
- One person regularly talks over others in the weekly meeting.Their side: They feel the meeting drags and are trying to keep it moving.
- A colleague keeps booking meetings over the focus time on your calendar.Their side: Your calendar shows the only open slots that fit everyone else.
- A remote colleague feels left out of decisions made in the office.Their side: Office staff didn't realize hallway conversations were turning into decisions.
- A teammate takes calls on speaker in the open office.Their side: Every meeting room is booked, and their headset is broken.
- Someone books the only large meeting room every week just in case.Their side: Their workshop got bumped twice when they didn't book ahead.
- The overnight handoff from a teammate in another time zone keeps missing details you need.Their side: They write it at the end of a long day, and nobody has told them what is missing.
Between teams
- Sales promised a customer a feature that the product team hasn't planned.Their side: Sales was told on a call that the feature was on the roadmap.
- Two teams want the same budget for next quarter.Their side: Each team has a project its leadership already approved.
- Two leads give your team conflicting instructions on the same project.Their side: Each lead believes they are the decision owner.
- A contractor and an employee disagree on who approves the final design.Their side: The contract says one thing and the team's habit says another.
- Support feels engineering ignores the bug reports it files.Their side: Engineering can't reproduce most of them, because the reports arrive without steps or screenshots.
- Finance rejected an expense your team was told was approved.Their side: The approval came from someone without budget authority.
A 5-step framework for team conflict resolution
For the real conflict resolution meeting between two people. Each step has phrases to borrow; say them in your own words.
1. Ask for a time, privately.
Not in the meeting where it happened and not over chat. Give them a heads-up on the topic so nobody is ambushed.
“Do you have 20 minutes this week? I'd like to talk about how our handoffs are going.”
“Can we grab a few minutes after lunch? Something from this morning's meeting is on my mind.”
2. Describe what happened, not who they are.
Stick to what a camera would have seen and how it affected the work. Leave out always, never and guesses about motives.
“The last three handoffs reached me after noon on Thursday, so testing slipped to Friday.”
“In the review, my section was cut before I'd finished explaining it.”
3. Ask for their side, and listen to all of it.
Assume there is a piece you can't see. Don't plan your reply while they talk; summarize what you heard before you answer.
“How does it look from your end?”
“So the approvals are landing late for you too. Is that right?”
4. Find the shared goal, then the options.
Name what you both want, then put two or three options on the table before choosing one.
“We both want the release out on Friday without a weekend scramble.”
“What if we tried a Wednesday cutoff, or split the handoff in two?”
5. Agree on one next step and a check-in.
Say it back so you both leave with the same version, and set a date to see if it worked.
“So you'll send the draft by Wednesday, and I'll flag anything missing the same day. Check in next Friday?”
“Let's try it for two weeks and see if it helps.”
Handling these conversations well is one of the qualities of a good leader, and our leadership activities include a set on conflict styles and mediating between two people.
A 60-minute conflict resolution training session
For one team of up to about 20, in a room or on a call with breakout rooms for the triads. No outside trainer needed.
| Start | What to run |
|---|---|
| 0:005 min | Opening round. Each person finishes the sentence: a disagreement at work goes well when... |
| 0:0510 min | The 5-step framework. Walk through the five steps on this page and read one sample phrase for each. |
| 0:1520 min | Scenario triads. Use scenarios from the list above that match your team's real friction, without naming anyone. |
| 0:3515 min | Two truths of a disagreement. Run it on a fictional scenario first. |
| 0:5010 min | Commitments. Each person picks one phrase from the framework to use this month. The team books 40 minutes for the team conflict charter. |
When a manager should step in, and when to bring in HR
Most disagreements are best settled by the two people involved. A manager should step in when:
- The two people have tried to sort it out themselves and it keeps coming back.
- It is affecting other people, deadlines or customers.
- One person has power over the other, such as a lead and someone they assign work to.
- Either person asks for help.
- The conflict has gone quiet in a bad way: people avoid each other or route work around one another.
How to step in
- Meet each person alone first. Hear each side without the other in the room, and ask what a good outcome looks like to them.
- Then bring them together. Use the five steps above, with you keeping time and keeping it on behavior and work.
- Decide what is yours to decide. If the conflict is about priorities or ownership, make the call and explain it rather than asking two people to negotiate it.
- Follow up. Check in with both a week or two later, separately.
Teams that know each other well tend to disagree more openly and recover faster. Our guide to team camaraderie covers the everyday habits behind that.
Want an expert to run conflict resolution training?
Psychological Safety in the Workplace is a live 60-minute session on building a team where people feel safe to speak up, give feedback and take risks, the ground any conflict resolution work stands on. It runs on Zoom by default. See all our live team building workshops, book about 2 weeks ahead, or get a free quote.
Two more for the same goal: a workshop on leading with courage and authenticity, and a talk by psychiatrist Dr. Ellen Vora on emotional intelligence.
