Difficult Conversation Scripts: Missed Quota & Behavior Issues

These are the three conversations managers put off longest, and the ones where winging it costs the most — a defensive rep, an HR-risk comment, or a conversation that produces sympathy instead of change. Read the script beforehand, adapt the specifics, and don't skip the documentation line at the end of each.

1. Missed Quota

Verbatim opener: "[Name], I want to talk directly about numbers — you closed at [X]% of target this [period], and that's the second [period] in a row below plan. I want to understand what's driving it before we talk about what happens next. Walk me through your own read on it."

De-escalation lines for common pushback:

• If rep blames territory/leads: "That's worth digging into properly — let's actually look at your pipeline coverage numbers against the team average, not just the outcome, so we know if that's the real driver."
• If rep blames the product/market: "Other reps in the same market hit plan this period, so I want to understand what's different in how you're working it, not dismiss the market factor — tell me what you're seeing that they might not be."
• If rep gets emotional or upset: "I hear that this is hard to hear. I want to be clear this conversation is about getting you back on track, not about writing you off — take a second if you need it."
• If rep goes silent/shuts down: "I'd rather you push back on me than go quiet — what part of this doesn't match how you see it?"

Close and next-steps script: "Here's what I want us to walk away with today: one specific thing we're changing starting this week, a date we check back in, and what 'back on track' looks like in numbers. [Specific change]. Let's check in on [date]. I'll document what we agreed so we're both working from the same page — does that match what you heard?"

Documentation line: Conversation held [date] re: quota performance [X]% of target for [period]; agreed action: [specific change]; check-in date: [date].

2. Attitude / Behavior Issue

Verbatim opener: "[Name], I want to raise something specific I've noticed, not a general impression. In [specific instance — a meeting, a message, an interaction], [specific observable behavior] happened. I want to understand what was going on for you at that moment, because it's not what I'd expect from you."

De-escalation lines for common pushback:

• If rep denies it happened: "I want to make sure we're talking about the same moment — here's specifically what I saw/heard [describe]. Does that match your memory of it, or did I misread something?"
• If rep says others do it too: "I'll look into that separately if there's a broader pattern worth addressing, but right now I'm talking to you about your behavior specifically, because that's the one I can act on today."
• If rep gets defensive about character ("you're saying I'm a bad person"): "No — I'm not making a judgment about who you are, I'm flagging one specific behavior in one specific moment. That's a much smaller, much more fixable thing."
• If rep minimizes ("it wasn't a big deal"): "It might not have felt that way from where you were standing — here's the impact it had on [specific person/team/outcome], which is why I'm raising it now rather than letting it go."

Close and next-steps script: "What I need going forward is [specific behavior change], starting now. I'm not going to let this sit unaddressed if it happens again, so I want us both clear on what changes. Is there anything getting in the way of that, that I should know about?"

Documentation line: Conversation held [date] re: [specific behavior] observed [date/context]; expectation reset: [specific behavior change]; rep response: [brief note].

3. Non-Improvement After Coaching (Last-Chance Conversation)

Verbatim opener: "[Name], I want to be very direct, because I owe you that. We've talked about [specific skill/behavior] on [dates/number of occasions], and I haven't seen it change in a way that's showing up in your results. I need this conversation to land differently than the others have."

Close and next-steps script: "Here's where that leaves us: I need to see [specific, measurable change] by [specific date] — not effort, the actual change showing up in [specific metric/behavior]. I'm going to check in on [interim date] so this isn't a surprise either way at the deadline. I want you to succeed here, and I also need to be honest that if this doesn't change, there are real consequences, up to and including [state the actual consequence you're prepared to enforce — e.g., a formal performance plan, role change]. What questions do you have about any of that?"

Documentation line: Conversation held [date] — final coaching conversation re: [specific skill/behavior], following prior coaching on [dates]; specific improvement required by [date]: [detail]; interim check-in: [date]; consequence stated: [detail].

Using These Scripts

• Fill in every bracket before the conversation — a script with visible placeholders read out loud sounds worse than no script at all
• Practice the opener once out loud, alone, before the conversation — the goal is to say it naturally, not read it
• Always leave with a specific next date on the calendar before the conversation ends — an open-ended "let's see how it goes" undoes the entire conversation
• Complete the documentation line the same day, while the specifics are still accurate