Role Play Scenarios for Managers: 15 Difficult Conversations to Rehearse

Role play has a bad name and it earned it. For most people the whole experience is one training room: a colleague you like, a scenario card, and a partner who caved in ninety seconds.

You said your opening line. They said "you know, that's fair, I've been meaning to work on that." You sat down having learned that you can do this. It was not true.

A rehearsal that goes well on the first pass is a demonstration. Everything worth practicing happens after the other person refuses your framing, which is where most managers find their script has run out.

Below are fifteen scenarios you can run with a partner or alone, each with the part most lists of difficult conversations at work leave out: what the person playing the counterpart is supposed to do.

The four rules that make it work

The partner has to resist. Not forever, and not by being unreachable. Give them a written position and three deflections, the ones below, and have them hold it until the manager earns a move. A partner who does not know what their character believes defaults to agreeing with you.

Say the words, do not describe them. "Then I'd probably tell him the follow-up was missed twice" is a plan, not practice. Practice is saying "the follow-up window was missed twice in June" out loud, while somebody watches your face. The gap between the two is what you are here to close.

Stop and restart when you fumble. Most role play is run like a performance: push through, then discuss. Run it like a music rehearsal instead. The moment a line comes out hedged, stop and take it again.

Score it against something specific. "That was good" teaches nothing. Two axes out of ten. Clarity and directness: was the topic named in the first sentence, was there one piece of evidence. Listening and empathy: did you ask anything, did you leave silence, did anything they said change what you did. Nine and four is a problem you can work on. Went fine is not.

Scenarios where you carry the bad news

Four where you know the content and the difficulty is delivery.

Hard feedback to a high performer

The setup. Your strongest designer gives the most useful critique on the team. Two juniors have stopped bringing work to review.

The role brief. Your standards are why the work is good. Accept the point warmly, commit to nothing, ask who complained.

Your goal. Keep the critique, name the effect, leave with one behavior that changes Monday.

A good run ends with the designer naming what they will do differently.

The underperformer you have been avoiding

The setup. Two quarters of missed follow-ups, and nobody has told the person there is a problem.

The role brief. Be surprised, then hurt. Nobody said anything at the last review, which is true. Ask whether this is a warning and refuse a vague answer.

Your goal. Say the word underperformance, own the delay, leave with a written standard and a date.

A good run ends with both of you naming the same three things next month has to show.

Denying a promotion

The setup. Your report has been telling people they are up for senior. They are not, and the gap is real.

The role brief. You came with evidence: the projects, the hours, two people promoted with less. Ask what is missing, and if the answer is vague, ask again.

Your goal. Give the decision in the first thirty seconds, name the gap, promise no timeline you cannot keep.

A good run ends with them repeating the missing piece accurately after you leave.

A raise you cannot give

The setup. A solid performer asks for twelve percent. The budget closed last month and the answer is no for two quarters.

The role brief. You have market data and you are polite about it. Treat no budget as a decision, not a fact. Mention once that a recruiter called.

Your goal. Give the real no, keep the person, turn the no into a specification with a date.

A good run ends with a date agreed and nobody pretending it was a yes.

Scenarios about work and boundaries

These three fail quietly. You leave with the work still on your desk.

Delegation that boomerangs

The setup. You handed off the vendor review three weeks ago. It has come back twice as a request to decide, dressed as a question.

The role brief. Be helpful and slightly anxious. You want to check in, just to be safe. Every time the manager answers, ask a smaller question.

Your goal. Hand the decision back without withdrawing support. Say who owns it and what you will review.

A good run ends with the report naming the decision and the day they will make it.

Saying no to a peer org

The setup. A sales director wants two of your engineers for three weeks. They do not manage you, and the case is good.

The role brief. You are senior, friendly and used to hearing yes. Frame it as agreed elsewhere, invoke the client twice, offer to take it to the VP if the no holds.

Your goal. Say no once, in a sentence, then offer the smaller thing you can do. Same shape as saying no to your boss, without the reporting line.

A good run ends with a no that survives the escalation.

A peer who took credit

The setup. Your analysis, presented to leadership by a peer, with the word we doing a lot of work in the retelling.

The role brief. You are not a villain. You presented what you saw as team work. Suggest, kindly, that the manager is being territorial.

Your goal. State what happened, ask for a specific repair, stay off motive.

A good run ends with an agreement about next time, not an admission about last.

Scenarios that point up the org chart

Easy in your kitchen, hard in front of someone who decides your next level.

Disagreeing with a VP

The setup. A VP picked a launch date you believe is two months early. You have the data, and the decision is close to final.

