The 20 scenarios below are practice ideas, not customer case studies or a test of anyone’s personality. Start with an everyday work disagreement. People can observe, write a response, or pass.
Choose a conflict scenario for your team
- Deadlines and workload: scenarios 1, 2, 7, 11, and 16.
- Meetings and communication: scenarios 3, 4, 8, 12, and 15.
- Decisions and ownership: scenarios 5, 6, 9, 13, and 20.
- Feedback and working relationships: scenarios 10, 14, 17, 18, and 19.
How to run a 15-minute role-play
- Choose a fictional situation relevant to the work. Avoid reenacting an active personal dispute in front of the team.
- Spend two minutes reading the roles. Each participant writes down what they need and what they can change. Invite a third person to observe.
- Play the conversation for four minutes. Ask about the other person’s constraints before offering a solution.
- Debrief for four minutes. The observer describes specific words and actions, without rating anyone’s personality.
- Repeat the opening for three minutes using one improvement.
- Use the last two minutes to record a working agreement and a date to review it.
The times are a suggested facilitation plan, not a validated requirement. If you get stuck, try: “Here is what I noticed. Here is the effect on the work. What am I missing, and what can we agree to do next?”
20 workplace conflict role-playing scenarios
1. Two deadlines, one available person
Roles: a project lead and a specialist shared by two projects.
Situation: both projects need a full day of the specialist's time before tomorrow. The lead promised a delivery date. The specialist cannot meet both commitments.
Practice: explain the trade-off without promising extra hours. Identify who can decide which deadline moves.
Finish with: a priority order, the decision owner, and a message to the affected project.
Debrief: did you surface the capacity constraint before discussing effort?
2. A handoff arrives incomplete
Roles: the person handing off a task and the teammate receiving it.
Situation: the work arrives on time, but two required files are missing. The recipient must either wait or make assumptions.
Practice: describe what is missing and its effect without calling the other person careless. Ask what made the handoff difficult.
Finish with: a short handoff checklist and a deadline for the missing information.
Debrief: what would make “ready to hand off” observable?
3. An urgent message goes unanswered
Roles: a teammate who needs a quick answer and a teammate doing focused work.
Situation: one person sent several chat messages. The other checks chat at set intervals and did not know the request was urgent.
Practice: separate the urgency of this request from assumptions about responsiveness.
Finish with: an agreed urgent channel, expected response window, and backup contact.
Debrief: was there a shared expectation before the disagreement?
4. The same voices dominate meetings
Roles: a meeting facilitator and a frequent contributor.
Situation: two people speak through most discussions. Written input from others arrives after decisions are made.
Practice: explain the participation pattern without treating quietness or confidence as a measure of contribution.
Finish with: a silent writing period before discussion and a way to submit input ahead of time.
Debrief: did the proposed format give people more than one way to contribute?
5. A decision keeps reopening
Roles: a decision owner and a teammate raising a late objection.
Situation: the team chose an approach last week. New information may affect it, but repeated reconsideration is delaying delivery.
Practice: ask what changed and distinguish new evidence from an unchanged preference.
Finish with: the decision, the evidence that could reopen it, and who makes that call.
Debrief: how can the team preserve both challenge and forward movement?
6. Quality and speed pull in different directions
Roles: a delivery lead and a quality reviewer.
Situation: a small release is due today. The reviewer found a defect. The lead thinks it is acceptable; the reviewer does not.
Practice: describe the concrete impact and affected users. Separate release requirements from optional polish.
Finish with: a named release decision owner and an explicit fix, defer, or stop decision.
Debrief: did you agree on the decision criteria before arguing about the answer?
7. “One small request” changes the plan
Roles: a stakeholder and a project owner.
Situation: the stakeholder adds a request after the team committed to a delivery scope. It sounds small but requires work from three people.
Practice: explain the dependencies and offer a choice between scope, timing, or another priority.
Finish with: what is included, what moves, and who informs the team.
Debrief: did either person make a commitment without checking its consequences?
8. Someone is interrupted repeatedly
Roles: a teammate presenting a concern and a colleague who keeps responding before they finish.
Situation: both want to solve the problem. The presenter feels unheard. The colleague thinks they are helping the discussion move faster.
Practice: name the behavior and make a specific request, such as finishing a short explanation before questions.
Finish with: a meeting rule the facilitator can apply consistently.
Debrief: did you describe what happened rather than guessing the other person's intent?
9. Two departments optimize for different goals
Roles: a sales lead and an implementation lead.
Situation: a customer wants an accelerated start. Sales wants to secure the opportunity. Implementation has no capacity in that week.
Practice: make both constraints visible and compare realistic options.
Finish with: a customer commitment approved by the people responsible for delivering it.
Debrief: which shared outcome helped move the discussion beyond departmental targets?
10. Feedback is too vague to use
Roles: a reviewer and a teammate receiving feedback.
Situation: the feedback is “Be more strategic.” The recipient does not know what behavior should change.
Practice: ask for a specific example, the expected outcome, and one alternative action.
Finish with: one observable behavior to practice and a date to discuss an example.
Debrief: could someone tell from the agreement whether anything changed?
11. A colleague asks for help when you are at capacity
Roles: a teammate requesting support and a teammate with a full workload.
Situation: the request is reasonable, but accepting it would put another commitment at risk.
Practice: state the capacity limit and explore a smaller contribution, different timing, or another source of support.
Your rapid TeamDynamics · two minutes
What makes your team tick?
Start with how your meetings work. Answer 12 quick questions for a first look at how your team communicates, makes decisions, and gets things done.
When we have team meetings…
Question 1 of 12 · Choose an answer to startFinish with: exactly what help is available and who owns the remaining work.
Debrief: did a polite response create an accidental promise?
12. Written comments sound harsher than intended
Roles: an author and a reviewer commenting on a draft.
Situation: short comments such as “Wrong” and “Why?” have made the author defensive. The reviewer thought brevity would save time.
Practice: discuss a specific comment and replace it with a question or explanation tied to the work.
Finish with: a feedback format and a point at which to switch from comments to a conversation.
Debrief: what information was missing from the original message?
13. Ownership is unclear after a meeting
Roles: two teammates who each thought the other owned a follow-up.
Situation: a task is now overdue. Neither person remembers an explicit owner being assigned.
Practice: reconstruct the agreement without turning the discussion into a memory contest.
Finish with: one owner, a due date, and a place to record future follow-ups.
Debrief: what could the team have recorded at the end of the meeting?
14. Credit for a shared result feels uneven
Roles: a teammate who presented a result and a colleague whose contribution was omitted.
Situation: a presentation mentioned the speaker's work but did not acknowledge the colleague's analysis.
Practice: explain the specific omission and ask for a proportionate correction. Give the presenter room to explain what happened.
Finish with: a correction to the relevant audience and an approach to attribution next time.
Debrief: was the request clear about what would repair the situation?
15. Remote participants miss part of the decision
Roles: an in-room facilitator and a remote participant.
Situation: an important discussion continues after the video call ends. Remote teammates learn about the decision later.
Practice: explain the information gap without making assumptions about intent.
Finish with: a rule for recording decisions and including remote input before a decision is final.
Debrief: who needs to know what, and by when?
16. A recurring deadline is missed
Roles: a task owner and a teammate depending on the output.
Situation: the same weekly deliverable has arrived late three times. The recipient is having to replan their work.
Practice: discuss the pattern, identify the constraint, and avoid accepting a new date without a feasible plan.
Finish with: a realistic deadline, an early warning point, and an escalation route if the dependency slips.
Debrief: did the plan change, or did you only repeat the expectation?
17. A public correction embarrasses a colleague
Roles: a colleague who corrected an error in a meeting and the person corrected.
Situation: the correction was accurate, but the delivery felt personal and derailed the discussion.
Practice: acknowledge the need for accurate information while discussing how to challenge the work respectfully.
Finish with: a phrase for raising a correction and a way to handle sensitive feedback privately.
Debrief: did the agreement preserve the ability to correct important mistakes?
18. Experience is treated as a veto
Roles: an experienced teammate and a newer colleague proposing an alternative.
Situation: “We tried that before” ends the conversation. The newer colleague thinks the constraints have changed.
Practice: ask what happened previously, what is different now, and what a small test would need to show.
Finish with: a test, a reason to decline it, or a clear next step to gather missing information.
Debrief: did you use experience as evidence that can be examined?
19. A working-style difference becomes a personal label
Roles: a teammate who wants a written brief and a teammate who prefers to start with discussion.
Situation: each describes the other as difficult. They need to plan a piece of work together.
Practice: replace labels with specific needs. Ask what minimum preparation would make the discussion useful.
Finish with: a short brief before the meeting and time to explore unanswered questions together.
Debrief: did either person have to defend their personality rather than explain what helps them work?
20. An escalation surprises the task owner
Roles: a task owner and a colleague who raised a delivery risk with their manager.
Situation: the colleague was worried about a deadline. The task owner felt bypassed and did not know an escalation was coming.
Practice: explain the risk and the communication gap separately. Discuss when immediate escalation is necessary and when a direct conversation can happen first.
Finish with: an escalation threshold, who is informed, and how the next update will be shared.
Debrief: would both people recognize the threshold in a future situation?
Questions for the observer
- What did each person need, and which facts were missing?
- When did the conversation move from assumptions to questions?
- What did the final agreement specify?
- What would you change in the opening minute?
Turn practice into one working agreement
Complete this sentence together: “When [situation] happens, [owner] will [action] by [time], recorded in [place]. We will review it on [date].”
For example: “When a handoff will miss its deadline, the task owner will tell the recipient before noon on the previous working day and propose a revised plan in the project tracker.”
Keep the agreement small enough to try. Use the team norms worksheet to record it. At the review, ask whether it helped the real work and change it if the problem persists.
When you are ready to address a real collaboration issue, use the conflict-to-agreement playbook. It connects the team’s working patterns with a specific conversation, an agreement, and a review date.
When a role-play is not the right next step
A practice exercise should not replace a private conversation about an unresolved personal dispute. Handle complaints, misconduct, and urgent safety concerns through the appropriate support process. Do not ask colleagues to disclose sensitive experiences or perform a conflict they do not want to revisit.
Connect the exercise to how your team works
TeamDynamics describes shared team behaviors across Communicating, Processing, Deciding, and Executing. Use the result to choose a habit to discuss, such as how urgent information is shared or how decisions are recorded. Personal preferences separately inform private CoDynamics; they do not determine the shared team result.
An assessment does not settle who is right in a disagreement. Combine it with concrete work examples, then agree on a change you can observe. Preview the Team Discussion Guide or use the guide to resolving team conflicts to plan the follow-up.
