SBI Model: Situation-Behavior-Impact Feedback Guide

Vague feedback gets a nod and changes nothing, and this guide shows you how to fix that with the SBI model. The first time I tried to give feedback to a senior employee at one of my early companies, I rehearsed for an hour, stumbled through it for ten minutes, and walked away thinking I had nailed it. Two weeks later the same behavior was happening, and I realized the feedback had not actually communicated anything specific.

I had said "you need to be more present in meetings," the person had nodded, and we had both moved on. Nothing changed because nothing concrete was discussed. Most management articles treat feedback as a soft skill, something you get better at with experience and emotional intelligence. That is partly true and mostly unhelpful: most feedback fails not because the manager lacks empathy but because the words are too vague to act on.

The SBI feedback model is a three-part structure (Situation, Behavior, Impact) that solves the vagueness problem. It is the most practical feedback framework I have used at small business scale. This guide is written for owners and operators who do not have a Chief People Officer to coach managers, but who still need feedback to produce behavior change.

I built FirstHR for this audience because most management content assumes a level of HR sophistication small businesses neither have nor need. The frameworks that survive at this scale are the ones an owner can run without training anyone first.

What the SBI Feedback Model Actually Is

In plain terms, SBI is a sentence template that forces feedback to be specific. Instead of saying "you need to communicate better," SBI makes you say "In yesterday's call (situation), when you interrupted Sarah twice while she was presenting (behavior), the client visibly disengaged and we lost ten minutes of meeting time (impact)." The two sentences carry the same intent. Only the second one is useful to the recipient.

Three things are true about every successful SBI implementation. First, the behavior step is observable: a video camera could have captured what you describe, with no interpretation needed. Second, the impact step is concrete: specific time lost, specific customer reaction, specific deliverable affected. Third, the feedback is delivered close to the event: within 1-2 weeks of the behavior, ideally within days. Without all three, the model produces structurally correct but practically useless feedback.

Most managers fail one of those three tests. They mix interpretation into the behavior step ("you were aggressive" instead of "you raised your voice"). They name vague impacts ("the team felt uncomfortable" instead of "Tom and Sarah did not contribute for the rest of the meeting"). They save up examples for quarterly reviews, by which point the specifics have faded. The framework gets blamed for being formal or awkward when the actual problem is in the execution.

Where SBI Came From and Why It Works

SBI was developed by the Center for Creative Leadership (CCL), a leadership development organization based in Greensboro, North Carolina. CCL has been researching and teaching leadership for over fifty years, working with leaders at organizations ranging from Fortune 500 companies to government agencies and nonprofits.

CCL calls SBI research-based, and says its own research on feedback shows the model lowers both the anxiety of giving feedback and the defensiveness of the person hearing it.

The framework works for a specific reason: it forces managers to separate three things that everyday feedback usually blurs together. Most feedback collapses observation, interpretation, and impact into a single judgment. "You were unprofessional in the meeting" is not feedback; it is a verdict. SBI splits the verdict into its components and forces you to name each one. The act of separation makes the feedback recipient's job clearer: I know what I did, I know what effect it had, and I can decide what to do about it.

CCL ties SBI to what it calls talent conversations: development discussions in which a manager moves a direct report toward better performance. They can happen at any time, though CCL counts the regular review cycle, annual reviews included, among the most critical moments for them.

The cadence is still the point: SBI earns its keep in dozens of small conversations over a year, not one heavy one. It needs no formal occasion and is small enough to use in passing, which is exactly what makes it work for small and midsize businesses (SMBs), where nobody has time for ceremonious feedback sessions.

Frequency does more work here than polish. According to Gallup research on feedback frequency, employees are 3.6 times more likely to strongly agree that they are motivated to do outstanding work when their manager gives feedback daily rather than annually. A rough SBI on Tuesday beats a perfect one in March.

The Three Parts of SBI Feedback

The framework has exactly three components, in a specific order. Skipping or reordering any of them breaks the model. Below is the structure with examples of how each part should sound in practice.

The order matters. Starting with the situation grounds the feedback in shared reality so the recipient can locate the moment in their memory. Moving to behavior forces specificity that prevents abstract debate. Closing with impact connects the behavior to outcomes the person can care about. Reverse the order and the feedback becomes harder to receive: leading with impact ("we lost ten minutes of meeting time") feels like an accusation before context is established.

Each of the three steps deserves its own discussion because each has its own failure modes. The next three sections cover them.

The Situation Step: Anchor in Specifics

