By Andreas Pettersson, Founder, Leaders ADAPT
Most pages of difficult conversation examples give you a list of topics and one opening line each. Then you are alone in the room when the employee says "that's not what happened," which is the moment the page was supposed to help with.
So this one is built differently. Eight difficult conversation examples, each written the same way: the opener, the gap, the line for when they push back, and the close that makes the change stick. I have run every one of these as a CEO and coached owners through them since.
Read them aloud once before the meeting. You will not need them word for word, but you will stop reaching for the compliment.
Quick answer: The most common difficult conversation examples for managers are: missed results, a behavior or attitude problem, missed deadlines and excuses, a raise or promotion the answer is no to, conflict between two employees, a personal issue affecting work, coasting, and a role that has outgrown the person. Each follows one shape: name the problem, state the impact, make one ask, hold it through pushback, close on a commitment.
The shape every difficult conversation example below follows
A difficult conversation script is a short, pre-written sequence of four moves, the opener that names the problem, the behavior and its impact, one ask with a deadline, and the close on commitment, adapted to the person rather than read verbatim.
Four moves. That is all any of the eight difficult conversation examples below contain, and it is why each takes under a minute to deliver. The full method, preparation through follow-up, is in the guide to difficult conversations with employees; this page is the words.
- Open on the problem, with your intent. No compliment first, no "how do you think it's going." One sentence that names the subject and why you care.
- State the behavior and its impact. A dated fact, then what it cost. The book I wrote for managers, The 5-Minute Leader, calls the structure SBED: Situation, Behavior, Experience, Direction. The rules are the useful part. The situation is specific, never "you always." The behavior is a fact, never "you were rude."
- Make one ask, with a date. Specific enough to verify.
- Close on their commitment, out loud. They state it, they own it.
And one governing rule for the middle, when it gets hard: don't argue about perceptions. Redirect to commitment. Every pushback line below is that rule in different clothes.
How to start a difficult conversation with an employee (the openers that work)
The first sentence decides whether the next fifteen minutes are a correction or a negotiation. Three openers that work:
- Direct and warm: "I want to talk about the Thursday review, because I need those meetings to go differently and I think you can get there."
- Plain: "This is a feedback conversation about the last three deadlines. Ten minutes."
- After a pattern: "We talked about this on the 4th. It has happened twice since. Today I want to be clearer than I was."
Two openers fail every time. The prequel ("I'm not perfect either, but...") discredits your words before you have said them. The sandwich (compliment, problem, compliment) gets heard as the compliment. Reaching for either means you are making yourself comfortable, not the conversation clear.
Example 1: the poor performance conversation
The situation: a capable person whose output has slipped for six weeks, and you have said nothing formal yet.
Open. "I want to talk about where your work is against where it needs to be, because I would rather do that now than in a review."
Gap. "The bar for this role is the weekly pipeline report by Friday noon, complete. In the last six weeks it landed on time twice, and twice it was missing the forecast column. That means I walk into Monday's leadership meeting without the number."
Ask. "Here is what I need from you: the report complete by Friday noon, every week, starting this week. If something is going to block it, I hear about it Thursday, not Monday."
Pushback: "The data doesn't come in until Friday afternoon." "Then the ask is to fix that with the data owner this week, and I'll back you. The Friday noon bar stands."
Close. "Say back what you're committing to. We look at it again on the 20th."
The gap line is the one I use most, in its shortest form: the bar is here, you are here, there is a gap, we close it now, here is what I need from you. No sandwich, no fluff. It is not a warning and not a plan; it is the poor performance conversation example that comes before either, and run well, the underperforming employee problem often ends here.
Example 2: the difficult conversation about attitude
The situation: eye-rolling in meetings, sarcasm in the team chat, "not my job" to a peer. Everyone has noticed. Nobody has said it.
Open. "I want to talk about how you show up with the team, and I'm going to be specific, because 'attitude' is not a useful word."
Gap. "Tuesday, when a teammate asked for help with the export, your answer in the channel was 'that's a you problem.' Thursday, in the planning meeting, you rolled your eyes while a colleague presented the timeline, and he stopped mid-sentence. Two people have started routing around you."
Ask. "When a peer asks for help, the answer is a time you can help or a reason you can't. In meetings, disagreement is spoken, not performed. Starting now."
Pushback: "You're reading too much into it, that's just how I am." "I'm describing two specific things that happened this week and what they did to the room. How you are is your business. How it lands on the team is mine."
Close. "What are you taking from this conversation?"
Notice the translation. You never ask for a better attitude. You name two behaviors, the effect they had, and the behaviors you will see instead. If the pattern continues after a clear conversation like this, the next one is about fit, not attitude.
Example 3: the difficult conversation about missed deadlines and accountability
The situation: the work is late, and every time there is a reason. The reasons are often true. That is what makes this hard.
Open. "I've noticed a pattern, and I want to name it plainly."
Gap. "When things don't happen, you have explanations instead of ownership. The vendor was late, the brief changed, nobody told you. Some of that is real. The result is the same: three deadlines missed this month, and I found out after each one."
Ask. "Reasons aren't results. From now on, you own the outcome completely. If something is going to block a deadline, you escalate the day you see it, not the day after the deadline."
Pushback: "So I get blamed when other people are late?" "You get to raise it the moment you see it, and then it's my problem too. What I won't accept is hearing about it afterward."
Close. "Can you commit to that? Say it back to me."
I set the same expectation with everyone who reports to me, and it sounds like micromanagement until you see what it prevents: if you thought it, tell me, same day, even a text. No sugarcoating, the down and dirty first. If I have to ask to find out, the delay was the problem.
That is not micromanagement. That is setting an expectation, and people cannot meet expectations you never set.
Example 4: the difficult conversation about a raise or promotion when the answer is no
The situation: a good employee asks for more money or a title, and the honest answer is no, or not yet.
Open. "I've thought about your request seriously, and the answer today is no. I want to tell you why and what would change it."
Reason. "The promotion to senior means owning client escalations without me in the room. Twice this quarter you brought them to me instead of resolving them. That is the specific gap."
Path. "If you run the next three escalations end to end and I only hear about them afterward, we have this conversation again in January, and I'll be arguing your side."
Pushback: "So I'm being punished for asking for help?" "You're being told exactly what the next level looks like. Asking for help is fine. Handing over the decision is the thing that changes."
Close. "Do you want to go for it? Then let's put the three escalations on paper."
No is a leadership skill. The version that damages people is the vague no: "not right now, budget, timing." The version that keeps them is a specific no with a specific path, delivered in the first sentence, not the last.
Example 5: two employees in conflict
The situation: two people who need each other are not speaking, and the work is suffering. The mistake is refereeing who is right.
Separately, first, to each. "I'm not here to decide who's right about the handoff. I'm here because the handoff is failing and I need it fixed. What do you need from the other side to make it work?"
Together. "Each of you told me one thing you need from the other. One of you needs the spec frozen 48 hours before build. The other needs to be in the room when the client changes scope. Those are the two rules. Say them back to me."
Pushback: "This won't work because he never..." "We're not doing history today. We're doing the two rules. If either one breaks, I hear about it the same day."
Close. "Two weeks. Then the three of us sit down for ten minutes and check."
The subject is never who is right. It is the working agreement, stated out loud by both.
Example 6: a personal issue that is affecting work
The situation: something is wrong at home, and it is showing at work. Managers avoid this one longest because it feels cruel. Done right, it is not.
Open. "I want to check in, because the last few weeks don't look like you, and I'd rather ask than guess."
Observation. "You've been offline most afternoons and two client calls were rescheduled at the last minute. I'm not asking for details. I'm asking whether something is going on that I should know about, and what you need."
The bar, gently but stated. "Here's what I can flex: hours, the Thursday deadline, who covers the calls. Here's what I can't: clients finding out about a reschedule the morning of."
Close. "Let's write down what changes for the next month, and check in weekly."
Care and the standard are not in tension. You flex the how and hold the what. Stop stating the bar and you have stopped managing and started hoping.
Example 7: the employee who is coasting
The situation: no crisis, someone competent doing 60 percent of what they could. Most managers never have this conversation.
Open. "This isn't a performance problem. I want to talk about the gap between what you're doing and what you're capable of."
Observation. "The work is on time and fine. It is also the same work you were doing a year ago, and I've stopped hearing ideas from you in planning. I don't think that's who you are."
Ask. "Pick one thing this quarter that scares you a little and own it. I'll give you three options, or bring me your own by Friday."
Pushback: "I'm doing my job." "You are. I'm asking whether you want more than the job. If the honest answer is no, tell me, and we'll talk about what that means."
Close. "Which of the three?"
Sometimes the honest answer is no, and that is useful information. In a team of five or more, the person doing 60 percent is the one the strong performers are watching you tolerate.
Example 8: the role has outgrown the person
The situation: someone who was right for the company at twenty people is not right for it at eighty. Nothing is wrong with them; something changed.
Open. "I want to have an honest conversation about the role, because it has changed more than either of us has said out loud."
Gap. "Two years ago this job was running the team. Now it is building a function across three regions, and the last two quarters that part has stalled. I don't think it's effort. I think the job moved."
Choice. "There are two honest paths. One is that you take on the new shape of the role with a very specific ninety days and my time on the page. The other is that we find the role that fits the strength you actually have, here or elsewhere. I want your read before I give you mine."
Close. "Take the weekend. Tuesday, we decide."
I have had this conversation with someone who took us from zero and could not take us further. It was freaking hard. We are still friends, and I helped him find his next role. We outgrew him, and pretending otherwise would have been the unkind option.
If the conversation ends in an exit, the exit is its own skill; how to fire someone covers it word for word.
How to handle a stubborn, defensive or defiant employee
Three pushback types cover almost every hard conversation, and each has a scripted answer I published in The 5-Minute Leader. These are the difficult conversation scripts for managers that get used most, because the pushback is where scripts stop and improvising starts.
| Pushback type | What it sounds like | Your line |
|---|---|---|
| The Defender | "That's not what happened." | "I might have seen it differently. Walk me through your perspective." Then: "Regardless, here's what I need going forward." |
| The Deflector | "Everyone does this." "Why are you singling me out?" | "We're talking about you right now. Can you commit to what I'm asking?" |
| The Ghost | "Okay. Sure. Got it." | "Tell me what you're taking away from this conversation." |
| The Reverser | "Well, you haven't followed up either." | "This conversation is not about me, it's about you. I'll handle what I need to do. You need to change this." |
| The Emotional | Tears, shutdown, silence | "I can see this is landing hard. Take a moment. This conversation is because I believe in your potential, not to make you feel bad." Then return to the ask. |
The defiant employee is a Defender who will not stop. Give the perspective line once, then stop offering it: "I've heard your view. The requirement stands. Are you able to commit to it or not?"
A no, said out loud, is a different conversation, and a clearer one than three more weeks of the same meeting.
Phrases to avoid in every one of these examples
- "It would be really nice if." Dead words. Every hedge tells them the problem is optional.
- "I know you're a good guy, but." The sandwich in one sentence.
- "You always" and "you never." Never true as stated, and they will prove it.
- "Everyone has noticed." Name who and what, or drop it.
- "How do you think it's going?" You know. Asking them to guess is a trap with a smile on it.
- "This is coming from above." Own the message or resolve your disagreement with your own manager first.
One more, because it is subtle: "but" after anything positive. "Good work on the deck, but." The word erases what came before it. If you must join the two, use "and." The same instinct sits behind every feedback model with a C in it: the structure exists so the message survives the delivery.
How to close so the change actually happens
The close has two parts, and most managers skip the second.
First, the commitment, spoken by them. Not "do you understand," which produces a nod. "Say back what you're committing to." They state it, they own it.
Second, the date. Put the check-in in the calendar before either of you stands up, and hold it inside the one-on-one meeting, where the standard gets restated until it is normal. If the change happened, say so at the check-in, by name, while it is still visible. If it did not, the next conversation is shorter and more formal, and for a results gap that usually means a performance improvement plan.
Three strikes is my rule on broken commitments. One is a conversation, two is a clearer conversation, and three means we are talking about something other than the commitment.
Difficult conversation examples FAQ
What are some examples of difficult conversations at work for managers?
The most common difficult conversation examples for managers are about slipping performance, a behavior or attitude problem, repeated missed deadlines and excuses, a raise or promotion request that must be refused, conflict between two team members, a personal issue affecting work, an employee who is coasting below their ability, and a role that has outgrown the person in it. Termination is a separate category with its own procedure.
How do you start a difficult conversation with an employee?
Start with the subject and your intent in one sentence, for example: "I want to talk about the last three deadlines, because I need that to change and I think you can." Do not open with a compliment or with a question that asks the employee to guess the problem. Move immediately to the specific behavior with dates, its impact, and the single change you need by a stated date.
What is an example of a poor performance conversation?
A manager states the standard and the gap as facts: "The report is due Friday noon, complete. In six weeks it was on time twice and twice missing the forecast, so I go into Monday's meeting without the number." Then the ask: "Complete by Friday noon every week, starting now, and if something blocks it I hear Thursday." The conversation closes with the employee stating the commitment and a review date.
How do you have a difficult conversation with an employee about their attitude?
Translate "attitude" into two or three specific, recent behaviors, such as a sarcastic message to a peer or visible eye-rolling while a colleague presented, and state the effect each had on the team. Then describe the behavior you will see instead, for example that requests for help get a time or a reason. Do not ask for a better attitude, which cannot be verified, and do not accept "that's just how I am" as a closing argument.
How do you handle a defensive or defiant employee in a difficult conversation?
Do not argue about perceptions. Offer the employee's view a hearing once ("Walk me through your perspective"), then restate the requirement ("Regardless, here is what I need going forward"). If the employee deflects to others or to the manager's own failings, decline the trade and return to the ask. If defiance continues, ask directly whether they can commit to the requirement; a spoken no is clearer than continued resistance.
What phrases should managers avoid in difficult conversations?
Avoid hedges ("it would be nice if"), the compliment sandwich ("you're doing great, but"), absolutes ("you always," "you never"), borrowed authority ("everyone has noticed"), guessing games ("how do you think it's going?"), and deflection to senior management ("this is coming from above"). Also avoid "but" after any positive statement, which cancels it. Every one of them tells the employee the problem is optional, or that the manager is delivering someone else's message.
Pick the one you have been rehearsing in the car
You already know which of the eight this is. Print that script, change the details, and say it out loud twice tonight. It will feel stiff. Tomorrow, in the room, it will come out as your own words, minus the wrapping.
Navigating difficult conversations is not a personality trait. It is four moves and a refusal to argue about perceptions. The eight difficult conversation examples above are the same four moves wearing different clothes, and once you have run three of them, you will stop needing the page.
The scripts are one chapter. The system is what keeps you from needing them.
Every conversation on this page is a symptom of a missed one earlier: feedback that waited for the review, an expectation never stated, a 1:1 that became a status update. The 5-Minute Leader is the operating system I wrote to make those misses rare: four protocols, five minutes a day, with the exact words for the three conversations managers avoid most and the response to every kind of pushback.
I built it running a company past 150 people as one of Canon's youngest CEOs, and I still run it. The timing rule inside the accountability protocol removes more of these conversations than any script can, and it is the first thing in that chapter. The 5-Minute Leader.
