The SBI feedback model: make specific feedback a weekly habit with one Snippet

“Great job on the call today.”

It’s kind, it’s quick, and it tells the person almost nothing.

Most managers have heard of the SBI feedback model, and many can name its three parts on demand. But feedback rarely happens in a training room. It happens in a Slack thread between meetings, in the two minutes before the next call, or in a Friday note written with one eye on the clock.

Under that pressure, Situation, Behavior, Impact shrinks to “nice work” or waits until the annual performance review. Each time that happens, the person misses what to repeat or, in some cases, what you want them to avoid in the future.

Make the specific version the fastest one to send, and you’ll send it more often. A Snippet that prompts for each part gets you most of the way there. Making it a weekly habit covers the rest.

What is the SBI feedback model and how is it helpful when giving feedback?

The SBI feedback model is a three-part structure for feedback from the Center for Creative Leadership (CCL). SBI stands for Situation, Behavior, Impact, and it’s used to describe when and where something happened, what the person said or did, and the effect it had.

• Situation: CCL’s guidance is to “include the time and place to reduce any confusion.” Name the meeting, call, or moment where the behavior occurred. In CCL’s words, “Avoid generalities, such as ‘last week,’ as that can lead to confusion.”
• Behavior: A good behavior description names the observable action and only what you saw or heard. “Keep to facts only and avoid inserting any opinions or judgments.” CCL’s example is “You interrupted me while I was telling the team about the monthly budget,” in place of “You were rude.”
• Impact: Describe “the results of the behavior in terms of the impact it had, whether the effect was positive or negative.” CCL’s impact example is “I felt frustrated when you interrupted me because it broke my train of thought.” Name who the behavior affected, like you, the customer, or the team’s ability to do its work.

CCL also teaches a fourth step, Intent, which turns SBI into SBII. Plain SBI tells the person what happened, and the intent step invites their side. 

You “inquire about the person’s original intentions” with a question like “What were you hoping to accomplish with that?” 

It helps most when the behavior surprised you, because the person can explain what they meant, and you find out where the real misunderstanding sits before you decide what happened.

How to use the SBI model to provide constructive feedback, step by step

Giving SBI feedback takes a few minutes of thought and about three sentences of writing. 

These five steps turn the model into a feedback conversation.

1. Pick one moment. Choose a specific situation, close enough to when it happened that the details are still fresh for both of you. Start with low-stakes feedback, like a specific thank-you, before you start using SBI for difficult feedback.
2. Write your SBI statement. Write one or two sentences for each of the three elements, including the situation, the observed behavior, and the impact. Keep the impact statement concrete, like a lost hour or a calmer customer. Then read it back and cut any interpretation dressed up as fact, like “careless” or “didn’t care.”
3. Deliver the feedback directly. However you deliver feedback, in a 1:1, a call, or a message, say the statement plainly. Skip the warm-up compliment, so the point doesn’t get lost.
4. Ask about intent and listen. CCL’s fourth step is a question like “What were you hoping to accomplish with that?” Then let the person receiving the feedback answer before you decide what happened.
5. Agree on a next step and follow up. Settle on what to keep doing or try next time, and check back the next time the same situation comes up.

SBI feedback examples (positive and corrective)

The first two SBI feedback model examples start from the vague version most of us would send, then rewrite it with SBI. Three shorter examples show positive and corrective feedback in other common situations.

SBI positive feedback example

Vague: “Great job with that customer.”

SBI: “On Tuesday’s escalation call with the billing customer, you summarized their three complaints back to them before offering a fix. They calmed down, agreed to your plan, and didn’t ask for a manager.”

Now the person has a pattern to reuse: summarize first, then solve.

SBI corrective feedback example

Vague: “You need to be more prepared.”

SBI: “In Thursday’s planning meeting, you presented the project plan without sending it to the team first. We spent the first 20 minutes reading it, so we ran out of time to decide on the budget.”

Add the intent question, and it becomes a conversation: “What were you hoping to get from the group on Thursday?” Then agree on a next step, like sending drafts the day before.

More SBI feedback examples

• Missed deadline (corrective): “Yesterday’s 5 p.m. deadline for the customer success report passed without an update from you. The team had to move our client call to Monday, and I had to explain the delay.”
• Team meeting (positive): “In this morning’s team meeting, you asked the newest person on the team for their view of the new feature’s rollout plan. They raised a testing gap the rest of us had missed, and we fixed the plan before launch.”
• Feedback to your manager (upward): “In Monday’s planning meeting, the priorities changed after we’d committed to the sprint. We lost two days of work, and the team wasn’t sure which list to follow. Could we review changes together before the sprint starts?”

Common mistakes that make SBI feedback slip

The model is easy. The habit is hard. Even managers who know and understand the value of SBI still fall back on vague feedback, and the reasons are predictable.

• The situation stays vague. A vague situation or time like “in that client meeting” or “lately” leaves the person guessing which moment you mean.
• The behavior becomes a label. “Great attitude” and “not a team player” describe a person. Behavior describes what they did.
• The impact goes missing or stays abstract. A missing or abstract impact leaves the person guessing why it mattered, so praise sounds like politeness and correction sounds like a preference.
• Nothing happens next. Feedback with no question and no next step comes across as a verdict rather than actionable feedback.
• It waits for the review. CCL’s guidance is that “giving feedback on a regular basis is more effective than saving it all for the performance review.”

Frequency matters as much as phrasing. Gallup reports that “80% of employees who say they have received meaningful feedback in the past week are fully engaged.” 

