How to Give Feedback to Employees: A 7 Step System With Scripts

By Andreas Pettersson, Founder, Leaders ADAPT

You told them. You're sure you told them. They nodded, thanked you, and left the 1:1 feeling heard. Ten days later the same thing happens, and you realize nothing you said ended with what changes next.

That's where most advice on how to give feedback to employees quietly breaks. The conversation describes the problem, maybe explains the impact, and stops. Feedback that never reaches what changes going forward is venting. Feedback softened into a maybe isn't heard as feedback at all.

Feedback, in the sense this page uses it, is a specific description of what someone did, the effect it had, and what needs to happen next.

The method I teach lives inside the 1:1 Protocol and runs on one clock: say it within 24 hours, and after 48, wait for the next time. Below are seven steps, a script for each, and a map to five deeper pages.

Why giving feedback to employees fails even after a good 1:1

Most managers I work with don't lack warmth. They lack the last sentence.

They'll describe the moment, they'll describe how it landed, and then they'll wait for the other person to draw the conclusion. The other person draws a different one, usually "my manager was a bit annoyed," and goes back to doing exactly what they did before.

The data points the same way. Leaders rate themselves stronger at the relationship than at the direct part.

Feedback by the numbers. 80 percent of employees who said they received meaningful feedback in the past week were fully engaged (Gallup, Fast Feedback Fuels Performance, 2022, 13,490 full time US employees). About seven in ten employees who strongly agreed they received meaningful feedback were highly engaged, against one in four with lower agreement, regardless of team size (Gallup, Span of Control, 2026, meta-analysis of 92,252 teams). Just 20 percent of individuals constantly seek and offer feedback (Culture Partners, Workplace Accountability Study, 40,000 respondents, vendor funded). In the Leadership Readiness Index Q3 2026 skills chapter (n = 66 of 480 completions, 0 to 20 scale), leaders self assessed Clarity and Directness at 7.6 and Relational Intelligence at 11.1 (Leaders ADAPT, leadership skills statistics).

A 3.5 point gap on a 20 point scale is the whole problem in one line. We're good at making people feel safe with us. We're worse at saying the sentence that asks them to change.

And the cost compounds. The rule I teach managers is blunt: every conversation you avoid costs ten times more six months later. The missed handoff becomes a pattern. The pattern becomes a performance review nobody saw coming.

How to give feedback to employees in 7 steps

Here's the whole system on one screen. Each step gets its own section and a script below.

1. Set the standard before you judge against it. Feedback only works on an expectation the person actually heard.
2. Say it within 24 hours. After 48, let it go and wait for the next occurrence.
3. Start with micro-feedback. Thirty seconds, no meeting, in the moment.
4. Use SBED when it's bigger. Situation, Behavior, Experience, Demands.
5. Hold it Warm but Firm. Warm about the person, firm about the behavior, no sandwich.
6. Redirect pushback to commitment. Don't debate what happened.
7. Check it stuck at the next 1:1. Then reinforce the change when you see it.

Step 1: Set the standard before you judge against it

This is the step every tip list skips, and it's why the other six fail.

If you're working out how to give feedback to a direct report for the first time, start here. Feedback sits on top of two things. If the expectation was never clear, you're holding someone to a standard that lived in your head, and they're right to push back. If there's no regular one-on-one, there's no relationship to carry a hard message, so your correction reads as an attack.

Get both in place and the conversation shrinks. You own this. Here's where it stands. Here's what changes.

That's why feedback is the middle of a sequence and not the start of one, and why holding employees accountable gets easier once the standard is written down.

Step 2: Say it within 24 hours

The 24/48 Rule is one rule with two numbers. See it, address it inside a day. The opener is short: "Quick feedback from yesterday. Got 2 minutes?"

Past 48 hours, don't dig it up. The detail has faded on both sides and it turns into an argument about memory. Wait. If the behavior is real, it'll come back, and you'll catch it fresh.

Step 3: Start with micro-feedback

Most behavior changes through small corrections, not big talks. Micro-feedback is a thirty second correction delivered in the moment, with no setup and no calendar invite.

A few lines a manager could use this week:

• "That update buried the decision in paragraph four. Lead with it next time."
• "You committed to Friday in front of the client team. Check capacity before you promise a date."
• "Good catch on the contract clause. Flag the next one in the channel, not in a private message."

