Giving Negative Feedback: Practice Scripts and Real Scenarios
Only 14% of employees feel performance feedback inspires them to improve. The problem isn't the message—it's the delivery. This guide gives you the complete SBI framework, word-for-word scripts, and AI practice scenarios to transform how you deliver constructive criticism.
Why Most Negative Feedback Fails
The irony of feedback is that everyone wants to receive it—69% of employees say they would work harder if they felt their efforts were better recognized and corrected—but almost no one wants to give it. A Gallup survey found that only 26% of employees strongly agree that the feedback they receive helps them do better work.
The gap isn't because managers don't care. It's because delivering negative feedback is genuinely uncomfortable, and most managers have never been taught how to do it well. They fall back on instincts that backfire:
- Being vague to soften the blow—which means the employee doesn't know what to change
- Using the feedback sandwich—which trains employees to distrust praise
- Making it personal—which triggers defensiveness and shuts down learning
- Avoiding the conversation entirely—which lets problems compound until they become crises
The solution isn't to suppress your discomfort—it's to develop a framework that channels it into effective delivery. The SBI framework (Situation-Behavior-Impact) has been validated across thousands of organizations as the most effective approach to constructive criticism. And like any skill, it gets easier with practice.
The SBI Framework for Negative Feedback
Developed by the Center for Creative Leadership, SBI stands for Situation-Behavior-Impact. It's the gold standard for feedback because it keeps the conversation objective, specific, and focused on observable facts rather than character judgments.
Situation
When and where did this occur?
Describe the specific context—date, time, meeting, or project. This anchors the feedback in reality and prevents "you always..." generalizations that trigger defensiveness.
- "In Tuesday's client presentation..."
- "During yesterday's sprint planning meeting..."
- "When you submitted the Henderson report last Friday..."
- "Over the past two weeks of the project..."
Behavior
What specifically did you observe?
Describe the observable action—what they said, did, or didn't do. Stick to facts that a camera could record. Avoid interpretations ("you were disrespectful") or mind-reading ("you didn't care").
- "...you checked your phone four times during Sarah's presentation..."
- "...the report contained five calculation errors in the revenue projections..."
- "...you said 'that's a stupid idea' when Marcus suggested the new process..."
- "...you arrived 15 minutes late and didn't acknowledge the delay..."
Impact
What was the effect?
Explain the consequences—on the project, team, client, company, or their own goals. This is where you answer "why does this matter?" Connect behavior to outcomes they care about.
- "...which made the client visibly frustrated—they cut the meeting short and haven't responded to follow-ups"
- "...which required 3 hours of rework and delayed the client deadline by a day"
- "...which shut down the discussion—Marcus hasn't contributed an idea in the last three meetings"
- "...which meant we started the standup without the context you were supposed to provide"
The Complete SBI Statement Formula
"[SITUATION], [BEHAVIOR], which [IMPACT]."
Example:
"In Tuesday's client presentation [S], you read directly from your slides without making eye contact with the client [B], which made them seem disengaged—two people were on their phones by minute 10 and they asked fewer questions than usual [I]."
SBI Examples for Common Feedback Situations
Here's how to apply SBI to the situations managers most commonly need to address:
Word-for-Word Opening Scripts
The hardest part is often just starting the conversation. Here are complete opening scripts you can practice and adapt:
Missed Deadlines
Address chronic lateness on deliverables while maintaining motivation
"I want to discuss the Project Alpha deliverables. Over the past month, three of your four submissions have been 2-3 days late: the brief on March 3rd, the draft on March 10th, and the final on March 18th. This has delayed the client's internal reviews and affected their confidence in our timeline. What's been happening on your end?"
Quality Issues
Discuss declining work quality without crushing confidence
"I want to talk about the Henderson report you submitted Friday. I found four calculation errors in the expense projections and two sections where the data didn't match the appendix. This is different from your usual standard, and I needed to spend two hours correcting it before the client meeting. Walk me through your process on this one—what was different?"
Attitude Problems
Address negativity affecting team morale
"I need to discuss something I've observed in our team meetings. In the last three standups, you've sighed audibly when Sarah shared updates and made comments like 'that'll never work' and 'we tried that before.' The impact is that Sarah seems reluctant to share ideas now, and I'm seeing the same hesitation from others. I want to understand what's behind this."
Communication Gaps
Improve responsiveness and clarity in team communication
"I want to talk about email responsiveness. In the past two weeks, I've sent three messages that needed same-day responses for client deadlines—the budget approval on the 5th, the scope change on the 8th, and the timeline question on the 12th. Each took 2-3 days to get a reply. This created pressure on the team and nearly missed a client deadline. What's happening with your inbox management?"
Performance Decline
Address a previously strong performer who's slipping
"I wanted to check in because I've noticed a shift in the last couple of months. Your work on the Johnson account last quarter was excellent—you exceeded every metric. Since February, I'm seeing missed check-ins, shorter client updates, and your last two proposals needed significant revision. This isn't the standard I know you're capable of. What's going on?"
Undermining Decisions
Address an employee who contradicts leadership in front of others
"In yesterday's all-hands meeting, when I announced the new process for client escalations, you said 'that's never going to work in reality' in front of the entire team. Whether or not you agree with the decision, publicly undermining it creates confusion and makes implementation harder. If you have concerns about a decision, I need you to raise them with me privately first. Can we agree on that?"
Missing Meetings
Address attendance issues without assumptions
"I want to discuss your attendance at our Thursday team syncs. Over the past six weeks, you've missed four of them and joined late for the other two. These meetings are where we align on priorities and surface blockers, so missing them affects coordination. What's been making Thursday mornings difficult?"
Client Complaints
Address feedback you've received from customers
"I received feedback from the Martinez account yesterday that I need to share with you. They said the last two check-in calls felt rushed, they didn't feel their questions were fully answered, and Sarah specifically mentioned feeling 'dismissed' when she asked about the timeline. I want to understand your experience of those calls—what's your read on how they went?"
After SBI: The Rest of the Conversation
SBI gets you through the opening. Here's the complete conversation flow:
Deliver your SBI statement
State the Situation, Behavior, and Impact clearly and completely. Then stop talking.
Pause and listen
Ask "What's your perspective?" or "Walk me through what happened on your end." Listen fully before responding. They may have context you lack.
Acknowledge and redirect
If they get defensive or make excuses: "I hear that you had competing priorities. And the deadline was still missed. Let's talk about what we can do differently going forward."
Collaborate on solutions
Ask "What would help you address this?" before offering your own suggestions. People are more committed to solutions they helped create.
Agree on specific next steps
"So we're agreed: you'll double-check all calculations before submission and flag any deadline risks at least 48 hours in advance. Let's check in on this on the 15th—I'll send a calendar invite."
7 Mistakes That Derail Feedback Conversations
Even well-intentioned feedback fails when these common patterns show up. Here's what to avoid and what to do instead:
1. Being vague to avoid discomfort
"Your communication could be better."
"In the client email on March 5th, you wrote 'we'll get back to you soon' without specifying a date. The client followed up twice asking when. I need you to include specific timeframes in all client communications."
Why it matters: Vague feedback is unfair because the employee can't act on it. They leave confused and you leave frustrated when nothing changes.
2. Making it about character instead of behavior
"You're being careless with your work."
"The last three reports had calculation errors: 5 in the March report, 3 in April, and 2 in May. I need to see zero errors going forward."
Why it matters: Character judgments feel like attacks and trigger defensiveness. Behavioral feedback is specific and changeable.
3. Piling on multiple issues at once
"We need to talk about your deadlines, your attitude in meetings, and also the quality of your last project..."
"I want to focus on one thing today: the project deadlines. We can discuss other topics in our next 1:1."
Why it matters: Multiple criticisms overwhelm and discourage. Address one issue thoroughly before moving to the next.
4. Apologizing for giving feedback
"I'm sorry to have to say this, but..."
"I want to share some important feedback about the Henderson project."
Why it matters: Apologizing suggests the feedback might not be valid or that you're unsure of yourself. Own the message.
5. Ending without clear next steps
"So, hopefully that makes sense. Let me know if you have questions."
"To summarize: I need to see response times under 4 hours for client emails. Let's check in on this in two weeks—I'll put time on the calendar for the 15th."
Why it matters: Without specific expectations and follow-up, the conversation is just venting. Accountability requires clarity.
6. Giving feedback in front of others
"In the team meeting: 'And speaking of deadlines, Sarah, your report was late again...'"
"Schedule a private 1:1 to discuss performance issues."
Why it matters: Public criticism humiliates and damages trust. Private conversations preserve dignity and allow honest dialogue.
7. Waiting too long
"In December review: 'Back in March, there was an incident with a client...'"
"Address issues within 48-72 hours while context is fresh."
Why it matters: Delayed feedback can't be acted upon, feels like an ambush, and suggests you've been cataloging grievances.
Handling Difficult Reactions
No matter how well you deliver feedback, you can't control the response. Here's how to handle the most challenging reactions:
😤 Defensiveness
"That's not fair! I was dealing with three other priorities!"
Respond: "I hear that you had competing demands. And the deadline was still missed without any heads-up. Let's talk about how to handle that situation next time—what would have helped?"
😢 Tears
Employee becomes visibly upset, starts crying.
Respond: "Take a moment. Would you like some water?" [Sit quietly.] When ready: "I can see this is upsetting. This feedback is important, which is why we're discussing it. When you're ready, let's continue."
😠 Anger
"This is ridiculous! You're targeting me!"
Respond: "I understand you're frustrated. I'm not targeting you—I'm addressing a specific situation. Let's take a breath and focus on the facts. Can we do that?"
🙅 Denial
"That didn't happen. You're remembering it wrong."
Respond: "I have the email thread here—let's look at it together. The message was sent on March 5th at 2pm, and the response came March 8th." [Come with documentation.]
🤷 Deflection
"Well, Sarah does the same thing and you never say anything to her!"
Respond: "My conversations with Sarah are separate. Right now, I want to focus on you and this specific situation. What would help you meet the deadline next time?"
😶 Silence
Employee shuts down, won't engage, one-word answers.
Respond: "I notice you've gone quiet. I'd really like to hear your perspective—it's important to me. Take a moment if you need it. I'm here to listen when you're ready."
Practice Scenarios
Each scenario presents different challenges. Practice these common situations before facing them in reality:
Missed Deadlines
Address chronic lateness on deliverables while maintaining motivation
Quality Issues
Discuss declining work quality without crushing confidence
Attitude Problems
Address negativity affecting team morale
Communication Gaps
Improve responsiveness and clarity in team communication
Performance Decline
Address a previously strong performer who's slipping
Undermining Decisions
Address an employee who contradicts leadership in front of others
Practice with AI That Pushes Back
Reading scripts is helpful, but it won't prepare you for a defensive employee who interrupts, makes excuses, or starts crying. EchoPitch lets you practice feedback conversations with AI that responds realistically—so you build the muscle memory to stay calm no matter what happens.
Start PracticingFrequently Asked Questions
Why is giving negative feedback so difficult?
Our brains are wired to avoid conflict and maintain social harmony—a survival mechanism from when social rejection meant real danger. Delivering criticism triggers anxiety about damaging relationships, causing hurt, or facing aggressive reactions. Research shows managers spend an average of 3 hours worrying about a 10-minute feedback conversation. This leads to vague feedback, avoidance, or the ineffective 'feedback sandwich'—none of which help the employee improve. Practice reduces this anxiety by building familiarity with the conversation pattern.
What's the best framework for giving negative feedback?
The SBI (Situation-Behavior-Impact) framework from the Center for Creative Leadership is the gold standard. State the Situation (when and where), describe the specific Behavior you observed (objective, factual), and explain the Impact (on the team, project, client, or their own goals). Then pause for their response, discuss solutions collaboratively, and agree on specific next steps with a follow-up date. This framework keeps feedback objective, specific, and actionable while avoiding character judgments.
How do I handle an employee who gets defensive?
Defensiveness is a natural response—expect it and prepare for it. Stay calm and don't match their energy. Acknowledge their emotion ('I hear that this is difficult to hear'), but don't retreat from the facts. Use 'and' instead of 'but' to connect: 'I understand you had competing priorities, and the deadline was still missed.' Then redirect: 'Let's focus on how to prevent this going forward.' Practice builds the muscle memory to stay composed during pushback.
Should I use the 'feedback sandwich' method?
No. Research consistently shows the feedback sandwich (positive-negative-positive) backfires. Employees learn to distrust praise because they're waiting for the 'but.' The critical message gets diluted between compliments. And it can feel manipulative. Instead, separate positive and constructive feedback into different conversations, or clearly delineate sections if you must cover both. Say 'I want to discuss two things—first, what went well, and second, what needs to change.'
When should I give negative feedback?
As close to the event as possible while allowing emotions to settle—typically within 2-3 days. Immediate feedback (same day) is ideal for small issues. Saving feedback for annual reviews is one of the biggest mistakes managers make: feedback loses context, feels like an ambush, and isn't actionable. If you notice something on Monday, have the conversation by Wednesday. The discomfort of prompt feedback is always less than the cost of delayed feedback.
How specific should negative feedback be?
Extremely specific. 'Your communication needs work' is useless—the employee doesn't know what to change. 'In yesterday's client call at 2pm, you interrupted Sarah three times during her project update and didn't acknowledge the client's budget concern until I prompted you' is actionable. Specificity makes feedback believable (it clearly happened), improvable (they know exactly what to change), and defensible (it's documented). Prepare specific examples before any feedback conversation.
What if the employee starts crying?
Pause and offer a moment: 'Take your time—I'll get you some water.' Sit quietly and don't fill the silence with reassurances that undermine your message. Don't apologize for giving feedback or take it back. Once they've composed themselves, acknowledge the emotion ('I can see this is upsetting') and then continue: 'This is important for us to discuss. When you're ready, I'd like to continue.' Practice helps you stay calm and compassionate without abandoning the conversation.
What if the employee completely disagrees with my assessment?
Listen to their perspective fully before responding—they may have context you lack. Then separate facts from interpretations: 'The deadline was Tuesday; the deliverable arrived Thursday—that part isn't in dispute. You're saying the client changed requirements on Monday, which I wasn't aware of. Let's look at the email thread together.' If you still disagree after hearing their view, you can say: 'I appreciate your perspective. I still see it differently, and here's why...' You don't need agreement to set expectations.
How do I give feedback to someone more senior or experienced than me?
Focus on impact rather than instruction. Instead of 'You should do X,' try 'When X happens, the impact is Y. I wanted to make sure you had visibility into that.' Frame it as sharing information they might not have, not telling them what to do. Use questions: 'I noticed X in the last project—was that intentional, or would you like to adjust for next time?' This approach respects their expertise while still raising the issue.
How can practicing actually help with real conversations?
Practice builds procedural memory—the same type of memory that lets experienced drivers navigate traffic automatically. When you've practiced handling defensiveness, tears, or denial multiple times, your response becomes automatic rather than requiring conscious thought under pressure. Research shows managers who practice handle unexpected situations 70% better and report 56% higher confidence. The discomfort shifts from the conversation itself to anticipating the conversation.
What if I've waited too long to give feedback?
It's never too late, but acknowledge the delay: 'I should have raised this sooner, and I apologize for not addressing it earlier. I want to discuss it now because it's important.' Then proceed with your feedback. The conversation will be harder than it would have been earlier, but avoiding it further only compounds the problem. Use this as motivation to address issues promptly in the future.
How do I follow up after giving negative feedback?
Always end the initial conversation with specific next steps and a follow-up date: 'Let's check in on this in two weeks, on the 15th.' During follow-up, acknowledge progress ('I've noticed you've been responding to clients within 4 hours—that's exactly what I was looking for') or address continued issues ('We discussed this on the 1st, and I'm still seeing X. Let's talk about what's getting in the way'). Follow-up shows the conversation mattered and creates accountability.
Related Articles
Difficult Conversations Practice Hub
Master all types of challenging workplace conversations
Performance Review Conversations
Navigate annual reviews with confidence
Praise and Recognition
Balance negative feedback with meaningful recognition
Hard Talks at Work
Broader conflict resolution and peer conversations
Practice Before the Real Conversation
Build confidence with AI that responds like real employees—including defensiveness, denial, tears, and anger. Know exactly how to handle anything before it happens.
Start Practicing