Good feedback is specific, timely, and about behaviour — not character. Almost everything that goes wrong with it comes from breaking one of those three rules.
Most managers I meet fall into one of two camps. The first softens everything into mush — "great job, maybe just tighten it up a bit?" — until the message disappears entirely. The second saves criticism up, says nothing for months, and then lets it all out in one overwhelming review. Both come from the same place: feedback feels risky, so we either dilute it or delay it.
But feedback isn't the risky part. Vague feedback and saved-up feedback are the risky parts. Here's the structure I keep coming back to, the exact words I use, and what to do when it doesn't land softly.
The mistake almost everyone makes
We make feedback about the person instead of the work. "You're disorganised" is a verdict on someone's character — there's nothing to do with it except feel bad. "The last two reports came in after the deadline" is an observation about behaviour — something a person can actually change. The moment feedback becomes about who someone is, defensiveness is the only reasonable response.
The structure: Situation, Behaviour, Impact
The cleanest tool I know is SBI. Three steps, in order:
- Situation — anchor it to a specific moment. "In yesterday's client call…"
- Behaviour — describe what you observed, without judgement. "…you answered the pricing question before the client had finished asking it."
- Impact — explain the effect it had. "…and I noticed they went quiet for the rest of the call."
That's it. No "you always," no character read, no sandwich of fake praise. Just a moment, a behaviour, and its impact — said out loud, close to when it happened.
Feedback about character invites defence. Feedback about behaviour invites change. Same intention, opposite outcome.
A script you can copy
If you freeze in the moment, borrow this and fill in the blanks:
"Can I share something I noticed? In [situation], you [behaviour], and the effect was [impact]. I wanted to flag it because I think you can adjust it easily — how did it look from your side?"
That last question matters more than the rest. It turns a verdict into a conversation, and it gives the other person a way in that isn't pure agreement or pure defence.
When they get defensive
Sometimes the reaction is a flinch, an excuse, or a flat "that's not fair." I've learned to treat that the way I've learned to treat objections everywhere else — not as a wall, but as information. A defensive reaction usually means the person cares, or feels unsafe, or has context you don't. None of those are reasons to retreat; they're reasons to get curious.
So I slow down. I name it gently ("I can see this landed hard"), I ask a real question, and I keep returning to the behaviour and the shared goal rather than trying to win. The point was never to be right. The point was to help someone do something well that they're currently doing in a way that's costing them.
The 5-point checklist
- Tie it to a specific moment, not a pattern or a personality.
- Describe behaviour, then impact — in that order.
- Give it soon, while it's small, not saved up for the review.
- End with a genuine question, not a verdict.
- Make it little and often, so feedback stops being an event and becomes normal.
Do that consistently and something quietly shifts: feedback stops being the scary annual thing and becomes just how your team talks. That's the whole goal — to make getting better a little less boring, and a lot less rare.
