The SBI feedback framework: a script for feedback that doesn’t damage trust
SBI stands for situation, behavior, impact. It’s a three-part structure for feedback conversations: name the situation (when and where), describe the behavior you actually observed (not your read on someone’s character), then state the impact it had. The reason it works where most feedback conversations don’t is simple. It keeps the conversation about what happened, not who someone is.
“You’re not a team player” gets defensiveness, every time, because there’s nothing in it to respond to except an accusation. “In yesterday’s client call, you cut in three times while Priya was walking through the numbers, and the client stopped directing questions to her after that” gets a different reaction. There’s something specific to agree with, push back on, or explain.
Why most feedback conversations go sideways before they start
Most feedback fails at the first sentence. A manager opens with a trait judgment — lazy, disorganized, not a team player — and the other person spends the rest of the conversation defending their character instead of hearing the point. By the time the manager gets to what they actually wanted changed, the door’s already closed.
SBI works because it removes the trait judgment from the opening. You’re not diagnosing someone’s personality. You’re describing three things: where it happened, what you saw or heard, and what resulted from it. All three are checkable facts, which is exactly why they’re harder to argue with and easier to hear.
The three parts, with an example for each
Situation. Anchor it in time and place. Not “you always do this” — a specific instance. “In this morning’s stand-up.” “During the client call yesterday afternoon.” Vague timing invites the response “that’s not fair, that was one time,” and now you’re arguing about frequency instead of talking about the behavior.
Behavior. Describe only what you saw or heard, not your interpretation of it. “You interrupted Priya three times” is behavior. “You were being dismissive of Priya” is a judgment wearing behavior’s clothes, and it’ll get treated like one. If you find yourself reaching for an adverb or an adjective to describe the behavior, you’ve probably drifted from observation into interpretation. Cut it back to what a camera would have recorded.
Impact. State what actually resulted, for the team, the client, or the work. “The client stopped asking Priya direct questions for the rest of the call.” “We missed the filing deadline because the draft sat in your inbox for four days.” This is the part that gives the other person a reason to change something. Without it, SBI is just a more polite way of listing complaints.
A full script
In this morning’s stand-up, you cut off two teammates mid-sentence while they were giving updates. After the second time, the room got noticeably quieter, and the last two updates were much shorter than usual.
That’s a complete SBI statement in three sentences. Say it, then stop talking. The instinct is to soften it with an explanation or rush into a solution. Don’t. Let the other person respond first.
What it sounds like in an actual conversation
A team lead we worked with had been putting off a conversation with a senior report for two months. The report was strong technically and difficult to challenge in meetings — he’d talk over people, then get frustrated when the room went quiet.
The team lead had tried “you need to work on your communication style” once, and it went nowhere. Too vague to act on, and vague enough to feel like a character attack.
The second attempt used SBI. “In yesterday’s planning meeting, you interrupted Meera twice while she was presenting her estimate, and she didn’t finish the point either time. The team ended up planning the sprint around your numbers without hearing hers.” The report’s first response was to explain he hadn’t meant to cut her off. That’s fine. The specificity of the situation and behavior gave him something concrete to respond to, instead of a character he had to defend.
The conversation that followed was about what to do differently in the next meeting, not about whether he was a good communicator in general. That’s the shift SBI is built to produce.
What SBI doesn’t fix
The framework structures what you say. It doesn’t make a manager willing to say it. If someone’s been avoiding a conversation for two months, learning SBI gives them better words for the conversation, but it doesn’t move them from avoidance to action on its own. That’s a separate skill, closer to confidence and conflict tolerance than to structure, and it’s usually the real reason feedback conversations don’t happen at all.
SBI also assumes you’ve actually observed the behavior. If you’re working from a secondhand account, say so, and treat the conversation as a fact-finding one before you use SBI to deliver a conclusion.
When SBI is enough, and when it isn’t
For most day-to-day feedback, a good SBI statement is the whole job. For a pattern that’s repeated despite feedback, or a report who gets defensive no matter how the message is framed, the structure alone won’t carry the conversation. That’s a facilitation problem more than a framework problem, and it’s usually where a manager needs practice with a real person pushing back, not another article to read.
If your managers already know a framework like SBI but still aren’t having the conversations, that’s the gap our feedback training program is built to close. Two days, practiced live, with the actual conversations your managers are avoiding.