SBI: feedback that names behavior, not character

Describe what a camera would have seen — not who you’ve decided the person is.

The idea

Good feedback has three parts and one habit. Anchor to a specific Situation (“in yesterday’s review”), describe the observable Behavior (“the deck went out two hours late”), and state the Impact you saw (“the client saw a draft”). Then ask for their view instead of handing down a verdict. Traits like “careless” can’t be disputed or fixed — only defended. Behaviors can be discussed. Build a line below and watch the listener react.

Scenario 1 — a missed deadline

You need to raise a deadline that slipped. Assemble the line.

listener’s defensivenesscalm
Scenario
1 of 3
Defensiveness
0 · calm
Line status
incomplete

Pick one tile per row. Watch the trait tiles push the meter into the warm zone, and the observable-behavior tiles keep the listener open.

How it works

Four moves, in order — the last one keeps it a conversation, not a sentence:

S  Situation  Pin it to one recent moment.
              "In yesterday's review" — not "you always".

B  Behavior   Say what a camera captured.
              "Sent the deck two hours late" —
              not "you're careless". Traits can't be fixed.

I  Impact     State the effect you observed.
              "The client saw a draft and we lost time."

?  Then ask   End with a genuine question, not a verdict.
              "What happened on your end?"

A template you can lean on:

"In [specific situation],
 I noticed [observable behavior].
 The impact was [what you saw happen].
 What's your read on it?"

When to use it

FitsTrade-off
One-on-ones, peer feedback, in-the-moment corrections, coaching conversations.SBI needs a moment you observed. For secondhand or aggregate feedback (“people say…”) gather specifics first. And it’s for behavior change, not for delivering a final verdict — a rating or termination needs clarity, not open questions.

Watch out for

Worked example

The interviewer asks, “Tell me about a time you gave difficult feedback.” A weak answer: “I told them they were being careless.” A strong, SBI-shaped one: “On the payments pull request, I pointed out that three tests were commented out and the null check was missing. I said that’s why it failed in staging and blocked the release for an hour — then I asked what happened. They’d rushed a hotfix; we agreed on a pre-merge checklist. Naming the behavior instead of calling them careless kept it a problem-solving conversation, not an argument.”

Check yourself

Which of these is behavior, not a trait?

You close with: “So don’t do that again, okay?” What’s off?