The situation step describes when and where the behavior happened. It seems trivial, but many feedback failures start here. Saying "in meetings" or "when we discuss budgets" is not a situation; it is a category. A real situation is one specific moment: yesterday's 10 AM client call, last Tuesday's standup, the email thread from Friday afternoon.

Why specificity matters: the recipient needs to be able to remember the exact moment to engage with the rest of the feedback. If the situation is vague, the conversation drifts into "which meeting?" and "when do you mean?" before any actual feedback gets delivered. The five seconds spent naming the specific situation save five minutes of wandering conversation.

The single most useful test for the situation step: could the recipient pull up their calendar and find the moment? If yes, the situation is specific. If no, it needs more anchoring. Aim for time-stamped specifics whenever possible: the day, the meeting, sometimes the time.

The Behavior Step: Observable Only

The behavior step is where most SBI feedback breaks down. The rule is simple: describe what a video camera or audio recorder would have captured, with no interpretation. Most managers find this surprisingly hard because everyday language is full of interpretive shortcuts. "You were dismissive" is interpretation. "You said 'that is not how we do things' and turned to your laptop" is behavior.

The test for the behavior step: strip the sentence of any words that imply judgment. If you can still describe what happened, the description is observable. If the sentence loses meaning when you remove judgment words, the description was not behavior; it was your conclusion about behavior. Most management feedback fails this test.

Why this matters: the recipient cannot argue with a video camera. They can argue with an interpretation. When you say "you were aggressive," the conversation becomes "no I was not" and you spend twenty minutes debating whether the person is aggressive in general. When you say "you raised your voice three times," the conversation stays anchored in what actually happened. The recipient may explain the context, but they cannot dispute the observation.

The Impact Step: Concrete Consequences

The impact step describes the effect that the behavior had. Effective impact statements are specific and connected to outcomes the recipient can care about: time lost, customer reactions, team dynamics, work quality, decisions delayed. Vague impact statements ("it created tension," "it was frustrating") reduce the framework to feelings, which is not what makes SBI work.

The test for the impact step: would a third party observing the situation be able to confirm the impact? If yes, the impact is concrete. If the impact only exists in your interpretation, you have not isolated it yet. Concrete impacts can be verified; vague impacts are arguments waiting to happen.

Three types of impact work especially well at SMB scale. First, time impact: how much time was lost or saved. Second, customer or business impact: how the behavior affected revenue, customer satisfaction, or specific business outcomes. Third, team impact: how the behavior affected what other people did or did not do. These are all observable by third parties, which makes them stand up to challenge if the recipient disputes the feedback.

Vague Feedback vs SBI Feedback Side by Side

Most managers default to vague feedback because it is faster to deliver. The cost shows up later: the person does not change, the issue keeps happening, and you eventually have to have the harder conversation anyway. SBI takes 60 seconds longer per feedback session and saves hours of follow-up.

The pattern across these examples: vague feedback assumes the recipient knows what behavior the manager is referring to, knows why it matters, and knows what to do about it. SBI assumes none of those things. SBI says: here is the specific moment, here is what happened, here is what it produced. The recipient is left with no ambiguity about what to do next.

Positive SBI Feedback Examples

One of the most underused applications of SBI is positive feedback. Most managers default to using SBI only when something is wrong, which is exactly what makes the framework feel confrontational. Positive SBI is equally valuable: it reinforces specific behaviors you want to see continue. Below are five examples of positive SBI feedback drawn from common SMB situations.

Three patterns across these examples are worth noticing. First, none of them say "great job." Generic praise does not reinforce specific behavior; it just feels good in the moment. Second, every impact statement is concrete and verifiable: 20 extra minutes of engagement, four hours saved, a customer renewal. Third, the situations are recent and specific, which means the recipient can clearly remember what they did. Positive SBI is most powerful when it is delivered within 24-48 hours of the behavior.

Constructive SBI Feedback Examples

Constructive SBI follows the exact same structure as positive SBI. The difference is that the impact is negative: time lost, customer reaction worsened, team dynamics damaged, work quality reduced. Below are five examples calibrated for common SMB situations where corrective feedback is needed.

The pattern across constructive examples: every one of them describes a specific incident, an observable behavior, and a concrete consequence. None of them says "you need to be more X" or "your communication is poor." The recipient can dispute interpretations all day; they cannot easily dispute that they interrupted Sarah twice in a specific meeting. The structure produces feedback that is harder to deflect.

A 5-Step Preparation Process for SBI Feedback

SBI feedback often fails in preparation, before the conversation even starts. The manager identifies a vague concern, walks into the conversation hoping the right words will come, and ends up giving the same vague feedback they meant to fix. The five-step process below produces SBI feedback that actually lands.