The role brief. You are not hostile, you are busy. Ask for it in one sentence, push on cost, mention the date is already in the board deck.

Your goal. Disagree in the first sentence, give one reason and one alternative, then stop.

A good run ends with a decision you could carry out loud, even one that went against you.

Asking for a raise

The setup. You are asking this time. Your scope grew by a team and a system. Your salary did not.

The role brief. Be warm and non-committal. Use "let me look into it", then "there's no budget this cycle", then "that number is high". Never say no outright.

Your goal. Name one number, hold the silence after it, leave with a date.

A good run ends with the number said flat and once, no hedge attached.

Scenarios where you are the messenger

You did not make the decision. You still have to own it, and the tell is the word they.

Delivering a decision you disagree with

The setup. Leadership killed the project your team spent a quarter on. You argued against it and lost.

The role brief. You want to know whether the manager agrees. Ask directly, twice. Any hedge is permission to keep fighting it upward.

Your goal. Deliver it as yours, share what reasoning you can, and recruit nobody into your objection.

A good run ends with the team clear on the decision, not on your opinion of it.

Announcing a change the team will hate

The setup. Three days a week in the office, starting next month. You found out yesterday. You have twenty minutes on a team call.

The role brief. With three people, make one openly annoyed, one silent, one relentlessly reasonable. Ask the questions with no good answer: who decided, was anyone consulted, what if I do not.

Your goal. State the change in the first sentence and take questions without inventing answers. "I don't know, I'll find out by Thursday" is allowed.

A good run ends with the hard question asked in the meeting, not in a private channel.

Scenarios where the room gets emotional

The hardest to rehearse, because your instinct is to make the feeling stop.

The report who has gone quiet

The setup. Six months ago they volunteered for everything. Now they deliver exactly what is asked, camera off, no opinions in review.

The role brief. Say you are fine. Say it three times, three different ways. Open up only if the manager asks something specific and then stays quiet.

Your goal. Name what you have observed, ask one open question, let the silence run.

A good run ends with one true sentence you did not have before.

The report who cries

The setup. Twenty seconds into ordinary feedback, they start crying. The feedback is fair and you are not taking it back.

The role brief. You are embarrassed, not manipulative. Apologize for crying, insist you are fine, try to end the meeting early.

Your goal. Stay in the room, name it in one sentence, pause, finish without softening the content.

A good run ends with the feedback delivered and a break offered, not a meeting abandoned.

The report who gets aggressive

The setup. You raise a missed commitment and it comes back hard: at your management, at the team, at whether any of this is fair.

The role brief. Interrupt. Raise your voice a little. Make it personal exactly once. Stay inside what a real person does with the door open. If they are also your best performer, run the toxic high performer version separately.

Your goal. Do not match the volume and do not retreat. Name the behavior, hold the topic, be ready to end the meeting.

A good run ends with the original subject still on the table once the temperature drops.

The apology you owe

The setup. You criticized someone in front of two colleagues. You were right about the content and wrong about the room.

The role brief. Accept the apology quickly, then stay cold. If the manager fishes for reassurance, hand it over and mean none of it.

Your goal. Say what you did, name the impact without "if" and without "you felt", ask what would make it right.

A good run ends with a specific repair, not with you feeling better.

Running these without a partner

Almost nobody has a partner who will do this properly twice. Alone works on one condition: out loud, and recorded. In your head, the counterpart always agrees with you.

Listen back for three things. Where you hedged. Where your voice went up and turned a statement into a request. How many words you spent before the subject arrived, which is the easiest of the three to fix.

This does not work if the scenario is not yours. Practising a generic underperformer teaches you a script for a person who does not exist, and the real one has a name, a history with you and one sentence that will throw you. Write that sentence into the scenario before you run it.

What a friendly partner cannot give you

A colleague running these scenarios wants you to succeed. They know what you meant, they finish the half sentence you left hanging, and they stop resisting around the moment they sense you getting frustrated. That is the help a real counterpart will not give you. The person across the table has only your actual sentences, and is listening for the escape hatch in them. Anything that takes the friendliness out gets you a truer read: a stranger, a partner briefed to hold position, a recording you are honest about, an AI counterpart with no reason to be kind about a hedge.

You can read all fifteen of these in ten minutes and be exactly as good at the conversation as you were before. The scenarios are not the thing. Saying the words with your heart rate up, hearing them land badly and taking the line again is the thing, which is why they are written as instructions rather than examples. How to practice a difficult conversation before you have it covers the reps, the timing, and the hour before.