Giving and Taking Feedback: The SBI Model
The two ways feedback usually goes wrong
Feedback fails in two opposite directions, and most people are fluent in both.
Too soft: you hint, you cushion, you bury the point in so much reassurance that the person walks away thinking everything's fine. You were "being nice." They learned nothing, and the problem continues — which is the least kind outcome of all.
Too harsh: you say the true thing bluntly, they go defensive, and now you're in an argument about your tone instead of the issue. You were "being honest." They heard an attack and defended, and nothing changed there either.
Both failures share a root: feedback aimed at the person instead of the behaviour. "You're careless" and "you're so talented" are both about who they are — one attacks, one flatters, neither gives them anything to act on. Real feedback is about what they did, described so specifically they know exactly what to change or keep.
There's a small, boring, extremely effective structure for this, and a second half nobody teaches: how to receive feedback without your defences eating it. This lesson is both.
What you'll have at the end
- The SBI structure for giving feedback that lands
- The move that separates feedback from criticism
- A protocol for receiving hard feedback without going defensive
Giving: the SBI model
Situation → Behavior → Impact. Three parts, in order. Each one keeps the feedback on the ground and off the person.
1. Situation — anchor it in time and place
"In yesterday's team meeting…"
Pin the feedback to a specific moment. This does something important: it makes the feedback about one event, not a verdict on their character. "You always…" invites a fight (one counter-example destroys it); "yesterday, in the meeting…" is a fact that can't be argued with. Specificity is what makes feedback feel fair.
2. Behavior — describe what they did, observably
"…when Priya was explaining her idea, you cut in twice before she'd finished."
The heart of it, and where nearly everyone goes wrong. Describe the observable behaviour — what a camera would have recorded — not your interpretation of it.
| ❌ Interpretation (attacks) | ✅ Behaviour (describes) |
|---|---|
| "You were being rude" | "You interrupted twice before she finished" |
| "You didn't care about the deadline" | "The work came in two days after the date we agreed" |
| "You were dismissive" | "You said 'we don't have time for this' and moved on" |
An interpretation can be denied ("I wasn't being rude!") and now you're arguing about their character. A described behaviour is just a fact. This is the same observation-vs-interpretation distinction as SO-09, and it's the single highest-leverage move in giving feedback.
3. Impact — say what it caused
"…and the effect was that Priya went quiet for the rest of the meeting, and we didn't hear the rest of her idea."
Say what the behaviour did — to you, to others, to the work. This is the information they genuinely may not have: people are often unaware of their impact, and the impact is why the behaviour matters. Without it, feedback is just a complaint; with it, it's useful.
Then stop and listen. SBI isn't a speech you deliver and leave — after the impact, hand it over. "What's your read on it?" opens the conversation SO-03 is for. Often they didn't know, and now they do.
The rest of this walkthrough is for members
Behind this: the full step-by-step, the exercise with a verifiable output, and the downloadable cheatsheet. Everything you've read above stays free, always.