SBI Model: Situation-Behavior-Impact Feedback Guide

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. Feedback is mostly a structural problem: most feedback fails not because the manager lacks empathy but because the words themselves are too vague to act on. "Be more professional" cannot be acted on. "In yesterday's call, when you interrupted Sarah twice, the conversation lost momentum" can be acted on. The difference is the structure, not the manager.

This guide explains the SBI feedback model, 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. The guide is written for owners and operators running 5-50 person companies who do not have a Chief People Officer to coach managers, but who still need feedback to actually 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.

What the SBI Feedback Model Actually Is

The simple working description: 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. SBI emerged from their research on what makes feedback actually produce behavior change, as opposed to feedback that produces only awkwardness.

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.

According to CCL's research on SBI, the framework was designed to help managers hold what they call "talent conversations": ongoing development discussions that build trust over time rather than the high-stakes annual reviews that produce defensiveness. The cadence is the point. SBI is not designed for one heavy conversation; it is designed for dozens of small ones over the course of a year.

For small businesses, this origin matters because it means the framework was designed for repeatability, not for ceremony. Managers who use SBI 2-4 times a week per direct report produce more behavior change than managers who craft a perfect SBI for the quarterly review. The framework is small enough to use in passing, which is exactly what makes it work at SMB scale where there is no time for ceremonious feedback sessions.

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 most 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 cost is minimal; the benefit is significant.

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 defend a video camera. They can defend 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 that 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 did 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.

For broader practice on giving feedback effectively, the employee feedback guide covers the full feedback toolkit at SMB scale, including when to use SBI and when other approaches fit better.

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 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 usually fails not in delivery but in preparation. 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.

Two failure modes to avoid during preparation. First, do not skip Step 2 (stripping interpretation from the behavior step). 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. Second, do not skip Step 5 (asking about intent). Without the closing question, SBI feels like a verdict. With it, the feedback becomes a conversation, which is the entire point of using the framework.

The total preparation time for a single SBI feedback is 5-10 minutes once you have practice. The first few times will take longer because the discipline of separating observation from interpretation is unfamiliar. After 10-15 SBI feedbacks, the structure becomes natural and the preparation time 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 practice is its own separate skill.

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.

For practical context on how SBI fits into the broader rhythm of manager-employee conversations, the 1:1 meeting guide covers the weekly conversation cadence that makes feedback like SBI possible at SMB scale.

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. The full discussion of intent versus impact is covered in Gallup's research on the manager-employee relationship, which consistently finds that two-way feedback conversations build trust faster than one-way feedback delivery.

SBI vs Other Feedback Frameworks

SBI is one of several feedback frameworks in active use. Each has strengths and weaknesses, and choosing the right one for the situation matters. 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. Pick one framework and use it consistently rather than switching frameworks based on the conversation; the consistency is what builds the muscle memory.

Why SBI Works Especially Well at Small Business Scale

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

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

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.

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. SHRM's performance management toolkit covers the broader principles, but the SMB-specific application is that speed of feedback compounds in small environments where every day matters.

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."

For the broader practice of running effective 1:1s, including agenda structure, frequency, and how to balance status updates with feedback, the 1:1 meeting guide covers the full practice.

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.

For broader context on running performance reviews effectively at SMB scale, including frequency, structure, and how to integrate SBI examples, the performance review guide covers the full process. OPM's performance management framework also offers a useful federal-government reference for how structured feedback fits into broader performance systems.

Common Mistakes in Using the SBI Model

The mistakes below appear consistently across managers using SBI for the first time. 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, the founder-led teaching plus peer practice rounds combination 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.

For the broader practice of developing managers at small business scale, the leadership development guide covers the manager skills that make any feedback framework work, not just SBI. Work Institute research on retention consistently finds that manager quality is among the top factors employees cite when leaving voluntarily; investment in feedback practice is investment in retention.

How FirstHR Fits

The honest disclosure: FirstHR is not a performance management or feedback platform. We do not have a dedicated SBI tool, feedback workflow, or 1:1 management module. 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, will live in your manager 1:1s, your performance review process, and your team rituals, not in dedicated software.

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-fee pricing ($98/month for up to 10 employees, $198/month for up to 50), so that owners and operators can focus on the higher-impact work of giving good feedback.

For the practice that sits underneath good feedback, the onboarding best practices guide covers the foundation that makes employees ready to receive feedback in the first place.

For the broader management foundation that frameworks like SBI sit on top of, the people management guide covers running a small team without enterprise overhead.

Frequently Asked Questions