10 Difficult Conversation Scenarios for Managers (From Someone Who Builds Them for a Living)

Designing difficult conversation scenarios is my actual job. I founded Real Talk Studio, where organisations use AI roleplay to let people practise conversations they'd otherwise walk into cold. Which means I've read a very large number of transcripts of real people attempting their hardest conversations.

The single biggest thing those transcripts have taught me: everyone avoids the same sentence.

Every difficult conversation has one sentence it exists to deliver. "Your role is at risk." "That comment wasn't okay." "This isn't working." People will do almost anything to avoid saying it. They circle it, soften it, bury it in paragraph four. And the conversation stays difficult precisely as long as the sentence stays unsaid.

The ten scenarios below are drawn from what we've built and what I've watched. For each: the setup, where people go wrong, and what good sounds like. Use them for self-rehearsal, peer role play, or training design. They're free to steal.

If you want the book-level playbook first, start with Crucial Conversations, Fierce Conversations, or Radical Candor. This page is what those books look like when they become a meeting.

1. The underperformer who's also a friend

The setup. A team member you genuinely like has been missing the bar for two months. You've hinted. They haven't caught the hints, because hints are designed not to be caught.

Where people go wrong. They open with fifteen minutes of warmth to cushion the blow, and the other person leaves the meeting genuinely unsure whether they've been given feedback at all. I've read transcripts where the feedback recipient thanks the manager for "a lovely catch-up".

What good sounds like. "I need to talk to you about your work, and because I respect you, I'm going to be direct. The last two months haven't been at the standard you set before. What's going on?" Care shown through clarity, not instead of it.

2. The first team meeting after a redundancy announcement

The setup. The email went out an hour ago. Some colleagues are at risk. You have to stand in front of the team, and you don't have the answers they want.

We built this as a team simulation with four AI characters, because real rooms don't take turns: someone scared and demanding numbers, someone angry and hunting for blame, someone who's checked out, and someone insisting it's all fine.

Where people go wrong. They over-promise to soothe the room. "I'm sure everyone will be fine" is a sentence you can't cash.

What good sounds like. Name what's true, hold the line on what you don't know, give the next concrete step. "I don't know who's affected yet. That's the truth. What I can tell you is when we'll know, and what I'll do with that information the moment I have it."

For the conversation with the person whose role is actually at risk, see how to tell an employee they're being made redundant.

3. Shutting down "banter" that's crossed a line

The setup. Mid-meeting, a joke lands at a junior colleague's expense. A second colleague amplifies it. The target laughs, the way people laugh when they don't feel they have another option. Everyone looks at everything except you.

Where people go wrong. They wait for a "better moment", and the moment never arrives. In the simulation we built of this, the jokes escalate if unchallenged, because that's exactly what happens in real rooms. Silence reads as permission.

What good sounds like. Immediate, brief, unheated. "Let's leave that there. Not the place. Where were we on the timeline?" Ten words in the moment beats a paragraph in private tomorrow, though the private follow-up matters too.

4. Saying no to your boss

The setup. Your director catches you at the end of a meeting: "One more thing before you go." A three-week workstream, presented as a favour. They treat anything short of a clear no as a yes.

Where people go wrong. They believe they've declined when they've actually said "I'll see what I can do". Read that sentence from the other side: it's a yes with a delay on it.

What good sounds like. A no with a choice attached. "I can't take that on without dropping something. Which would you like me to drop?" You're not refusing to help. You're refusing to pretend capacity is infinite.

This is one of the five conversations I prepare every new manager for. It shows up earlier than most people expect.

5. Holding your price under commercial pressure

The setup. A buyer you've worked with for years demands a discount and mentions, almost casually, that they're reviewing the range. One number, one threat, one relationship on the line.

Where people go wrong. They concede in the first sixty seconds to make the tension stop. The tension is the negotiation. Ending it early just means paying for its absence.

What good sounds like. Hold the number, trade the structure. "I can't move on price. What I can do is put weight behind the promotion in other ways. Let's talk about what would actually move volume for you."

Sales teams who need more of this, worked as drills: sales role play scenarios that actually prepare reps.

6. The pay rise you have to decline

The setup. A good performer asks for a raise. Budget says no. They deserve a better answer than "budget says no", but that's also the truth.

Where people go wrong. They blame invisible forces ("my hands are tied") which protects the manager and abandons the employee. The employee leaves with no path, only a wall.

What good sounds like. The honest no plus the real path. "The answer right now is no, and I want to be straight about why. Here's what would need to be true for it to be yes, and here's what I'll do on my side."

7. The colleague whose personal struggles are affecting the team

The setup. Something's clearly wrong in a team member's life. Their work is slipping and others are covering. Compassion and accountability are pulling in opposite directions.

Where people go wrong. They pick one. Full compassion mode ignores the team quietly absorbing the load. Full accountability mode is cruelty with a process behind it.

What good sounds like. Both, held separately. "I can see things are hard right now, and I want to support you properly. I also need to be honest that the team's carrying extra, so let's work out what support looks like and what a realistic bar is for the next month."

8. Escalating a concern your own manager doesn't want to hear

The setup. You've spotted a problem, maybe a compliance risk, maybe a doomed project, and the person you report to would prefer you hadn't.

Where people go wrong. They present the concern so tentatively that it's easy to dismiss, then feel unheard. Hedged delivery invites the brush-off it fears.

What good sounds like. Specific, documented, calm. "I want to flag something formally. Here's what I've seen, here's the risk if I'm right, and here's what I think we should check. I'd rather raise it now and be wrong than stay quiet and be right."

9. The customer conversation that starts hostile

The setup. They're angry before you've said a word. The first twenty to forty seconds decide whether you get a conversation at all. That figure comes from work we've done with contact-centre teams: the opening window is where calls are won or lost.

Where people go wrong. They meet objections head-on and argue, or fold instantly and give the shop away. Both are ways of not listening.

What good sounds like. Sidestep the stock objection, not the person. Acknowledge, then move: "Completely understand, you weren't expecting this call. Thirty seconds and then you can tell me to get lost. Fair?"

10. The apology you owe someone

The setup. You got it wrong. Publicly, or in a way that cost someone.

Where people go wrong. "I'm sorry if you felt..." An apology for their feelings rather than your actions, which everyone recognises as no apology at all.

What good sounds like. Own the act, skip the "if". "I was wrong to say that in the meeting. It undermined you in front of the team, and I'm sorry. Here's what I'll do differently."

How to actually use these scenarios

Reading scenarios is scouting. Practising them is training. A few ways to get the reps in:

Solo rehearsal, out loud. Write the one sentence each conversation exists to deliver, then say it to an empty room until it stops feeling impossible.
Peer role play. Give your partner the setup and one instruction: "don't make it easy for me". The politeness of colleagues is the weakness of this method.
AI simulation. This is what we build at Real Talk Studio: characters who push back, get emotional, interrupt, and occasionally hang up on you if you break their trust. No audience, unlimited attempts, feedback on what you actually said.

However you practise, practise before it's real. The worst place to attempt a difficult conversation for the first time is inside one.

If you've just finished Crucial Conversations and want the honest comparison of courses, workshops, peer practice and simulation, I wrote Crucial Conversations training: what works and what doesn't. For a founder's view of the category itself: AI roleplay training.

Toby Sinclair is the founder of Real Talk Studio, an AI conversation simulation platform. He designs roleplay scenarios used across financial services, healthcare, retail and contact centres, and has reviewed hundreds of transcripts of people practising their hardest conversations. He's an ICF Professional Certified Coach.