Feedback
5 Feedback Scripts New Managers Can Use Tomorrow
10 min read
Giving feedback for the first time is terrifying. Your heart races, your words come out wrong, and you end up either saying nothing or saying too much. This article gives you five copy-paste scripts for the situations you'll face in your first months as a manager, word for word, ready to use tomorrow.
Most new managers know they should give feedback. The hard part is finding the words when the moment comes. That's what feedback scripts are for: not a teleprompter to read from, but a starting point you prepare in advance so you walk into the conversation knowing what you want to say and how to say it. Each script below follows the same simple structure, which we'll break down before getting to the five situations you're most likely to face.
Why Feedback Is the Skill That Changes Everything
Here's a stat that should scare every new manager: according to a survey cited by Harvard Business Review, 69% of managers are uncomfortable communicating with employees. And 37% specifically dread giving direct feedback that might trigger a negative response.
That discomfort has consequences. When managers avoid feedback, small issues compound into big ones. The employee who shows up late to meetings doesn't know it's a problem. The work that's 80% of what you expected stays at 80%. The brilliant team member who dominates every conversation never learns to make space for others. Nothing changes because nobody said anything.
And the data on the other side is just as clear. Gallup's research found that employees who receive daily or weekly feedback are 3.6 times more likely to be motivated to do outstanding work compared to those who only receive annual reviews. Even more striking: 80% of employees who received meaningful feedback in the past week are fully engaged, regardless of whether they work remotely, in-person, or hybrid.
Feedback isn't a nice-to-have. It's the single highest-leverage habit a manager can build. And the good news is: you don't need to be naturally gifted at difficult conversations. You need a framework and a few scripts to get started.
The SBI Feedback Model Explained (With Real Examples)
Every script in this article uses the SBI model, developed by the Center for Creative Leadership. It stands for three things:
Situation. When and where did it happen? Ground the feedback in a specific moment so the person knows exactly what you're talking about. Not "you always do this." Instead: "In yesterday's team meeting..."
Behavior. What did you actually observe? Describe the action, not the person. Not "you're disrespectful." Instead: "you spoke over Sarah twice while she was presenting."
Impact. What was the effect? How did the behavior affect the team, the work, or you? Not "it was bad." Instead: "it made it harder for the team to follow her points, and I noticed she went quiet after that."
That's it. Three sentences. Situation, behavior, impact. You describe what happened, what they did, and what it caused. No guessing at motives. No character judgments. Just facts and consequences.
The CCL later extended this to SBI-I, where the final "I" stands for Intent: you ask the person what they were trying to do. This turns a one-way message into a two-way conversation. We'll use that extension in the scripts below.
Now let's get into the five situations you're most likely to face.
Script 1: The Person Who's Chronically Late to Meetings
The situation: One of your direct reports shows up 5-10 minutes late to meetings, not once, but repeatedly. It's not catastrophic, but it's starting to affect the team. Other people notice. It sends a signal.
Why this is hard for new managers: It feels petty. You think, "Is it really worth saying something about 5 minutes?" The answer is yes, because it's not about the minutes. It's about respect for everyone's time and the standard you're setting.
The script:
"Hey [name], I wanted to mention something I've noticed. In the last three team meetings [situation], you've joined about 5-10 minutes after we started [behavior]. I know it might seem small, but it means the team either waits for you or has to catch you up, which eats into everyone's time [impact]. Is there something going on with the timing that I should know about? [intent]"
What to expect: They'll probably apologize and explain (a conflicting meeting, a timezone issue, a habit they didn't realize was visible). That's fine. The point isn't to punish. It's to make the pattern visible and agree on a fix.
If they get defensive: Stay calm. Don't escalate. You can say:
"I'm not saying it's a big deal. I'm flagging it early precisely so it doesn't become one. What would help you be on time consistently?"
The principle: Address small things early. When you let a pattern continue for weeks without saying anything, the eventual conversation becomes much bigger and harder. A light, early mention is always easier than a formal discussion three months later.
Script 2: The Work Is Below the Quality You Expected
The situation: Someone delivers a report, a design, a piece of code, or a client email that doesn't meet the standard. Not terrible, but not what you expected. And you're worried about saying something because you don't want to seem like you're micromanaging.
Why this is hard for new managers: You were probably an individual contributor recently. You know you could do it better. But your job now is to help them do it better, not to redo their work. The temptation is to either fix it yourself (which teaches nothing) or say nothing (which sets a low bar).
The script:
"Thanks for getting the [deliverable] to me. I want to share some thoughts on it. In the client summary you sent yesterday [situation], the data section didn't include the comparison with last quarter's numbers [behavior]. Without that context, the client might not see why our recommendation makes sense, and it could slow down their decision [impact]. Was there a reason you left that out, or was it an oversight? [intent]"
Then (and this is critical) follow up with what "good" looks like:
"For next time, what I'd love to see is the current numbers alongside the previous quarter, with a one-line takeaway for each section. Would it help if I showed you an example of what I mean?"
What makes this work: You're not saying "this is bad." You're saying "here's what was missing, here's why it matters, and here's what I'd like to see." That's coaching, not criticism. Kim Scott, author of Radical Candor, argues that the most damaging thing a manager can do is withhold feedback to be "nice." She calls this "ruinous empathy": caring about the person but not being direct enough to help them improve.
A common mistake: Sandwiching the feedback between two compliments ("Great job on the structure! The data section needs work. But overall, nice effort!"). This is the "feedback sandwich," and most experienced managers agree it dilutes the message. The person walks away thinking everything is fine. Be kind, be specific, be direct. That's enough.
Script 3: Someone Dominates Conversations in Meetings
The situation: One team member, often the most experienced or most confident, talks over others, answers questions directed at other people, or turns every discussion into their monologue. The quieter team members withdraw. The meeting feels one-sided.
Why this is hard for new managers: The dominator is often one of your strongest performers. They're not doing it to be rude. They're engaged and enthusiastic. Telling them to talk less feels like punishing good behavior. But the impact on the rest of the team is real.
The script:
"[Name], I appreciate how engaged you are in our team meetings, it's clear you care about the work. I did want to flag something though. In this morning's sync [situation], I noticed you jumped in several times while Alex and Priya were sharing their updates [behavior]. I think it made them pull back a bit, and I want to make sure everyone has space to contribute [impact]. Was that something you were aware of? [intent]"
Then offer a concrete path forward:
"Here's what I'd love to try: in our next meeting, let's make sure everyone shares their update fully before we open it up for discussion. Your input is valuable. I just want to make sure it doesn't accidentally crowd out others."
Why this matters: Research on psychological safety, particularly from Google's Project Aristotle, found that the strongest teams aren't the ones with the smartest people. They're the ones where everyone feels safe to speak. When one person dominates, that safety erodes, even if the dominator has no bad intentions.
If they take it well (and most people do, when you frame it as a positive trait that needs calibration): thank them genuinely. This is someone who cares. Channel that energy, don't suppress it.
If they push back ("I'm just trying to help" or "Nobody else seems to have a problem with it"), don't argue the point. Redirect to impact:
"I believe that. And I'm not asking you to hold back your ideas. I'm asking you to leave a beat before jumping in, so the rest of the team has room to contribute too. Your ideas won't land as well if people feel talked over."
Script 4: How to Give Positive Feedback as a New Manager
The situation: Someone on your team did something great. Maybe they handled a difficult client, shipped ahead of schedule, helped a colleague, or took initiative on something nobody asked them to do. You noticed.
Why new managers skip this: Because it feels unnecessary. "They know they did a good job." They don't. Or more precisely: they don't know that you noticed. And that difference matters enormously.
Gallup's research shows that only about one in five employees receive feedback on a weekly basis. And 66% of employees say they would likely leave their role if they don't feel appreciated by their manager. Positive feedback isn't fluff. It's retention and motivation.
The script:
"I wanted to take a second to tell you something. During the client call on Thursday [situation], when the client pushed back on the timeline and the energy in the room shifted, you stayed calm, acknowledged their concern, and walked them through the revised plan step by step [behavior]. That completely turned the conversation around. They went from frustrated to aligned in about five minutes [impact]. That's exactly the kind of ownership I want on this team."
What makes this work: It's specific. Not "great job on the call." That's nice but forgettable. When you describe the exact moment, the exact behavior, and the exact impact, the person knows you were actually paying attention. They also know what to repeat, because you've told them precisely what "great" looks like.
A bonus move: Give this feedback in front of the team when appropriate. Public recognition of specific behavior does two things: it reinforces the behavior for the person, and it signals to the rest of the team what "good" looks like here.
One rule: Positive feedback should outnumber constructive feedback, especially in your first weeks as a manager. You're building a foundation of trust. When people know you notice and appreciate their work, they're far more receptive when you later point out something that needs to change.
Script 5: Giving Feedback to Someone More Senior or Experienced Than You
The situation: You're a new manager, and one of your direct reports has been at the company for 5 years. They know more about the work than you do. They might even have wanted the role you got. Now you need to give them feedback on something. The power dynamic feels inverted.
Why this is the hardest script: Because your authority feels fragile. You think: "Who am I to tell them what to do? They've been here longer. They'll see right through me." This is classic imposter syndrome in action, and it's completely normal.
The script:
"[Name], I know you have a lot more experience with [area] than I do, and I genuinely value your perspective. That said, I want to share an observation. In your email to the product team yesterday [situation], the tone came across as quite blunt, particularly the line about the deadline being 'impossible to take seriously' [behavior]. I think it put them on the defensive, and it might make them less willing to collaborate with us on the next sprint [impact]. What was your read on how that landed? [intent]"
What makes this work: You lead with respect for their experience. You're not pretending to know more than them. But you're also not abdicating your responsibility. Your role isn't to be the expert on their domain. It's to observe the impact of their behavior and help them see what they might not see themselves.
If they push back ("That's just how I communicate" or "They needed to hear it"), don't cave, but don't fight either:
"I hear you, and I'm not questioning your intent. I'm just thinking about the effect. If the goal was to get them aligned on the timeline, and the result was that they shut down, then maybe there's a different approach that gets you the same outcome without the friction?"
This reframes the conversation around effectiveness, not personality. You're not asking them to change who they are. You're asking them to consider whether their approach got the result they wanted.
A truth about authority: Your authority as a new manager doesn't come from knowing more or being better at the work. It comes from being consistent, fair, and honest. Every time you give feedback, even uncomfortable feedback, you're proving that you take the role seriously. That builds credibility faster than any other action.
When They React Badly: Your Emergency Script
No matter how well you deliver feedback, sometimes the reaction is emotional. They might get defensive, go quiet, tear up, or push back hard. This is the moment most new managers panic and either backpedal ("Forget I said anything") or escalate ("Well, I'm the manager and this is how it is").
Neither works. Here's what does:
If they get defensive:
"I can see this is tough to hear. Let me explain why I'm bringing it up. I'm not trying to criticize you. I'm trying to help us both be better at this. What's on your mind?"
If they go quiet:
"I notice you've gone quiet, and I want to make sure you're okay. This conversation isn't a judgment call. It's something I noticed and I wanted to talk through it. We can come back to this later if you need some time to think."
If they tear up:
"Hey, it's okay. Take a moment. I'm not bringing this up because I'm unhappy with you. I'm bringing it up because it matters, and I wanted you to hear it from me."
The key in all three situations: don't retreat from the feedback itself. Acknowledge the emotion, give space, and hold the message. You can be compassionate and direct at the same time.
How to Make Feedback a Habit, Not a One-Time Event
The five scripts above are starting points. But the real transformation happens when feedback stops being a special, scheduled, anxiety-inducing event, and becomes something that happens naturally, in small doses, every week.
Here's how to build that habit:
Give feedback within 48 hours. The closer to the event, the more specific and relevant it feels. Feedback about something that happened three weeks ago is archaeology, not coaching.
Start with positive feedback. Especially in your first month. Build a ratio of at least 3:1 positive to constructive. Not because you're avoiding hard conversations. Because you're building the trust that makes hard conversations possible.
Use your 1:1s. The feedback section of a weekly one-on-one meeting is the perfect container for this. It's private, it's recurring, and your team member expects it. That removes the "surprise" factor that makes feedback feel like an ambush. Palmeet builds feedback into the structure of your 1:1s: you flag what you want to address during prep, deliver it in a dedicated section during the meeting, and track how it landed afterward. Feedback becomes part of the rhythm, not something you have to remember to do.
Ask for feedback about yourself. This might feel vulnerable, but it's the most powerful trust-building move a new manager can make. When you ask "How can I better support you?" or "What could I do differently to help you?", you're modeling the behavior you want to see. And you're showing that feedback goes both ways.
Quick-Reference Cheat Sheet
| Script | Situation | Opening line |
|---|---|---|
| 1. Chronic lateness | Pattern of arriving late to meetings | "I've noticed that in the last three meetings..." |
| 2. Quality gap | Deliverable below expectations | "I want to share some thoughts on the [deliverable]..." |
| 3. Meeting dominator | One person talks over others | "I appreciate how engaged you are. I did want to flag something..." |
| 4. Positive recognition | Excellent work worth calling out | "I wanted to take a second to tell you something..." |
| 5. Senior direct report | Feedback to someone more experienced | "I know you have more experience than me. That said..." |
| Emergency | Defensive/emotional reaction | "I can see this is tough to hear..." |
What to Read Next
- How to Run Your First 1:1 as a New Manager (Step-by-Step): A minute-by-minute walkthrough with scripts for every section of your most important weekly meeting, where these feedback scripts fit naturally.
- Promoted to Manager? Here's Exactly What to Do in Week 1: A day-by-day checklist for your entire first week, including when and how to start giving feedback.
- 7 Mistakes Every New Manager Makes (And Scripts to Fix Them): Mistake #2 is not giving feedback. This goes much deeper on why, and how to fix it.
- What to Actually Say in a 1:1 (With Real Examples): Full dialogues showing what a good 1:1 sounds like in practice, not just a list of questions.
For further reading: Radical Candor by Kim Scott on giving feedback that's both caring and direct, the Center for Creative Leadership's SBI model for the original framework used in this article, and Gallup's research on feedback and engagement for the data behind why frequency matters more than formality.
Frequently Asked Questions About Giving Feedback as a New Manager
How Do You Give Feedback for the First Time as a New Manager?
Describe the specific situation, what the person did, and how it affected the team or the work. Then ask for their perspective. This is called the SBI framework (Situation, Behavior, Impact), and it works because it keeps feedback factual, not personal. Use your next 1:1 as the moment. Tools like Palmeet include a dedicated feedback section with prompts so you don't have to start from a blank page.
What Is the SBI Feedback Model?
SBI stands for Situation-Behavior-Impact. It was developed by the Center for Creative Leadership as a way to give feedback that's specific, objective, and non-judgmental. You describe when and where something happened (situation), what the person did (behavior), and what effect it had (impact). The extended version, SBI-I, adds an Intent question to turn it into a dialogue.
How Often Should Managers Give Feedback?
Aim for at least one piece of positive feedback and one piece of constructive feedback per direct report per week, ideally during your recurring 1:1. Daily micro-feedback (a quick "that was well handled" after a call) is even better once you're comfortable with it.
What Do You Do When an Employee Reacts Badly to Feedback?
Don't backpedal and don't escalate. Acknowledge the emotion ("I can see this is tough to hear"), give space if needed, and hold the message. The emergency scripts in this article cover the three most common reactions: defensiveness, silence, and tears.
You don't need to be a natural at feedback. Nobody is. What you need is the willingness to say the thing that matters, even when your voice shakes a little. Every script in this article exists so you don't have to find the words alone. Use them. Adapt them. And know that the fact that you're preparing at all puts you ahead of most managers who've been doing this for years.
Your team deserves honest feedback. And you're ready to give it.
Palmeet guides you before, during, and after every meeting, so each one is better than the last. Get early access →