Watch for two failure modes during preparation. The first is skipping Step 2 (stripping the interpretation out of the behavior). Most managers think they have isolated the behavior when they have actually just used softer interpretive language. The test: read your behavior sentence aloud and ask whether a video camera could have captured it exactly. If not, keep working on it.

The second failure mode is skipping Step 5 (the intent question) when the feedback is corrective. Without that closing question, a correction feels like a verdict. With it, the feedback becomes a conversation.

The worksheet below is that preparation on one page, with the two tests built into it: strike the judgment words out of the behavior line, and name an impact a third party could confirm. Fill it in before the conversation rather than during it, and keep the completed sheet, because the last section is where the person's answer goes.

Once you have some practice, preparing a single piece of SBI feedback takes 5-10 minutes. The first few will take longer, because separating observation from interpretation is an unfamiliar discipline. After 10-15 rounds, the structure becomes natural and preparation drops to 2-3 minutes per piece. The skill compounds quickly.

How to Actually Deliver SBI in Conversation

Preparation produces a script, but real feedback happens in conversation. The script needs to translate into 60-90 seconds of natural-sounding speech, followed by a question that opens dialogue. Most managers can write SBI better than they can deliver it, which means delivery is a separate skill that needs its own practice.

The total exchange usually runs 5-15 minutes depending on how much the recipient wants to discuss. The actual SBI delivery is 60-90 seconds; the rest is conversation. Skipping the conversation part turns SBI into a verdict, which is exactly what makes it feel formal and uncomfortable.

Extending SBI to SBII: Adding the Intent Step

CCL has published a four-step extension of the basic framework called SBII, which adds Intent as a final step. The structure: Situation, Behavior, Impact, Intent. After delivering the first three components, the manager asks about the intent behind the behavior: "What were you trying to accomplish?" or "What was going on for you?"

The point of SBII: feedback is more useful when it becomes a two-way conversation. The intent question does three things at once. First, it surfaces context the manager may have missed (the behavior may have been a reasonable response to something the manager did not see). Second, it builds psychological safety by signaling that the manager is curious, not delivering a verdict. Third, it creates space for the recipient to take ownership of the next step rather than being told what to do.

For most everyday feedback, the basic three-step SBI is sufficient. Add the intent step (SBII) when the relationship is new, when the behavior is genuinely ambiguous, when you suspect intent matters, or when you want the recipient to do most of the talking. Skip it for routine reinforcement of clear behaviors.

Regular contact is what makes either version work. In a 2015 Gallup study of US employees, people whose managers hold regular meetings with them are almost three times as likely to be engaged as people whose managers do not (Gallup). The structure matters less than whether the conversation happens at all.

SBI vs Other Feedback Frameworks

SBI is one of several feedback frameworks in active use, and each fits a different kind of conversation. Below is a comparison of the most common frameworks at SMB scale.

The most common confusion: SBI vs STAR. They look similar but serve different purposes. SBI is for the person giving feedback; STAR is for the person being asked. SBI: "In yesterday's meeting, when you interrupted Sarah, the conversation lost momentum." STAR: "In a recent client engagement, the task was to negotiate a new contract; my action was to propose a revised scope; the result was a 15% increase in deal size." Different audiences, different purposes, different mechanics. They are not interchangeable.

For most small businesses, SBI is the right default for ongoing feedback because it is the simplest framework that produces specific, actionable observations. SBII (the four-step version) adds value when intent matters or when the relationship is new. DESC fits conflict resolution better than routine feedback. STAR belongs in interviews and self-reflection, not in feedback delivery. For ongoing feedback, pick one framework and use it consistently rather than switching frameworks from one conversation to the next; the consistency is what builds the muscle memory.

Three of the others deserve a note. COIN sits close enough to SBI that the choice is really about whether you want the next step named inside the framework or handled in the conversation after it. Start, Stop, Continue belongs at team level, in a retrospective, where the output is a shared list rather than one person's behavior. And the feedback sandwich survives because it is easy to teach, not because it works.

Why SBI Works Especially Well at Small Business Scale

SBI works especially well at small business scale, for three specific reasons. That runs against the conventional view that structured feedback frameworks are corporate overhead, useful at scale but unnecessary at small businesses where the founder knows everyone personally.

First, small businesses cannot afford to lose people to vague feedback. At an enterprise, a misunderstanding between manager and employee is recoverable: there are layers of HR, performance review processes, and time to course-correct. At a small business, the same misunderstanding can mean a key person leaves within a quarter. SBI's specificity prevents the misunderstandings that vague feedback produces.

