A friend who manages a product team of twelve told me something over dinner that stuck with me for weeks. “I knew for three months that one of my senior engineers was underperforming,” she said. “I rehearsed the conversation in my head a hundred times. And every time, I convinced myself it wasn’t the right moment.” By the time she finally had the talk, two other team members had already started job searching — frustrated that nothing was being done.
That pattern plays out in teams everywhere. Managers know feedback matters, but the gap between knowing and doing is enormous — and it’s almost always a language problem, not a courage problem. This article gives you seven word-for-word scripts for the feedback conversations that most managers avoid, delay, or botch. Each one is designed to open the conversation without triggering defensiveness, keep it focused on behavior and outcomes, and close with a clear path forward.
We pulled from Gallup’s 2025 engagement data showing that manager engagement dropped from 30% to 27% — with feedback avoidance cited as a key driver — and cross-referenced it with Harvard Business Review’s recent research on the five most common mistakes managers make when giving negative feedback. The seven scripts below synthesize those findings into language you can actually use this week.
Before you use any script: the 30-second setup
Every script below follows the same underlying architecture. Before you walk into the room — or open the video call — do three things. First, write down the specific behavior you observed and when it happened. Vague feedback (“you need to communicate better”) gives the other person nothing to work with. Second, name the impact that behavior had on the team, the project, or the business. People change when they understand consequences, not when they feel scolded. Third, decide what “good” looks like going forward, so you can end the conversation with a clear ask instead of an awkward trailing off.
With that foundation, here are the seven conversations.
1. The underperformance conversation
This is the one managers delay the longest — often because they’re hoping the problem will resolve itself. It almost never does. The key is to separate the person’s value from their recent output, and to make the conversation about getting them back on track rather than cataloging failures.
The script: “I want to talk about [specific project/metric] over the past [timeframe]. I’ve noticed [specific behavior or output gap], and the impact has been [concrete consequence]. I want to be direct about this because I respect your work and I think there’s a gap between what you’re capable of and what’s been showing up recently. Can you walk me through what’s been going on from your perspective?”
The critical move here is the last sentence. When the employee diagnoses the problem themselves, they own the solution. If you diagnose it for them, you become the person who “doesn’t understand.” Gallup’s data consistently shows that the most effective managers spend more time listening during feedback conversations than talking — the ratio that works best is roughly 70% listening, 30% speaking.
2. The missed expectations conversation
Different from underperformance. Here, the person may be working hard but delivering something other than what was agreed upon. The issue is usually alignment, not effort — and the conversation needs to address the gap without implying laziness or incompetence.
The script: “When we aligned on [project/deliverable], my understanding was [what you expected]. What was delivered was [what actually happened]. I want to understand where the disconnect happened so we can prevent it next time. What was your understanding of the goal?”
Notice what this script doesn’t do: it doesn’t assign blame. It frames the problem as a gap between two understandings, which makes it safe for the person to engage honestly. Many missed-expectation situations are actually delegation failures — the manager thought they were clear, but the handoff lacked the specificity needed. This conversation often reveals that the system needs fixing, not the person.
3. The interpersonal conflict conversation
When two team members can’t work together effectively, the manager’s instinct is often to stay out of it or tell both parties to “work it out.” That rarely works, because by the time it reaches the manager, the conflict has usually calcified into identity positions (“she’s disrespectful” or “he doesn’t listen”) rather than behavioral observations. Your job is to bring it back to behaviors and working agreements.
The script: “I’ve observed some tension between you and [colleague] that’s starting to affect [specific team outcome — meeting dynamics, project timelines, etc.]. I’m not here to referee or decide who’s right. I want to understand your experience of the working relationship and figure out what we can adjust so the team can operate effectively.”
Two things matter here. First, name a specific impact — don’t just say “I’ve noticed tension.” Second, explicitly remove yourself from the judge role. The moment you pick a side, you lose the ability to broker a solution. The goal is to get each person to commit to one or two behavioral changes, not to relitigate every past slight. Sometimes the best outcome is a clear working agreement — who owns what decisions, how disagreements get escalated — rather than a friendship.
4. The resistant senior report
This is the conversation that trips up even experienced managers: giving feedback to someone who has more tenure, more technical expertise, or more organizational clout than you do. The resistance often comes not from the content of the feedback but from the perceived authority dynamic — they don’t believe you have standing to evaluate them.
The script: “I know you bring a lot of experience to this, and I value that. I also have a responsibility to the team’s outcomes, and there’s something I need to raise. When [specific behavior], the effect on the team is [impact]. I’d rather have this conversation directly with you than let it become a bigger issue. How do you see it?”
The acknowledgment at the front isn’t flattery — it’s a genuine recognition that creates psychological safety. The phrase “I have a responsibility” is important because it reframes the conversation from “I’m criticizing you” to “I’m doing my job.” Senior reports often respond well when they understand you’re not questioning their competence but addressing a specific impact. If they push back hard, stay on the impact. You don’t need to win the argument about intent — you need agreement on what changes going forward.
5. The hygiene or professionalism conversation
Body odor, inappropriate comments, messy workspaces that affect shared environments — these conversations feel impossibly personal because they are. Most managers would rather walk over hot coals than have this talk, which means by the time they finally do, the rest of the team has been suffering for months. Speed and privacy matter here more than anywhere else.
The script: “I need to bring up something sensitive, and I’m raising it privately because I’d want someone to do the same for me. I’ve noticed [specific observation — keep it factual and brief]. I realize this might be uncomfortable to hear, and I want you to know this doesn’t change how I view your work or your place on this team. Is there anything I should know, or anything I can help with?”
The “I’d want someone to do the same for me” line is doing heavy lifting — it reframes the conversation from judgment to care. Keep this conversation short. Don’t over-explain, don’t provide multiple examples, and don’t circle back to it unless the issue persists. One clear, compassionate mention is usually enough. If there’s an underlying cause — a medical condition, a living situation — the closing question gives them space to share it without you prying.
6. The promotion denial conversation
Telling someone they didn’t get the promotion they wanted is one of the highest-stakes feedback moments a manager faces, because the person’s sense of professional identity is on the line. Done badly, you lose them within six months. Done well, you actually deepen their commitment because they see you as someone who’s invested in their growth.
The script: “I know the promotion decision matters a lot to you, and I want to be transparent about where things stand. The decision was [outcome], and I want to walk you through the reasoning rather than leave you guessing. The areas where you’re strongest are [specific strengths]. The gaps that factored into the decision are [specific, behavioral gaps — not vague ‘executive presence’ language]. Here’s what I think a path forward looks like over the next [timeframe].”
Three things make or break this conversation. First, never use vague criteria like “executive presence” or “strategic thinking” without defining exactly what behaviors you mean — otherwise, the feedback is unfalsifiable and feels political. Second, the path forward must be concrete and time-bound, or it sounds like a brush-off. Third, check back in 30 days. Most managers have this conversation, feel relieved it’s over, and never follow up — which tells the employee the “path forward” was just a consolation speech. Following up signals that you meant it. The managers who protect their decision-making energy for these follow-ups are the ones who retain their best people.
7. The exit conversation
Sometimes the feedback is that the role isn’t working, and it’s time to part ways. This conversation requires clarity and empathy in equal measure — being direct enough that there’s no ambiguity about the outcome, while treating the person with the dignity they deserve. Many managers soften this conversation so much that the person leaves the room unsure whether they’ve been fired or just coached.
The script: “I’ve thought about this carefully, and I’ve decided that this role isn’t the right fit going forward. This isn’t about your value as a professional — it’s about the match between what this role needs and where your strengths are. Here’s what the transition will look like: [specific timeline, support, references]. I want this to be handled with respect, and I’m open to discussing how we manage the transition.”
Be direct in the first sentence. If you bury the conclusion after five minutes of preamble, the person spends those five minutes in anxiety, reading your face for clues, and they’ll barely hear anything you say. The word “decided” is important — it signals that this isn’t a negotiation. But the rest of the script makes clear that while the decision is final, the process will be humane. Offering to discuss the transition gives the person some agency in a moment where they feel they have none.
The conversation you’re avoiding is the one your team needs most
Here’s what most management advice gets wrong about feedback: it treats the conversation as the hard part. The hard part is actually everything that happens afterward — the follow-up, the accountability, the willingness to have the same conversation again if the behavior doesn’t change. A script gets you through the first five minutes. What gets you through the next five months is a genuine commitment to the person’s growth — or, when growth isn’t happening, the willingness to make a clear decision.
The managers who build the strongest teams aren’t the ones who avoid discomfort. They’re the ones who’ve learned that a few minutes of discomfort now prevents months of dysfunction later. Every script above is a tool, but the real skill is the coaching mindset underneath — the belief that honest feedback, delivered with care, is one of the most valuable things you can give someone.
Pick the conversation you’ve been postponing. Use the script that fits. And have it this week — your team is already waiting for you to lead.