In the same article, Gallup notes that “among nearly 15,000 employees, only 16% said the last conversation with their manager was extremely meaningful.” 

The good news is that weekly conversations don’t have to be long. In Gallup’s words, “if these conversations happen every week, they can be brief.”

A short, specific note every week does more for people than a long, careful one every quarter.

How does SBI compare to other feedback frameworks?

SBI is one of several feedback frameworks managers learn for effective communication, and it’s the narrowest. It gives you the words for one specific moment.

• The feedback sandwich wraps corrective feedback between two compliments. SBI drops the padding and states the situation, behavior, and impact directly, so the point doesn’t get lost in the praise.
• Radical Candor, from Kim Scott’s book of the same name, is about the relationship between caring personally and challenging directly. SBI fits inside that approach as the way to word a specific piece of developmental feedback.
• STAR (Situation, Task, Action, Result) is often used to describe past work, like in interviews. SBI is built for feedback on a behavior you observed, and it ends with the impact on people within the organization.

The SBI-inspired feedback template (copy the Snippet free)

When the SBI feedback template lives in a TextExpander Snippet, it works anywhere you type. Whether you’re sending feedback by email, Slack, or a 1:1 doc, using a Snippet template ensures that it follows the SBI structure and adds two optional lines: an intent question and a next step. 

Use Fill-ins for every part that changes. A word in {braces} is a field you type into, options separated by a slash are a pop-up menu you pick from, and lines in [square brackets] are optional sections you include only when you need them.

{Quick note / Some feedback / A specific thank-you} on {Situation and date}:

When you {Observable behavior}, the impact was {Impact on me, the team, or the customer}.

[I’m curious what you were aiming for there. {Intent question}]

[Next time, {What to keep doing or try}.]

TextExpander allows my team to use standard templates, but still customize specific details without breaking our workflow.

William Brown, Lead Recruiter, Gusto

How to set up the Snippet

1. Create a new Snippet. Name it Specific feedback and give it the abbreviation ;sbi.
2. Add your feedback template. Copy the one from this post or write your own, and paste it into the content field.
3. Turn each field into a Fill-in. Make Situation and date a single-line Fill-in, and Observable behavior and Impact multi-line Fill-ins. Keep the labels as written, because they do the coaching.
4. Add the pop-up menu. Turn the opener into a pop-up menu with Quick note as the default.
5. Add the optional sections. Make the intent line and the next-step line optional sections, so you include them only when they fit.
6. Test it once. Type ;sbi in a blank message, fill in a made-up example, and read it back for any word that judges the person.

How to make SBI a regular part of the feedback conversation

SBI becomes a habit the same way any work habit does, with a cue that starts it, a structure that makes it easy, and enough repetition that it runs on its own.

• Cue: pick one trigger and write it as an if-then plan, like “When I close my laptop on Friday, I write one SBI note” or “When someone does something worth repeating, I type ;sbi in the thread.” In a meta-analysis of 94 independent tests, Gollwitzer and Sheeran found that if-then plans had a positive effect on goal attainment of “medium-to-large magnitude (d = .65).”
• Structure: the Snippet lays out all three parts with labeled fields, so you never start from a blank message.
• Repetition: every note counts. In a study of real-world habit formation, Lally and colleagues found a median of 66 days for a new daily behavior to become automatic, and missing one opportunity “did not materially affect the habit formation process.”

The field labels do more coaching than you’d expect. It’s hard to type “great attitude” into a field called Observable behavior without noticing it doesn’t fit.

The value of TextExpander is that I don’t have to open another document, I don’t have to search for the text I want, I don’t have to copy and then paste.

Scott Hollinger, EdD, university graduate professor

3 more ways to make the Snippet work for you

• Use it in every channel. The same ;sbi works in Slack, email, your HR system’s review form, and 1:1 notes, so your feedback has the same shape wherever you write it.
• Keep a private SBI log. A second Snippet, like ;sbilog, adds a dated one-liner with the person’s name, the situation, the behavior, and the impact. Paste it into each person’s 1:1 doc, and at review time you start with real examples instead of memory.
• Share it with your managers. A shared Snippet Group gives every people leader on your team the same structure, and an update to the wording reaches everyone the next time they use it. Keep names and performance details out of shared Snippets and type them into the Fill-ins instead. See how shared Snippets work in TextExpander for business.

My team saves so much time avoiding the need to repeatedly type out the same sentence or feedback phrases to freelancers. Also, we have a bank of phrases that we can all use, enhancing consistency and collaboration between us.

Verified G2 reviewer, computer software company

Where SBI isn’t enough

SBI is a structure for a message, and some situations need more than a message.

• Serious performance issues need a conversation and your organization’s HR process and escalation path, and so does repeated behavior that one note didn’t change. A written note can document what happened, but it shouldn’t replace the meeting.
• Mixed feedback needs two statements. SBI covers one behavior at a time. When the same moment had something to keep and something to change, give each its own situation, behavior, and impact, so the correction doesn’t get lost in the praise.
• Listening sits outside the three steps. CCL’s intent step adds it, so ask the question and wait for the answer.

One specific note, every week

Back to “Great job on the call today.” With ;sbi, the same 30 seconds produces this:

“Quick note on today’s onboarding call with the new client: When you walked them through the first week’s timeline before they could ask, the impact was a short Q&A and a client who left knowing what happens next. Next time, open with the timeline again.”

It’s still kind and still quick, and now the person knows what to repeat.

Try TextExpander free and add the feedback Snippet before your next 1:1. To keep building the habit, see how other customers turned their first Snippet into a daily habit.