SBI: Situation-Behavior-Impact

SBI (Situation-Behavior-Impact) is the most widely taught feedback framework in modern corporate and tech environments. It is short, memorable, and does one thing exceptionally well: it strips interpretation and judgment out of feedback and replaces them with observable facts plus their downstream effect. Most failed feedback conversations fail because of imprecision and implied character attacks; SBI directly addresses both.

Origin

SBI was developed by the Center for Creative Leadership (CCL) in the 1990s as part of their executive coaching curriculum. CCL needed a tool that could be taught to non-professional feedback-givers in less than an hour and still produce measurably better conversations. SBI became that tool, and is now standard in most Fortune 500 management training programs, engineering-leadership curricula, and tech-company onboarding.

The Framework

S - Situation: When and where did this happen?
B - Behavior:  What did you specifically observe? (not infer)
I - Impact:    What was the effect on you, the team, or the work?

The discipline is in what SBI excludes:

No: "You always..."        (generalization)
No: "You were trying to..." (mind-reading)
No: "You're the kind of person who..." (character attack)
No: "Everyone thinks..."   (pluralizing the complaint)

Each of these is replaced with something concrete and first-person:

S: "In yesterday's architecture review at 2pm..."
B: "...when you interrupted Priya three times while she was explaining
    the tradeoffs..."
I: "...I noticed she stopped contributing for the rest of the meeting,
    and I felt less likely to raise my own concerns next time."

SBI converts a vague grievance into a specific, actionable piece of information.

How to Use It

The four-step SBI delivery:

1. Prepare the three elements in writing before the conversation.
   If you cannot write them out, you are not ready to deliver them.
2. Open with permission or context: "Can I share something I noticed?"
3. Deliver the three elements in order. Be specific. Be brief.
4. Stop. Let them respond. Do not add a lecture or a prescription.

SBI is for the opening move of a feedback conversation. After delivering S-B-I, the conversation becomes a dialogue — you ask questions, they respond, together you figure out next steps. SBI is not the whole conversation, it is the honest, specific entry point.

Positive SBI

SBI is equally valuable for positive feedback. Vague praise ("great work!") lands less well than specific praise:

S: "In the incident post-mortem yesterday..."
B: "...you reframed the discussion from 'who caused this' to 'what
    about the system allowed this'..."
I: "...and that shifted the whole room. Two engineers volunteered
    improvements they had been holding back. Thank you."

Most organizations under-use positive SBI. It is the cheapest high-leverage move in people management.

Tech & Company Example

A tech lead needs to give feedback to a senior engineer about PR review behavior.

Bad (vague, judgmental):
  "Sam, your code reviews are really harsh. You're discouraging people,
   especially the juniors. You need to be nicer."

Better (SBI):
  "Sam, can I share something I've noticed?

   S: In the last two weeks, specifically the PRs from Jamie
      (#1847 and #1852) and from Alex (#1861),

   B: your review comments used phrases like 'this is wrong,'
      'who taught you to write code like this,' and 'NACK, rewrite.'
      There were also five or more comments on each PR addressing
      style choices unrelated to correctness.

   I: Jamie mentioned to me that they're hesitant to open PRs now,
      and I noticed Alex has been asking other seniors to review
      instead of you. I'm worried we're losing the junior review
      pipeline and I want to understand your perspective."

The bad version invites defensiveness ("I'm not harsh, I'm thorough"). The SBI version is hard to argue with factually — the PR numbers, the quotes, the observable behavior changes are all there. The conversation that follows can be productive instead of defensive.

SBI in Async Contexts

SBI works in writing too. A typical written SBI is 3-5 sentences:

"Hey Sam — following up on something I noticed in the Ops sync today.
When the question about the retry policy came up and you said 'we've
been over this, read the doc,' Jamie went quiet and didn't raise their
other question. I want the reviews to feel safe for that kind of
question. Could we grab 15 minutes tomorrow to talk about it?"

Short, specific, and it sets up a live conversation for the nuance.

When It Works

One-on-one feedback between peers, manager-report, or report-manager
Performance review preparation (SBI gives you the specific evidence)
Code review culture coaching (model the framework in your own reviews)
Incident reviews where behavior factored in
Positive reinforcement (often even more valuable than corrective use)

When It Does Not Work

Systemic or cultural issues — SBI is about individual behavior; if the problem is a team norm or process, SBI targets the wrong layer.
Very large power gaps — A junior giving SBI to a VP-4-levels-up often fails for reasons unrelated to SBI quality; structural safety is the prerequisite.
When the "I" would be extreme — If the impact genuinely is "you will be fired," SBI is not the moment; that is a formal performance conversation.
When you do not actually know the Behavior — Hearsay SBI ("I heard you said X to Priya") undermines the framework. Only deliver SBI about behavior you directly witnessed.

Common Failure Modes

Inference disguised as Behavior — "You were dismissive" is an inference. "You interrupted three times in 4 minutes" is behavior. The line is crisp.
Missing Situation — "You've been negative lately" — when, specifically? Without a specific Situation, the feedback is a generalization.
Vague Impact — "It was bad for morale" is weak. "Jamie told me they're hesitant to ship anymore" is specific.
SBI-sandwich — Burying SBI between two pieces of fluff ("you're great, also this thing, you're great!"). Recipients see through it immediately.
Prescription as Impact — "The impact is you need to stop doing this." That is not an Impact; it is a demand. Impacts describe effects; requests for change come later in the conversation.
Weaponized SBI — Using the framework as cover for an attack by cherry-picking examples. SBI is a tool for honesty; if you are being uncharitable, the framework will not save the conversation.

SBI-I (SBI + Intent) — Some versions add a fourth step where you ask about the person's intent. "What were you trying to do?" Useful when the behavior's motivation is unclear.
COIN (Context-Observation-Impact-Next steps) — Similar structure, adds explicit Next-Step phase at the end.
CEDAR — A longer cousin that adds Emotion handling and explicit Ask.
DESC (Describe-Express-Specify-Consequences) — Assertiveness-training cousin of SBI, covered in Difficult Conversations.
Radical Candor — A philosophy more than a framework; SBI is a tactical way to deliver Radical Candor conversations.
Stop-Start-Continue — Retrospective cousin; better for team-level retros than individual feedback.