SBI Feedback: How to Use the Situation-Behavior-Impact Method (With Examples and Scripts)

SBI feedback, sometimes called the SBI feedback model, is short for Situation-Behavior-Impact, a three-part structure that the Center for Creative Leadership built as part of its leadership training programs and that has since spread into performance review templates and manager coaching guides across most industries. The premise is simple: feedback lands better when it separates fact from judgment, so instead of telling someone they're disorganized or difficult to work with, the structure has you name where something happened, what you actually observed, and what it changed, always in that order.

Each part is doing a specific job, and skipping any one of them breaks the sequence even if the other two are solid. Leave out the situation and the other person doesn't know which instance you're talking about, so they either guess wrong or assume you're describing a pattern you haven't actually shown them. Leave out the behavior and jump straight to a label like "you're unreliable," and there's nothing concrete for them to change, just a verdict to argue with. Leave out the impact and the behavior sounds like a rule you're enforcing for its own sake, which makes it easy for the other person to shrug off.

What makes this different from just "being specific" is the enforced order. Most feedback that goes wrong doesn't fail because the person forgot to be specific, it fails because they led with judgment ("that presentation was a mess") and backfilled the specifics only if the other person pushed back. The Situation-Behavior-Impact sequence flips that order so the facts come first and the reaction, if there needs to be one, comes last.

The situation is the anchor for the rest of the conversation, and it only needs one or two sentences. Name when it happened and where, specifically enough that the other person immediately knows which moment you mean without you having to describe the whole scene.

A weak situation line sounds like "you've been doing this a lot lately," which is really a behavior and impact claim disguised as a situation, without ever naming a moment. A strong situation line sounds like "in yesterday's client call, right after the pricing question came up," which gives the other person an exact anchor before you say anything evaluative at all.

Two rules make the situation line hold up. First, pick one instance, not a pattern. If you've noticed something three times, describe the most recent or most significant one, and save the pattern itself for the impact line if it's relevant. Bundling three instances into one situation line usually makes the other person defend the instance they remember most clearly rather than hear the actual point. Second, keep it recent. A situation from six weeks ago asks the other person to reconstruct a memory they may not have anymore, which weakens everything that follows it.

The behavior line is where the structure quietly turns back into an opinion, because behavior and judgment use similar-sounding words. "You were dismissive in the meeting" sounds like a behavior description, but dismissive is already an interpretation, it's your read on their tone, not something a camera would have captured.

The test for a clean behavior line is whether a neutral third party in the room would have seen or heard the exact same thing. "You checked your phone twice while Maria was presenting her numbers" passes that test. "You didn't seem interested in what Maria was saying" doesn't, because someone else in the room might have read the same phone checks as multitasking, not disinterest.

Two phrases do most of the work here: "I noticed" and "I heard." Starting the behavior line with one of them keeps you anchored to observation rather than inference, and it also signals to the other person that you're describing your own vantage point rather than delivering a verdict on who they are. If you find yourself reaching for a word that describes someone's attitude, mindset, or character instead of their actions, that's usually the sign the behavior line has drifted into judgment and needs to be rewritten.

Impact is the part that gives the other two a reason to matter, and it's also the part people rush through most, often collapsing it into a single vague line like "it wasn't great" or "it affected the team." A weak impact statement tells the other person that something went wrong. A strong one tells them specifically what changed because of what they did.

Concrete impact ties to something measurable or visible: a deadline that slipped, a client who asked a follow-up question that could have been answered upfront, a teammate who had to redo a section of work. "It affected the project" is vague enough that the other person can't picture the actual cost. "I had to rebuild the slide the night before the board meeting" gives them something specific to weigh.

Impact also doesn't have to be negative, which is where a lot of people underuse SBI feedback. "When you walked the new hire through the account setup step by step yesterday afternoon, she told me afterward it was the first time she felt like she actually understood the tool" follows the same structure, and it's often more useful for reinforcing behavior you want repeated than for correcting behavior you want to stop. Reserving it only for corrections is one of the more common ways people underuse the method.

Reading the structure explained is one thing. Hearing what it sounds like in an actual sentence is another. Here are five SBI feedback examples across different relationships and directions, each one labeled so you can see where situation ends and behavior begins.

SBI feedback and constructive criticism aren't opposites. The method is one specific way to structure constructive criticism, but the two terms get used differently in practice. Constructive criticism examples usually cover a wider range of wording styles, some built around questions, some around shared framing ("this affects both of us"), some around offering to help. This structure is narrower on purpose: a fixed three-part sequence, not a general style of phrasing, which makes it easier to teach and easier to check yourself against mid-conversation.

The same distinction applies to negative feedback more broadly. Negative feedback describes the category, feedback about something that isn't working, while Situation-Behavior-Impact describes the mechanism for delivering it. You can give negative feedback badly, as a character judgment, or well, using the structure, and the difference between those two versions is usually the entire reason a conversation goes sideways or doesn't.

It's also worth separating the method from the practice of it. This guide covers the structure itself and how to word each part. Practicing it out loud, adjusting your pacing, hearing how a script actually sounds when you say it under pressure, is a different exercise, and it's usually the part people skip even after they've memorized the sequence.

A few habits show up constantly in feedback that technically follows the format but doesn't actually work.

Folding the behavior into the situation. "In yesterday's meeting, when you were being dismissive" tries to do both jobs in one sentence and skips the actual observable behavior entirely. Split it: name the meeting, then name specifically what you saw.

Turning the impact into a character read. "It made you look unprepared" restates a judgment instead of naming a consequence. "The client asked to reschedule because the numbers weren't ready" names a consequence. If your impact line could be answered with "no it didn't," it's probably not concrete enough yet.

Stacking situations. Three different meetings compressed into one piece of feedback ("you've done this in the last three stand-ups") turns a specific structure into a vague pattern complaint, and the other person will usually argue about which instance you actually mean instead of hearing the point.

Skipping the impact because it feels obvious. It rarely is. What feels self-evidently important to you, a slipped deadline, a tone in a meeting, often isn't obvious to the person who caused it until you say what it actually changed.

Using SBI feedback only for corrections. The structure works just as well for reinforcing behavior you want to see again, and skipping that use is one of the easiest ways to leave a useful tool half-used.

Writing out a script and saying it out loud for the first time in the actual conversation are two different levels of preparation, and the gap between them shows up in pacing more than wording. A situation line that reads fine on paper can come out rushed or accusatory if you haven't heard yourself say it first, and an impact line that felt clear in your head can trail off if you haven't rehearsed the transition into it.

Reading this guide gets you the structure. Saying the actual script out loud, the missed-deadline conversation, the upward feedback to a manager, the positive version you've been meaning to give someone, is what tells you whether the wording holds up under real delivery. SayNow AI lets you rehearse SBI feedback scripts like these out loud before the real conversation, so the pacing and tone are already familiar by the time you're saying them to the actual person.