Run these often and the big conversations get rare. For a full bank of lines, sorted by situation, use the constructive feedback examples page. For reinforcing lines that name what to repeat, use the positive feedback examples.

Step 4: Use SBED when it's bigger

Some things don't fit in thirty seconds: a pattern, a miss with real consequences, a behavior you've already flagged once.

SBED is a four part feedback structure of Situation, Behavior, Experience and Demands, in which the final part states exactly what the person must do going forward.

Each letter has a rule. Situation is specific, never "you always." Behavior is what you observed, never your read of their intent, so "you were rude" doesn't qualify. Experience is the impact on you, the team or the work. Demands is the sentence most managers leave out.

An illustrative SBED on a handoff:

"In Tuesday's handoff to the support lead (Situation), the notes left out the two open escalations (Behavior). Support called the customer without context, and the customer had to explain the problem twice (Experience). From now on, every handoff lists open escalations first, and you confirm the other side has read them (Demands)."

Four sentences. No adjectives about the person. The last one is the only part they can act on.

If your team already knows SBI, the SBI feedback model page walks through how it compares with SBED, letter by letter. The 4 Cs of feedback page covers the other four letter models managers get handed.

Step 5: Hold it Warm but Firm

Warm but Firm has three parts. Open with intent: say you're invested in their success and that's why you're being direct. Deliver the SBED in the middle with no softening, no maybe, no perhaps. Close by offering support: what do you need from me to make this shift?

The warmth is about the person. It's never fake praise about the work, which is why it isn't a sandwich. The feedback sandwich page takes that apart properly.

One mistake ruins this step before it starts. I've watched leaders open firm feedback with a disclaimer about their own imperfections, meaning to sound humble. My answer is always the same: "You're discrediting yourself." A prequel about you shrinks the message about them. Leave it out.

Step 6: Redirect pushback to commitment

People push back in three recognizable ways. The Defender says that's not what happened. The Deflector says everyone does it. The Ghost says "okay, sure, got it" and nothing lands.

Don't argue about perceptions. Acknowledge that they may have seen it differently, then move to the one thing you control: what they'll do going forward. For the Ghost, ask them to tell you what they're taking away. The full scripts for all three sit on the constructive feedback examples page.

When pushback turns into a standoff, you're past feedback and into a harder conversation. The playbook for that is on difficult conversations with employees.

Step 7: Check it stuck at the next 1:1

Feedback delivered isn't feedback absorbed. The 1:1 is where you find out.

Ask one question in the alignment part of the meeting, the last 20 percent of the 1:1 Protocol in The 5-Minute Leader: what did you change after we talked about the handoffs? Then listen. If they changed it, tell them specifically what you noticed, because "do more of this" is still a demand. If they didn't, you have a pattern, and the next SBED is shorter. Asking before telling here is the manager as coach role in practice: let them name the change first, then add what you saw.

This is also where a check in meeting earns its place: short, on the calendar, about the state of agreed work rather than a performance of being busy.

Which feedback page for which job

Each page linked from this hub does one job. Use this table to pick the right one.

How often should a manager give feedback?

Micro-feedback: whenever you see the behavior, same day. SBED: rarely, because regular micro-feedback keeps most issues small. Structured follow-up: in every 1:1.

Gallup's panel found employees were 3.6 times more likely to strongly agree they were motivated to do outstanding work when their manager gave daily rather than annual feedback (Gallup, 2022). Frequency beats eloquence. Regular feedback for employees works because it arrives while the behavior is still fresh enough to change.

How often the 1:1 itself runs depends on the person. Even with a large team, I tell founders a 20 minute one-on-one every other week, run personally, beats hiring a layer to do it for them. The rhythm is what carries the feedback. The one-on-one meetings guide covers cadence in depth.

Should feedback wait for the 1:1?

No. Here's a scheduling mistake I see constantly. A manager notices something on Monday, writes it on a list, and raises it at Friday's one-on-one, four days cold.

Don't save feedback for a 1:1 that's five days away. Say it inside 24 hours. The 1:1 does a different job: it's where you check whether the change held, spot patterns across weeks, and give the heavier SBED when a pattern has formed.

What a CEO I advise learned about three sentences

In an advisory 1:1, a CEO I work with showed me a harsh comment about one of the company's directors, sitting in a shared document.

