How to Give Constructive Feedback to an Employee
Give critical feedback with the SBI model: describe the situation, behaviour and impact, listen to their side, and agree one action. With examples.
How do you give constructive feedback?
Describe a specific situation, the behaviour you saw and its impact. Then ask for their view and listen before you respond. Stay on that one issue, even when they push back, and finish by agreeing one specific action and a date to check in.
The hard part is not the formula; it is the first two minutes, when the other person is surprised and looking for a reason the feedback is unfair. Most feedback fails there, through a label (“you're careless”) or a retreat.
Harvard Business Review's advice for these conversations is consistent: be specific about what you observed, ask for the other person's perspective, and agree next steps together (HBR, 2024). This guide turns that into words you can say, including what to say when the reply is a deflection.
The Situation-Behaviour-Impact model
SBI keeps feedback to facts the other person can recognise, rather than a judgement they will want to defend.
SBI is a tool from the Center for Creative Leadership (Mind Tools). It has three parts:
- Situation: when and where. “In Tuesday's planning meeting.”
- Behaviour: only what you saw or heard, not your guess at the motive. “You cut across Leo three times.”
- Impact: the effect on you, the team or the work. “He stopped contributing.”
The discipline is in the middle step. An HBR piece on difficult conversations makes the same point: separate what you observed from your interpretation of it (HBR). Here are five rewrites. Adapt them with your own facts.
| Issue | Instead of the label | Say it in SBI form |
|---|---|---|
| Late code reviews | You're not pulling your weight on reviews. | In the last two sprints (situation), four of the reviews assigned to you sat for more than three days (behaviour). Two releases slipped while the authors waited (impact). |
| Missed handoff | You dropped the ball on the Henley account. | When you went on leave last Friday (situation), the handover note did not mention the open refund (behaviour). The client chased it twice and Priya had to rebuild the history from email (impact). |
| Interrupting in meetings | You come across as arrogant in meetings. | In Tuesday's planning meeting (situation), you cut across Leo three times before he finished a sentence (behaviour). He stopped contributing, and we lost his view on the estimate (impact). |
| Rushed client deck | Your work has got sloppy. | In the deck you sent the client on Monday (situation), the revenue figures on slides 4 and 9 did not match (behaviour). Their finance lead asked which one was right, and I had to correct it on the call (impact). |
| Missing stand-ups | You clearly don't care about the team. | Over the past three weeks (situation), you have joined stand-up on four of fifteen days (behaviour). The team has had to guess where your work is, and two people duplicated a task (impact). |
Then stop talking and ask: “What's your view?” or “What's been getting in the way?” It is where you learn the context you did not have.
What do you say when they get defensive?
A decent, capable person usually deflects first. These are the replies to expect, and a response to each that keeps the conversation on track.
| They say | What is happening | You might say |
|---|---|---|
| “Everyone is late with reviews, not just me.” | Deflection: moving the topic from you to the team. | “That may be true, and I'll look at the team picture separately. Right now I want to talk about yours, because two releases waited on them. What's been making them hard to get to?” |
| “Honestly, nobody told me this was a problem.” | Surprise, often fair. Own your part. | “You're right that I should have raised it sooner, and that's on me. I'm raising it now because it's started to affect releases. Can we look at what would help from here?” |
| “I have been doing two jobs this month. Did you know that?” | Hidden context. This is new information; treat it as such. | “I didn't know the full extent, and that matters. Tell me what's been on your plate. I still need reviews moving, so let's work out together what gives.” |
| “So what do you want me to do differently?” | The turn towards agreement. Do not waste it. | “Reviews assigned to you get a first pass within one working day. If that is not possible, flag it in the channel so someone else can pick it up. Does that work?” |
Each response acknowledges what is fair, asks a question, and returns to the one behaviour. You are not trying to win the point about whether everyone is late. You are trying to change one thing. New context, such as covering a colleague's work, may change the action you agree; it does not make the feedback wrong.
Ending with one agreed action
A feedback conversation without an agreed action is just a complaint. Finish with something both of you could check.
A good agreed action has four parts:
- One thing. Not a list. The behaviour you discussed.
- Observable. “First pass on assigned reviews within one working day”, not “be more responsive”.
- Theirs as well as yours. Ask, “What would make that possible?” If they need something from you, such as taking a task off their plate, say yes or say what you can do.
- A check-in. “Let's look at it together in our 1:1 next Thursday.”
Close by saying it back: “So, reviews get a first pass within a day, you'll flag in the channel if you can't, and I'll move the migration ticket to Leo. We'll check in Thursday.” Then send the same three lines in a short message after the meeting.
Feedback mistakes to avoid
Four habits that make a fair message land badly.
Labels instead of behaviour
"Unreliable" and "careless" describe a person and invite an argument about character. Describe what they did, when, and what it caused.
The feedback sandwich
Praise, criticism, praise teaches people to brace when you compliment them, and the middle often gets lost. Give positive feedback on its own, when it is earned.
Piling on
Once they push back, it is tempting to add three more examples from last year. Stay on the one issue you came to discuss.
Backing down
When they get upset, saying "it is not a big deal really" undoes the conversation. Acknowledge the feeling and keep the point.
If the issue is no longer a single behaviour but a sustained gap against the role, the conversation changes. See how to talk to an underperforming employee. For conversations with peers or your own manager, see difficult conversations at work.
Practising this with an AI counterpart
Feedback is a spoken skill. Saying your SBI line out loud once, and hearing the deflection, does more than rereading your notes.
The “Give tough feedback” role-play casts a senior member of your team: good at the job, proud, a little defensive, and with reasons you may not know about. You describe the situation in your own words, for example a senior engineer who keeps missing review deadlines. The team member opens with “Hey, you wanted to talk? Is everything OK?” and then reacts as a real person would: deflecting first, explaining their side, and coming round only when the feedback is specific and they feel heard. You can set the pressure to friendly, standard or tough.
The report, written as a leadership coach who observed the conversation, scores four things:
Specificity (30%)
Describes the situation, the behaviour and its impact, without labels
Listening (25%)
Asks for and acknowledges the other side before responding
Focus (20%)
Stays on the issue without piling on or backing down
Agreement (25%)
Ends with one specific, agreed action and a check-in
A character label such as “you are unreliable” is called out by name. The report also says how your team member is likely to read you and what to work on before the real conversation. Scores are estimates from one practice run, not a judgement of you as a manager. The role-play is for rehearsal only; it does not feed you lines in a real meeting. If you turn the camera on, it is a mirrored self-view that is not recorded or analysed. For other conversations you can rehearse, see the guide to role-play practice for work conversations.
Frequently asked questions
- What is an example of constructive feedback?
- For example: "In the last two sprints, four reviews assigned to you sat for more than three days, and two releases slipped while authors waited. What has been getting in the way?" It names the situation, the observable behaviour and its impact, then asks for their view. It avoids labels such as "unreliable".
- What is the SBI feedback model?
- SBI stands for Situation, Behaviour, Impact. It is a feedback tool from the Center for Creative Leadership: you describe when and where something happened, the specific behaviour you observed, and the effect it had on you, the team or the work. It keeps feedback factual and stops it turning into a judgement of the person.
- How do you give feedback to a defensive employee?
- Expect the first reaction to be a deflection and do not argue with it. Acknowledge anything fair, ask what has been getting in the way, and listen properly. Then return calmly to the one behaviour and its impact, and move towards a single agreed action.
- Should you use the feedback sandwich?
- Usually not. Wrapping criticism between two compliments blurs the message, and people learn to distrust your praise. Be direct and kind about the issue, and give positive feedback separately when it is deserved.
- How often should managers give feedback?
- Soon after the behaviour, while the details are fresh and before it becomes a pattern. Waiting for an annual review means hearing about a problem months late, which feels unfair.
- How do you follow up after giving feedback?
- Put the agreed action and the check-in date in a short message after the meeting. At the check-in, say what has improved before raising anything still open. If nothing has changed, have a second, more formal conversation and involve HR if your policy requires it.