Contents
Use this when you need to deliver feedback that lands without triggering defensiveness. Situation-Behaviour-Impact strips away judgment, interpretation, and character attribution — leaving only what happened, what the person did, and what it caused. Three sentences. No adjectives about who someone is. Just observable facts about what they did and what followed.
Section 1
What This Tool Does
Most feedback fails before it's finished. Not because the content is wrong, but because the delivery triggers a threat response in the first four seconds. "You're not a team player." "You need to be more strategic." "Your communication skills need work." Each of these tells the recipient something about their character — and the moment feedback becomes about identity rather than action, the prefrontal cortex goes offline and the amygdala takes over. The recipient stops listening and starts defending. You've lost them. The conversation that follows is theatre.
The Center for Creative Leadership developed the Situation-Behaviour-Impact model — SBI — to solve this specific problem. Not the problem of what to say, but the problem of how to structure what you say so the other person can actually hear it. The mechanism is almost absurdly simple: describe the situation (when and where), describe the observable behaviour (what the person did or said, in terms a video camera could capture), and describe the impact (what happened as a result — to you, to the team, to the outcome). That's it. Three components. One sentence each, if you're disciplined.
The simplicity is deceptive. SBI works because it systematically removes every element that makes feedback feel like an attack: labels, generalizations, mind-reading, and moral judgment. "You're dismissive in meetings" contains all four. "In yesterday's product review, when you checked your phone while Maria was presenting the user research findings, she lost her train of thought and the team didn't get to discuss the methodology concerns" contains none. Same underlying issue. Radically different neurological response in the receiver.
What makes this more than a politeness technique is the precision it forces on the giver. Most people, when asked to deliver feedback, discover they can't actually describe the behaviour they're reacting to. They have a feeling — frustration, disappointment, concern — and they've attached a label to the person who caused it. SBI forces you to reverse-engineer that label back to the specific observable event that generated the feeling. Sometimes you discover the behaviour wasn't what you thought it was. Sometimes you realise the impact was on you personally, not on the team, and the feedback conversation needs to be framed differently. The preparation discipline is as valuable as the delivery structure. Often more so.
Section 2
How to Use It — Step by Step
Instructions on the left. Worked example — giving feedback to a senior engineer who derailed a cross-functional planning session — on the right.
Step 1 — Isolate the Situation
Anchor to a specific time, place, and context
Pin the feedback to a single, identifiable moment. Not "lately" or "in general" or "whenever we have meetings." A specific date, a specific meeting, a specific context. This does two things: it prevents the recipient from feeling that you've been cataloguing their failures for months, and it gives them a concrete memory to access. If they can remember the moment, they can evaluate your feedback against their own recollection. Vague situations produce vague defensiveness. Specific situations produce specific reflection.
Worked example
Senior engineer in sprint planning
"During Monday's Q3 sprint planning session with the product and design teams..." — the recipient knows exactly which meeting, who was present, and what was being discussed. No ambiguity. No sense that this is a pattern accusation disguised as a single instance.
Step 2 — Describe the Behaviour
State only what a camera would have recorded
This is the hardest step and where most people fail. The behaviour must be observable — words spoken, actions taken, things done or not done. Not interpretations of intent. Not adjectives about attitude. "You were dismissive" is an interpretation. "You interrupted the product manager three times and said 'we've already tried that' without asking what was different about the new proposal" is a behaviour. The test: could a stranger watching a video of the meeting confirm your description? If yes, it's behaviour. If they'd need to read the person's mind to confirm it, it's interpretation. Strip it back.
Worked example
Observable actions, not character judgments
"...you interrupted Priya twice while she was presenting the proposed architecture changes, and when she finished, you said 'this won't scale' without referencing any specific technical constraint or offering an alternative approach." Every element is verifiable. The recipient may disagree with the impact, but they can't dispute what they said and did.
Step 3 — Articulate the Impact
Explain what happened as a result — to people, outcomes, or you
Impact is where the feedback gets its weight. Without impact, you're just narrating events. The impact can be on the team ("the design team stopped contributing for the rest of the session"), on the outcome ("we left without alignment on the architecture, which will delay the sprint by at least two days"), on the relationship ("Priya told me afterward she doesn't want to present to the engineering team again"), or on you personally ("I felt uncomfortable and wasn't sure whether to intervene"). Be honest about whose impact you're describing. First-person impact ("I felt...") is harder to dispute than third-person impact ("the team felt..."), but both are valid when grounded in observable evidence.
Worked example
Concrete consequences, not vague disappointment
"The result was that Priya stopped presenting her rationale, the design team went quiet for the remaining forty minutes, and we ended the session without a decision on the architecture. I've since learned that Priya has asked her manager to send someone else to future planning sessions." The impact is specific, consequential, and verifiable. It's not "people were upset." It's: a decision didn't get made, a key contributor withdrew, and a working relationship may be damaged.
Step 4 — Pause and Invite
Stop talking. Let the recipient respond.
After delivering the SBI statement, stop. Do not fill the silence. Do not soften it with "but I know you didn't mean to" or "it's not a big deal." The pause is structural — it transfers ownership of the conversation to the recipient. They may explain context you didn't have. They may acknowledge the impact. They may push back on your description of the behaviour. All of these are productive. What you're creating is a dialogue, not a verdict. If you keep talking after the impact statement, you're delivering a monologue, and monologues don't change behaviour. Ask a genuine question: "What was going on for you in that moment?" or "How do you see it?" Then listen.
Worked example
Creating space for the other side
"...Priya has asked her manager to send someone else to future planning sessions. I wanted to share this with you directly. What's your perspective on what happened in that meeting?" Then silence. The engineer might reveal that they'd already flagged the scaling concern in a document nobody read, and their frustration boiled over. That context matters. It doesn't erase the impact, but it changes the conversation from "you did a bad thing" to "how do we solve this together."
Section 3
When It Works Best
✓
Ideal Conditions for SBI
| Dimension | Best fit |
|---|---|
| Feedback type | Developmental feedback — both reinforcing (positive) and redirecting (corrective). SBI is often taught as a tool for difficult conversations, but it's equally powerful for praise. "In the board meeting, when you walked the investors through the cohort analysis without reading from slides, the room visibly leaned in and we closed the round two weeks later" is far more useful than "great job on the fundraise." |
| Relationship dynamic | Any direction: manager-to-report, peer-to-peer, report-to-manager, cross-functional. The structure is especially valuable when giving feedback upward or laterally, where you lack positional authority and the risk of the conversation going sideways is highest. The objectivity of the format lends credibility regardless of hierarchy. |
| Emotional temperature | Best delivered when the giver has had time to separate their emotional reaction from the observable facts. If you're still angry, you'll contaminate the behaviour description with interpretation. A 24-to-48-hour cooling period between the event and the conversation is ideal — long enough to gain perspective, short enough that the details remain vivid for both parties. |
| Behavioural specificity | Works when the issue is a specific, describable behaviour — not a personality trait, a values misalignment, or a capability gap. "You didn't prepare a risk analysis for the proposal" is SBI-ready. "You lack strategic thinking" is not — that's a judgment that needs to be decomposed into specific behavioural instances before SBI can be applied. |
| Cultural context | Particularly effective in direct-communication cultures (US, Netherlands, Australia, Israel) and in organisations that have established feedback as a norm rather than an event. In high-context cultures (Japan, Korea, many Middle Eastern contexts), the directness of SBI may need to be softened or delivered through intermediaries — the structure still helps, but the delivery channel matters. |
| Stakes | Scales from low-stakes coaching moments to high-stakes performance conversations. For formal performance reviews, SBI provides the evidentiary backbone — each piece of feedback grounded in a specific situation, behaviour, and impact rather than vague impressions accumulated over months. |
Section 4
When It Breaks Down
⚠
Failure Modes
| Failure pattern | What goes wrong | What to use instead |
|---|---|---|
| Smuggled judgments | The giver uses SBI's structure but loads the behaviour description with interpretive language: "When you aggressively pushed back on the timeline..." The word "aggressively" is a judgment, not an observation. The recipient hears the judgment, not the structure, and the model's entire benefit evaporates. This is the most common failure — people think they're being objective because they're using the format, while their word choices betray the interpretation they're trying to avoid. | Write out the behaviour description in advance. Remove every adjective and adverb. Read it aloud. If a neutral observer could dispute any word, revise. |
| Pattern feedback forced into a single instance | The real issue is a recurring pattern — someone consistently dominates meetings, repeatedly misses deadlines, habitually interrupts. SBI anchors to a single situation. Using one instance to address a pattern feels disproportionate to the giver and confusing to the recipient, who thinks "that was one time." The tool isn't designed for pattern conversations. | Use SBI for the most recent and clearest instance, then explicitly name the pattern: "This is the third time I've noticed this dynamic. Can we talk about what's driving it?" |
| Mechanical delivery | The giver recites the three components like a script — robotic, rehearsed, devoid of genuine care. The recipient feels processed, not respected. SBI is a thinking structure, not a speech template. If it sounds like you're reading from a framework, you've lost the human connection that makes feedback land. | Internalise the structure but deliver it conversationally. The preparation is rigid; the delivery should feel natural. |
| Impact fabrication | The giver can describe the situation and behaviour clearly but can't articulate a real impact — so they inflate or invent one. "The team lost trust in you" when actually one person was mildly annoyed. Exaggerated impact undermines credibility. If the impact is small, say so honestly. Small impacts are still worth discussing if the behaviour is likely to recur. | Be honest about the scale of impact. "It didn't derail the meeting, but I noticed two people disengage" is more credible than manufactured catastrophe. |
| Systemic issues disguised as individual feedback | The behaviour you're observing is a rational response to a broken system — someone cuts corners because the process is impossible to follow within the given timeline, or someone dominates meetings because there's no facilitation structure. Giving individual SBI feedback for systemic problems is unfair and ineffective. The behaviour will recur because the system incentivises it. | Use the Iceberg Model or 5 Whys to determine whether the behaviour is individual or systemic before initiating the feedback conversation. |
| Weaponised objectivity | In toxic environments, SBI can be used to build a paper trail against someone rather than to help them improve. The structure's apparent objectivity makes it easy to document a series of "behaviour + impact" statements that, taken together, construct a case for termination rather than a path for development. The recipient senses the intent immediately. | Check your intent before using the tool. If the goal is documentation rather than development, be honest about that — with yourself and with HR. SBI is a development tool, not a prosecution brief. |
The most dangerous failure mode is smuggled judgments — and it's dangerous precisely because the giver doesn't realise they're doing it. The SBI structure creates a feeling of objectivity. You've followed the steps. You described the situation, the behaviour, the impact. But embedded in your "behaviour" description are words like "dismissive," "aggressive," "careless," "unprofessional" — each one a conclusion you've drawn, not a fact you've observed. The recipient's brain detects the judgment instantly, even if they can't articulate why the feedback feels unfair. The fix is unglamorous but essential: write out your SBI statement before the conversation. Read the behaviour component aloud. For every word, ask: would a video camera capture this? "Interrupted three times" passes. "Was dismissive" does not. This five-minute preparation exercise is the difference between feedback that changes behaviour and feedback that damages a relationship.
Section 5
Visual Explanation
SBI model — the three components applied to the sprint planning feedback example. Each component strips away a layer of subjective interpretation, leaving only observable, discussable facts.
Section 6
Pairs With
SBI is a delivery mechanism for a single piece of feedback. It doesn't help you decide whether to give feedback, prepare for the emotional dynamics of the conversation, or structure what comes after. These tools fill those gaps.
Use before
Ladder of Inference
Before you deliver SBI feedback, climb down your own Ladder of Inference. You observed something, selected certain data from it, added meaning, made assumptions, drew conclusions, and formed beliefs. SBI forces you to go back to the bottom rung — the observable data — but only if you've first recognised how far up the ladder you've already climbed. Without this self-check, your "behaviour" description will be contaminated by the conclusions you reached three rungs ago.
Use before
Iceberg Model
Is the behaviour you're about to address a surface event, or a symptom of something structural — unclear role expectations, misaligned incentives, a broken process? The Iceberg Model helps you determine whether individual feedback is the right intervention or whether you need to address the system underneath. Giving SBI feedback for a systemic problem is like treating a fever without diagnosing the infection.
Use after
Active Listening
After delivering your SBI statement and pausing, the conversation shifts to the recipient's perspective. Active Listening — reflecting back what you hear, asking clarifying questions, resisting the urge to rebut — is what turns a feedback delivery into a feedback dialogue. SBI opens the door. Active Listening is how you walk through it together.
Use after
Nonviolent Communication
When the conversation moves beyond the initial SBI statement into deeper territory — unmet needs, recurring frustrations, relationship repair — NVC provides the framework. SBI gets the facts on the table. NVC helps both parties articulate the feelings and needs underneath those facts. They're complementary: SBI is the opening move, NVC is the extended conversation.
Mental model
Reframing
Sometimes the feedback conversation reveals that the "problem behaviour" looks entirely different from the recipient's vantage point. Reframing — the deliberate practice of seeing the same situation through a different lens — keeps you from locking into your initial interpretation. The engineer who interrupted Priya might have been trying to protect the team from a technical dead end. That doesn't erase the impact, but it reframes the conversation from "stop being rude" to "how do we raise technical concerns without shutting down presenters."
Mental model
STAR Method
STAR (Situation, Task, Action, Result) is SBI's structural cousin, designed for self-narration rather than feedback delivery. Understanding both models clarifies the distinction: STAR is how you describe your own actions in an interview or review. SBI is how you describe someone else's actions in a feedback conversation. The shared DNA — anchor to a situation, describe specific actions, articulate outcomes — reinforces why specificity is the universal solvent for vague, unproductive conversations.
Section 7
Real-World Application
Google's Project Oxygen — rebuilding manager feedback from observable behaviours
The scenario
In 2008, Google's People Analytics team launched Project Oxygen to answer a question many engineers considered already settled: do managers matter? The data said yes — teams with effective managers had lower turnover, higher satisfaction, and better performance. But the follow-up question was harder: what specifically do effective managers do? Google's initial manager feedback surveys were full of vague assessments — "good communicator," "empowering," "has a clear vision." These told managers they needed to improve but gave them nothing actionable to change. A manager rated poorly on "communication" had no idea which communication, in which context, was the problem.
How the tool appliedGoogle's People Operations team restructured their upward feedback instruments around behavioural specificity that mirrors SBI's core logic. Instead of asking "Is your manager a good communicator?" they asked questions anchored to observable situations and behaviours: "When you share a new idea with your manager, does your manager ask follow-up questions to understand it before responding?" and "In your last 1:1, did your manager provide specific examples when giving you feedback on your work?" The feedback recipients — managers — received data tied to specific interaction patterns rather than abstract trait ratings. The impact component was captured through outcome correlations: teams whose managers scored high on these behavioural questions showed measurably higher psychological safety scores and innovation output.
What it surfacedThe behavioural specificity revealed that Google's best managers weren't distinguished by charisma, technical depth, or strategic vision — the traits most people associate with leadership. They were distinguished by a small set of observable, coachable behaviours: asking questions before giving answers, providing feedback with specific examples, and expressing interest in direct reports' career development through concrete actions (not just stated intentions). The worst-performing managers weren't "bad leaders" in some holistic sense — they simply didn't do these specific things. That distinction mattered enormously for intervention design. You can't coach someone to "be a better leader." You can coach someone to ask two follow-up questions before responding to a proposal.
The non-obvious factorWhat made Google's application distinctive was the scale at which they validated the SBI principle. Across tens of thousands of manager-report relationships, the data consistently showed that feedback specificity — the degree to which feedback was anchored to observable situations and behaviours rather than trait labels — predicted whether the feedback actually changed the manager's behaviour in subsequent quarters. Managers who received "you need to communicate better" showed no measurable improvement. Managers who received "in team meetings, when engineers raise concerns, you tend to respond immediately with solutions rather than asking clarifying questions — and the engineers report feeling unheard" showed significant behavioural change within one quarter. The mechanism was identical to SBI: strip the judgment, describe the behaviour, show the impact. Google proved it works not just in a single conversation but as an organisational feedback architecture.
Section 8
Analyst's Take
Faster Than Normal — Editorial View
SBI endures because it solves the right problem at the right level of abstraction. Most feedback frameworks try to address the entire arc of a developmental conversation — the relationship context, the emotional dynamics, the goal-setting, the follow-up. SBI does one thing: it structures the opening statement so the recipient can hear it without their defences activating. That narrowness is a feature. The tool doesn't try to make you a better coach. It tries to make your first three sentences land cleanly. Everything else — the dialogue, the mutual understanding, the behaviour change — flows from whether those first sentences triggered reflection or triggered defence. Get the opening right and the rest of the conversation has a chance. Get it wrong and nothing downstream matters.
The failure I see most often in practice isn't structural — people learn the S-B-I format in twenty minutes. It's the inability to separate observation from interpretation under emotional pressure. A founder tells me they used SBI with a direct report. I ask them to repeat the behaviour component. Nine times out of ten, it contains at least one smuggled judgment: "carelessly," "without thinking," "in a way that showed they didn't care." They don't hear it. The judgment feels like a fact to them because they've been sitting with it for days. This is why written preparation is non-negotiable. Not optional. Not "nice to have." Write the three components down. Read the behaviour sentence. Circle every word that a neutral observer couldn't verify from a recording. Replace or delete those words. This takes five minutes and is the single highest-leverage investment you can make in any feedback conversation.
The modification I recommend most: add a fourth component — Intent inquiry. After delivering Situation, Behaviour, and Impact, explicitly ask about the recipient's intent: "What were you trying to accomplish in that moment?" This does two things. It signals genuine curiosity rather than prosecution. And it surfaces the gap between intent and impact — which is where almost all interpersonal friction lives. The engineer who interrupted Priya probably intended to save the team from a flawed architecture. His intent was constructive. His impact was destructive. When both parties can see that gap clearly, the conversation shifts from blame to problem-solving: "How do you raise legitimate technical concerns in a way that doesn't shut down the presenter?" That's a question worth answering together. SBI gets you to the table. The intent question gets you to the real conversation.
Section 9
Top Resources
01
Feedback That Works: How to Build and Deliver Your Message — Center for Creative Leadership (2nd Edition, 2019) [VERIFY]
Primary sourceThe original source from the organisation that developed SBI. A slim, practical guide — under 40 pages — that walks through the model with worked examples across corporate, nonprofit, and educational contexts. Worth reading for the nuance on positive feedback delivery, which most SBI training overlooks. The second edition includes updated guidance on virtual and asynchronous feedback.
02
Book
The scientific foundation for why SBI works. Kahneman's research on System 1 (fast, automatic, judgment-prone) and System 2 (slow, deliberate, analytical) explains the cognitive machinery that makes unstructured feedback fail. When you say "you're dismissive," you're delivering a System 1 conclusion. SBI forces you back to System 2 — the observable data that preceded the conclusion. Chapters on anchoring, the halo effect, and substitution are directly relevant.
03
Book
Horowitz's chapter on giving feedback ("The Right Way to Lay People Off" and the sections on radical honesty in management) provides the operational context that SBI lives inside. His principle — "don't put it off, don't be vague, and don't make it about you" — is SBI distilled to its essence by someone who had to deliver feedback at the highest stakes. Read this for the why behind the how.
04
Book
Netflix's feedback culture — where candid, specific feedback is an explicit organisational norm — is the most visible large-scale implementation of the principles underlying SBI. Hastings and Meyer describe how Netflix trains employees to give feedback using the "4A" framework (Aim to assist, Actionable, Appreciate, Accept or discard), which shares SBI's insistence on behavioural specificity and impact articulation. The chapter on feedback is a masterclass in what happens when an entire company commits to observable-behaviour feedback at scale.
05
Nonviolent Communication: A Language of Life — Marshall Rosenberg (2003) [VERIFY]
BookRosenberg's framework — Observation, Feeling, Need, Request — is SBI's deeper cousin. Where SBI structures the opening statement of a feedback conversation, NVC structures the entire emotional exchange that follows. The "Observation" component in NVC is identical in principle to SBI's "Behaviour" component: describe what happened without evaluation. Reading Rosenberg after learning SBI reveals that the same cognitive discipline — separating observation from interpretation — is the foundation of every effective communication framework. The difference is depth: SBI is a scalpel for a single feedback moment; NVC is a philosophy for how humans can speak to each other without violence.
Decision Tools Library — Browse by phase
Why this matters next
mental modelsIncentives
Ladder of Inference applied the Incentives mental model
mental modelsLeverage
Ladder of Inference applied the Leverage mental model
mental models5 Whys
Ladder of Inference applied the 5 Whys mental model
mental modelsScale
Ladder of Inference applied the Scale mental model
mental modelsEnvironment
Ladder of Inference applied the Environment mental model
mental modelsFeedback
Ladder of Inference applied the Feedback mental model
Continue exploring
MPSMNCAL
Decision tool
Minto Pyramid
Structure written communication top-down — lead with the answer, then support wi
Decision tool
STAR Method
Structure persuasive narratives about actions and outcomes — Situation, Task, Ac
Decision tool
Nonviolent Communication
Navigate conflict by expressing observations, feelings, needs, and requests with
Decision tool
Active Listening
Structure the receiving side of communication — reflect, paraphrase, clarify, va
More like this, in your inbox
I send a newsletter every week — free, no spam, unsubscribe anytime.