Second, small business managers are often new managers. They are first-time founders, technical leads who got promoted, or operational managers who never had formal management training. The structural simplicity of SBI is exactly what new managers need: a script they can follow before they have developed instincts. Frameworks like SBI compensate for inexperience by replacing intuition with structure.

The cost of a poor manager shows up in the numbers. In a 2023 survey of 2,066 employees reported by SHRM, 34% of the people who had a negative experience with a poor manager wanted to leave the organization, and 41% said they were stressed or anxious about reporting to work (SHRM).

Third, small businesses depend on tight feedback loops. The reason small companies sometimes beat large ones is that they decide and adjust faster. Feedback is part of that loop. Vague feedback creates lag between behavior and change; SBI compresses the lag by making the conversation directly actionable, and in a small environment that speed compounds.

Using SBI in Weekly 1:1 Meetings

The single highest-leverage place to use SBI is in weekly 1:1 meetings. Done well, weekly 1:1s become the primary mechanism for feedback at SMB scale, with SBI as the structural backbone. Done poorly, 1:1s become status reports with vague encouragement, and feedback gets saved for quarterly reviews where it is too late to be useful.

The pattern: 1:1s with SBI feel substantively different from 1:1s without. The conversation moves faster because the recipient knows exactly what was meant. Action items are more concrete. The recipient leaves the meeting with specific behaviors to start, stop, or continue, not vague resolutions to "do better."

Using SBI in Performance Reviews

Performance reviews are where SBI delivers some of its highest leverage. Most performance reviews suffer from vague language: "strong communicator," "needs improvement on follow-through," "exceeds expectations on customer focus." The employee reads the review and has no idea what specifically to do differently. Replacing each generality with 2-3 SBI examples produces reviews that actually inform behavior.

The discipline that makes this work: collecting SBI observations throughout the cycle, not at the last minute. Managers who keep a running feedback log per direct report find performance reviews easier to write and more useful to read. The investment is 30-60 seconds per observation, captured weekly. The compound benefit is a review that produces actual behavior change instead of awkward small talk.

Federal practice puts the same idea into a cycle. The Office of Personnel Management splits performance management into planning, monitoring, developing, rating, and rewarding, and defines monitoring as measuring performance and giving employees ongoing feedback on progress toward their goals. SBI is what that monitoring step sounds like inside a small business performance system.

Common Mistakes in Using the SBI Model

The eight mistakes below show up again and again in managers using SBI for the first time, from mixing interpretation into the behavior step to forgetting positive feedback altogether. All are avoidable once you understand the underlying patterns.

The pattern across these mistakes: treating SBI as a script to memorize rather than a structure to internalize. A script makes feedback feel mechanical. A structure makes feedback feel natural while preserving the discipline. The goal is not to recite Situation-Behavior-Impact verbatim every time; it is to ensure that when you give feedback, all three components are present and clear, in whatever language fits the conversation.

Training Managers to Use SBI at SMB Scale

SBI is easy to explain and hard to do well. Most managers grasp the structure in 15 minutes and need 4-8 weeks of practice to apply it consistently. At small business scale, where formal manager training programs are usually absent, the question is how to develop SBI as a team capability without enterprise-style training infrastructure.

For most small businesses, combining founder-led teaching with peer practice rounds produces the best results at the lowest cost. External training is rarely worth the budget at SMB scale unless you have specifically identified that managers need it and have no senior person who can teach the framework internally. The skill builds through practice, not through theory.

The retention case for this practice is direct. In a Gallup survey of people who quit a job in the past year (fielded November 2023), 42% said their manager or organization could have done something to prevent it, and 45% said no manager or other leader had proactively discussed their job satisfaction, performance, or future with them in the three months before they left (Gallup).

Practicing feedback is retention work; the people who leave voluntarily are often the ones nobody asked.

How FirstHR Fits

FirstHR works underneath SBI rather than inside it, running the day-to-day HR work that feedback conversations depend on.

The platform handles onboarding, employee profiles, document management, org charts, and the operational HR foundations that most small businesses need. SBI feedback, when you adopt it, lives in your manager 1:1s, your performance review process, and your team rituals.

That said, feedback works better when the underlying people operations are working. A team running SBI on top of broken onboarding will spend most of its feedback discussions explaining basic role expectations rather than developing existing employees. A team running SBI on top of consistent onboarding, clear roles, and structured 1:1s will produce feedback conversations that actually drive behavior change. FirstHR exists to handle the operational HR foundation at flat, predictable pricing, so that owners and operators can focus on the higher-impact work of giving good feedback.

Frequently Asked Questions