Framework · People leadership · 2 min read
SBI feedback
Feedback in three parts (Situation, Behaviour, Impact), then an invitation to share their view, so your feedback is specific, fair and easy to act on.
- SSituation
When and where it happened, as precisely as you can.
"In yesterday's review with the PM…" - BBehaviour
What you observed, as a camera would see it. Not personality.
"…you showed three options without a recommendation…" - IImpact
The effect on users, the team or the outcome.
"…so the PM dropped the bulk-edit flow." - +Invite
Ask for their view, then agree the next step together.
"What was your thinking?"
Use it when
- A designer did something that hurt the outcome, and you need to say it without it feeling personal.
- Someone did something great, and you want them to repeat it, not just hear "great job".
- You notice your feedback sounds like a judgement ("you're not strategic enough") and want it to be specific.
How to use it
- Name the Situation. Say when and where it happened, as precisely as you can. Output: one phrase such as "In yesterday's review with the product manager…".
- Describe the Behaviour. Say what you saw or heard, as a camera would record it. No adjectives about personality. Output: one observable behaviour.
- State the Impact. Say the effect on users, the team or the outcome. This is why the feedback matters. Output: one concrete consequence.
- Invite their view. Ask "What was your thinking?" and listen. Then ask "How could we approach the next one?" Output: their perspective and an agreed next step.
- Give it soon and in the right place. Give it within days of the event. Praise in public, correct in private. Output: feedback that arrives while the event is still fresh.
Worked example
On an internal operations platform, a designer presented three options for a bulk-edit flow without a recommendation.
| Part | Corrective | Praise |
|---|---|---|
| Situation | "In yesterday's review with the product manager…" | "In the critique on Tuesday…" |
| Behaviour | "…you presented three options without a recommendation…" | "…you asked the developer about edge cases before showing the design…" |
| Impact | "…and the product manager chose the cheapest one, which drops the bulk-edit flow users need." | "…it saved us a full iteration." |
| Invite | "What was your thinking? How could we approach the next one?" | "What made you ask that first?" |
Watch out for
- Behaviour that is really a judgement. "You were rude" is a conclusion. "You interrupted the PM twice" is a behaviour.
- Impact on you only. "It annoyed me" is weak. Link the impact to users, the team or the outcome.
- Skipping the invite. Without it, SBI becomes a verdict. Their answer often changes your view of what happened.
- Saving it up. Feedback given weeks later, or only in a review, feels like an ambush. Give it within days.
Template
Write it before you say it. If you can't fill the Behaviour line with something a camera would see, rewrite it.
Person: Date of event:
Praise or corrective:
Situation: When and where?
Behaviour: What did they do or say? (observable, no personality words)
Impact: What effect did it have on users, the team or the outcome?
Invite: "What was your thinking? How could we approach the next one?"
Their view:
Agreed next step:
- The Making of a ManagerJulie ZhuoBook · 2019 (Amazon)
- Thanks for the FeedbackDouglas Stone & Sheila HeenBook · 2014 (Amazon)
- SBI Feedback ModelCenter for Creative Leadership (external site)
- How to Get Helpful Feedback on UX WorkNN/gVideo (external site)
"See on Amazon" links are affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.