TL;DR: Most managers know feedback matters, yet many avoid it or deliver it badly. The Situation-Behavior-Impact (SBI) model, developed by the Center for Creative Leadership, gives you a simple three-part structure: describe when and where something happened, name the specific behavior you saw, and explain its impact. Add a question about intent and it becomes a two-way conversation. Below you’ll find how SBI works, ready-to-use examples, phrases to avoid, and how often to give feedback.
Why feedback is worth getting right
Feedback is one of the most powerful tools a manager has, and one of the most neglected. Gallup has found that 80% of employees who say they received meaningful feedback in the past week are fully engaged. In another study of nearly 15,000 employees, Gallup reported that only 16% said their last conversation with their manager was extremely meaningful.
That gap is the opportunity. The problem usually isn’t that managers don’t care. It’s that feedback feels awkward, so it gets vague (“great job!”), personal (“you’re careless”) or delayed until the annual review, when it’s too late to be useful.
What is the SBI feedback model?
SBI stands for Situation, Behavior, Impact. The Center for Creative Leadership (CCL), which created it, describes three steps: clarify the situation, describe the specific behaviors observed, and explain the impact that behavior had on you. CCL says its research shows the method reduces anxiety for the person giving feedback and defensiveness in the person receiving it.
| Step | What you say | Example |
|---|---|---|
| Situation | When and where it happened, as specifically as possible | “In Tuesday’s client call about the Q4 campaign…” |
| Behavior | What the person actually did or said, the facts a camera would capture | “…you walked through the budget slide and answered each of their cost questions with numbers…” |
| Impact | The effect on you, the team, the customer or the result | “…and afterward the client told me they felt confident signing off. It saved us a week.” |
The key is the middle step. Behavior is observable. “You were rude” is a judgment; “you interrupted Sara twice while she was presenting” is a behavior. People can argue with a judgment, but it’s much harder to argue with a specific description.
Add intent: SBII
CCL recommends extending the model with a fourth step: inquire about intent. After explaining the impact, ask something like, “What was your thinking there?” This turns one-way feedback into a conversation and protects you from acting on wrong assumptions. Often, the gap between what someone meant and how it landed is exactly what needs to be discussed.
SBI examples you can adapt
Positive feedback
“During yesterday’s sprint planning (situation), you flagged that the API migration would block the mobile team and suggested splitting it into two tickets (behavior). That kept both teams moving this week and avoided a delay we would have caught too late (impact). Thank you.”
Positive feedback deserves the same specificity as corrective feedback. “Nice work” is pleasant; telling someone exactly what to repeat is useful.
Corrective feedback
“In this morning’s stand-up (situation), when Ahmed mentioned the test failures, you said ‘that’s not my problem’ and moved on (behavior). I noticed Ahmed went quiet for the rest of the meeting, and the issue still isn’t assigned (impact). Can you walk me through what was going on for you at that point? (intent)”
Feedback to your own manager
“In last week’s all-hands (situation), when you shared the reorg timeline before telling our team privately (behavior), several people came to me worried about their roles, and I didn’t have answers (impact). Next time, could we get a heads-up first?”
Phrases to swap out
- Instead of “You always…” or “You never…”, refer to one specific instance.
- Instead of “You’re not a team player,” describe the behavior: “You declined the last three review requests.”
- Instead of “Everyone thinks…”, speak for yourself and the impact you observed.
- Instead of the “feedback sandwich” (praise, criticism, praise), keep positive and corrective feedback separate so neither gets diluted.
- Instead of “Does that make sense?”, ask an open question: “How do you see it?”
How often should you give feedback?
More often than you think. In its guidance on effective feedback, Gallup argues that for most jobs feedback should happen a few times per week, because it “has an expiration date” and people remember recent experiences best. Gallup also found that frequent 15- to 30-minute conversations can have a greater impact than longer ones held less often.
A practical rhythm looks like this:
- In the moment: quick SBI feedback within a day of the behavior, positive or corrective.
- Weekly: a short one-on-one where feedback flows both ways.
- Quarterly: a step-back conversation about growth, goals and patterns.
- Annual review: a summary with no surprises, because everything was already discussed.
Tips for delivering it well
- Give corrective feedback privately. Praise in public can work, depending on the person, but criticism almost never should.
- Check your timing. Not in the middle of a crisis or right before someone presents.
- Prepare your SBI in writing. Thirty seconds of notes keeps you on facts rather than feelings.
- Listen after you speak. The intent question only works if you’re open to the answer.
- Agree on a next step. End with what will happen differently, and follow up.
- Ask for feedback yourself. Managers who model receiving feedback make it safer for their team to hear it.
The bottom line
Good feedback is specific, timely and about behavior, not personality. The SBI model gives you a repeatable way to do that in under a minute: name the situation, describe the behavior, explain the impact, then ask about intent. Practice it on positive feedback first, since it’s easier, and you’ll find the corrective conversations get less awkward too. For more on the model, CCL’s article on using SBI in talent conversations is a useful next read.
The Teck Hustlers Editorial Team covers technology, business, finance and gaming news for readers who want the story behind the headline. Every article is researched, written and edited by our in-house team, checked against company announcements, filings and reputable reporting, and updated when new facts emerge. We focus on what each development means for founders, professionals, investors and everyday users. Have a tip or a correction? Reach us through our contact page.
