Giving feedback is the skill that separates managers people respect from managers people quietly tune out. And almost everyone finds it uncomfortable, which is exactly why so much feedback is either avoided entirely or delivered so vaguely that nothing changes.
The problem usually is not courage. It is structure. "You need to be more proactive" is not feedback, it is a verdict, and the person on the receiving end cannot do anything with it except feel judged. They do not know what they actually did, so they cannot repeat it or stop it.
The fix I come back to again and again is a model called SBI: Situation, Behaviour, Impact. It is simple enough to use in the moment and structured enough to keep you out of the 2 traps that wreck feedback: being vague, and making it personal.
What SBI actually means
Three parts, in order. The order matters.
- Situation. Pin the feedback to a specific moment. When and where did it happen? This stops the conversation drifting into sweeping generalisations like "you always" or "you never", which are almost never true and put people instantly on the defensive.
- Behaviour. Describe what the person actually did, observably, as if you were replaying a recording. No interpretation, no motive, no labels. "You interrupted twice" is behaviour. "You were dismissive" is a judgement you have layered on top, and it is exactly where feedback goes wrong.
- Impact. Explain the effect it had: on you, on the team, on the work, on the client. This is the part that makes feedback land, because it connects what they did to something they care about. People will argue with your opinion of them. They will rarely argue with the genuine impact their actions had on others.
The discipline is in separating behaviour from impact. We jump to impact-as-accusation all the time ("you embarrassed me in that meeting"). SBI forces you to first say what they did, then separately what it caused. That small gap is what keeps the person listening instead of defending.
Worked example 1: constructive feedback
A team member, let's call him Sam, talked over a junior colleague repeatedly in a client meeting.
The lazy version: "Sam, you were really dominating in there. You need to give other people more space." Vague, labelled, and Sam will either deny it or shrink.
The SBI version:
"Sam, in the client call this morning (situation), I noticed you jumped in and finished Priya's point twice before she got to the end of it (behaviour). What I saw was Priya go quiet for the rest of the meeting, and the client missed the detail she was actually closest to (impact). I wanted to flag it because I rate her input and I want the client hearing it directly."
Notice what that does. It is anchored to one meeting, not Sam's character. It describes something he could see on a recording. And the impact is concrete and tied to a shared goal, the client getting the best thinking, rather than "you were rude". From here you can ask, "How did you see it?" and have an actual conversation, because Sam has something specific to respond to.
Worked example 2: positive feedback
SBI is not just for problems, and this is where most managers leave value on the table. "Great job today" feels nice for about 4 seconds and teaches the person nothing about what to do again. Praise is only useful when it is specific enough to repeat.
Say a team member, Mia, handled a frustrated customer well.
The throwaway version: "Mia, you were great with that customer. Well done."
The SBI version:
"Mia, when that customer rang in upset about the delayed order this afternoon (situation), you let them finish without interrupting, repeated the problem back so they knew you had heard it, then gave them a clear next step and a date (behaviour). They went from furious to thanking you inside 5 minutes, and they have already replied to say they will stay with us (impact). That is exactly the standard I want us known for. Do that every time."
That person now knows precisely what worked: let them vent, reflect it back, give a clear next step. You have turned a one-off into a repeatable skill, and you have made the recognition mean something because it is clearly real and not just a reflex "good job".
How to make it stick
A few things I have learned about using SBI in the real world.
- Give it close to the event. Feedback has a short shelf life. A specific situation from this morning is useful. The same point dredged up at a review 4 months later just feels like an ambush.
- Lead with curiosity, not a verdict. SBI gets you in the door cleanly, then ask how they saw it. You might be missing context. The goal is a shared understanding, not a delivery of sentence.
- Keep impact honest. Do not inflate it to win the point. If the real impact was small, say so. Overstating it is the fastest way to lose your credibility for the time it actually matters.
- Practise on the good stuff first. If the only time your team hears structured feedback is when something went wrong, feedback itself becomes a threat. Use SBI for praise just as often, and the hard conversations get easier because the channel is already trusted.
Feedback is not a personality trait you either have or lack. It is a skill, and SBI is the scaffolding that makes it learnable. Use it for a fortnight, on the good and the bad, and you will notice people stop bracing when you say "can I give you some feedback?"
If the conversations you are avoiding are heavier than this, working through them with a coach before you have them is one of the highest-value things a new leader can do. That is exactly what a free strategy call is for: a relaxed talk about the specific situation in front of you, and how to walk into it with a plan.