The point underneath it was fair. The framing wasn't. It read as scolding from above, and scolding in writing gets defended, not acted on.

We flipped it from blame to responsibility: as director, hitting the business development goals is your job, whatever support I can or can't give you in your function. Then the rule I give every leader who drafts feedback: "Make it three sentences, not a prepared speech."

Then the sequencing, which is a plan and not a threat. "Say it a different way first, and if it doesn't resonate Wednesday next week, then say it like you said it now."

I also told the CEO what to expect. Raise the bar on a defensive person and he'll say you're exposing him, that he can't deliver. Let him. Exposure isn't a failure of the feedback. It's often the point of it.

That's the whole system in miniature. Short. Specific. A clear demand. A second, firmer pass on a date you name in advance.

How do you give feedback remotely?

The mechanics don't change. The signal does. You can't read a face through a laggy video tile, so you have to ask for what you'd normally see.

Keep cameras on in one-on-ones and say why: you need to see how they're doing. Ask for their energy out loud instead of guessing. After any SBED, follow up in writing with what was said and what they committed to, because remote conversations lose detail fast.

Feedback on documents is different. It can default to async: comments in the doc, one line per point, the demand stated plainly. Save live time for anything about behavior.

How to give feedback to employees: FAQ

What is the best feedback model for managers?

There isn't one best model for every situation. A thirty second correction works for small, fresh behavior. For larger issues, a structure that ends in a stated demand, such as SBED (Situation, Behavior, Experience, Demands), tends to work better than one that stops at impact, because the person leaves knowing what to do next. SBI from the Center for Creative Leadership covers the first three steps.

How do you give feedback to an employee who gets defensive?

Avoid arguing about what happened. Acknowledge that the employee may have seen it differently, ask for their view, then move the conversation to what happens going forward and ask for a commitment. If the employee goes quiet and agrees too quickly, ask them to say what they are taking away. Defensiveness usually drops when the discussion shifts from the past to the next step.

How long should a feedback conversation take?

Most feedback takes under five minutes. In-the-moment corrections take about thirty seconds. A structured conversation using Situation, Behavior, Experience and Demands usually runs two to five minutes, plus time for the employee to respond. Conversations that run much longer often mean the feedback was not prepared in advance or has turned into a broader performance discussion that needs its own meeting.

What should you avoid when giving feedback to employees?

When learning how to give feedback to employees, common mistakes include waiting several days, describing character instead of behavior ("you're careless"), generalizing with "you always," hedging the request with "maybe" or "if you get a chance," wrapping criticism between compliments, and opening with a disclaimer about your own flaws. Each one makes the actual request harder to hear. Ending without a clear statement of what should change is the most frequent omission.

How do you give feedback to a direct report remotely?

Remote feedback follows the same structure with more explicit signals. Keep cameras on during one-on-ones, ask directly how the person is doing rather than inferring it, and send a short written summary afterward listing what was discussed and what the person committed to. Feedback on written work can usually be given asynchronously as comments, while feedback on behavior is better delivered live.

How do you know if feedback worked?

Feedback worked when the behavior changes, not when the conversation felt good. Managers can check at the next one-on-one by asking what the person changed since the conversation, and by watching for the next occurrence of the situation. If the behavior repeats, the next conversation is shorter and more specific. If it changes, naming the improvement reinforces it.

The feedback system, start to finish

If you've ever walked out of a 1:1 sure the message landed and watched the same miss repeat, you already know the gap isn't effort. It's structure. Learning how to give feedback to employees is mostly learning to say the last sentence, fast, and then checking it.

Feedback also doesn't stand alone. It's one part of four protocols, and each one closes a different leak.

Delegation Protocol: handed-off work stays handed off, which gives your feedback a written standard to point at. 1:1 Protocol: problems show up while they're small, and it's the room where a correction gets checked. Accountability Protocol: everyone can see the bar, so a miss is obvious without you chasing it.

Rhythm Protocol: daily and weekly cadence the team keeps running on the days you're out.

Three weeks from now, the difference is small and obvious. Corrections take thirty seconds and happen the same afternoon. Your 1:1s open with the other person telling you what they changed. The SBED conversations you used to dread happen once a month instead of once a week.

Tomorrow morning, before your first meeting, write down one behavior you saw in the last 24 hours and the single sentence that says what changes. Deliver it before lunch. Two minutes, no preamble.