You've been putting off this conversation for two weeks. Every 1:1 passes and you find something else to talk about, project updates, team morale, anything but the actual issue.

The SBI feedback model exists precisely for moments like this. It's a framework that gives you the words when you're standing there with sweaty palms, trying to say something real without blowing up the relationship. But it works for a reason most managers never get taught: it's designed around how the human brain reacts to feedback, not around what managers wish people would do.

SBI stands for Situation, Behaviour, Impact. It's short, it's specific, and it works.

If you're looking for the full library of SBI scripts for different scenarios, that's covered in our main SBI feedback model guide. This post is about the why: why SBI lands when other frameworks don't, and what's happening in the room when a manager finally says the thing.

‍

Why Most Managers Avoid Feedback

The uncomfortable truth: most managers aren't bad at feedback because they don't care. They're bad at it because nobody ever taught them how to do it. They got promoted because they were great individual contributors, not because they had coaching skills. And then they're suddenly responsible for other people's growth with zero training on how to actually have a hard conversation.

This is the manager gap in action. The CMI and YouGov 2023 study of UK managers found that 82% of managers are "accidental managers" promoted into the role without formal training. The data is UK-specific, but the dynamic shows up everywhere. The best engineer becomes a manager and gets buried under the assumption that technical excellence translates to leadership skill. It doesn't.

The result? Feedback that never gets delivered, or feedback that lands like a grenade, vague, personal, and guaranteed to trigger defensiveness. Neither one helps your team grow.

‍

What the SBI Feedback Model Actually Is

The SBI model was developed by the Center for Creative Leadership, one of the most respected leadership research organizations in the world. The idea is simple: break your feedback into three specific parts.

Situation. When and where did this happen? Give the exact context. "Last Tuesday in our sprint planning meeting" is a situation. "Sometimes in meetings" is not.

Behaviour. What did you actually observe? This is about what you saw or heard, not what you think it means. "You talked over Sarah three times" is a behaviour. "You're dismissive of others" is an interpretation.

Impact. What effect did that behaviour have? On you, on the team, on the project. "It shut down the conversation and no one else contributed for the rest of the session" is an impact. Keep it factual, not punishing.

That's the whole model. Three parts. One framework. Zero guesswork.

‍

Why SBI Works (The Psychology Behind It)

Most feedback fails before it even starts. The moment someone hears "I need to give you some feedback," their nervous system lights up. The brain reads social threat the same way it reads physical threat. You get a stress response, heart rate up, defensiveness on, listening off. The conversation is over before it begins.

Generic feedback makes this worse. When you say "you need to be more professional," you're attacking identity. The person can't separate themselves from the criticism. Their brain says: this person thinks I'm unprofessional as a person. The walls go up.

SBI works because it bypasses that response. Behaviour is observable. It's something you did in a specific moment, not who you are. When feedback is grounded in a concrete situation and a specific behaviour, the brain has somewhere to land. It can actually process the information instead of just defending against it.

Amy Edmondson's research on psychological safety backs this up: teams that feel safe to take interpersonal risks handle feedback significantly better than teams operating in fear. When people trust that feedback isn't a personal attack, they can actually hear it. If you want to build that kind of team culture, these psychological safety exercises are worth exploring alongside SBI.

Now imagine using that same structure with your team. The specificity is what makes it stick, and what makes it land without starting a war.

Gallup research shows that managers account for at least 70% of the variance in employee engagement. Seventy percent. Your ability to give feedback well isn't a soft skill. It's the most direct lever you have on your team's performance. For more on how managers can sharpen this, see these manager feedback examples and when to use them.

‍

How to Use the SBI Model: Step-by-Step

This isn't theoretical. The practical method, step by step.

Pick one recent, specific moment. Not a pattern. Not "over the last few months." Last Thursday. In the design review. During the client call. The more specific, the better. If you can't name a situation, you're not ready to give feedback yet, you're just venting.

Describe what you saw or heard. Not what you assumed, not what you think it means. Stick to the facts. "You sent the report 20 minutes before the client meeting" is observable. "You were careless with the deadline" is a judgment. One invites a conversation. The other invites a fight.

Tell them what it caused. Keep it grounded in the real effect, on the team, on the client, on the outcome. "The client had to make decisions without seeing the full data" is an impact. "It was really frustrating for me" can be true and useful, but it needs to be paired with a business or team-level impact to land with weight.

What a positive SBI example sounds like:

"In this morning's all-hands (Situation), when you walked the team through the Q4 numbers without defensiveness even after Marco pushed back hard (Behaviour), it set the tone for the rest of the meeting. People felt safe to ask real questions, and we got to the actual concerns instead of dancing around them (Impact)."

What a corrective SBI example sounds like:

"In yesterday's client call (Situation), when the client asked about the rollout timeline and you said 'we'll figure it out' instead of walking through what we've already planned (Behaviour), they followed up with me afterward asking if we have a real plan. It affected their confidence in the project (Impact)."

Compare the difference:

Your one-on-one meetings are the natural home for this. Private, regular, low-stakes enough to have a real conversation. Use SBI there first. Build the muscle before you need it in a high-stakes moment.

If you want to build these habits into a full manager development practice, the New Manager Training Program covers this and the skills that come after.

‍

Common SBI Mistakes (and How to Fix Them)

‍

Conclusion

Feedback isn't about being right. It's about giving your team the information they need to actually grow. The SBI feedback model doesn't make hard conversations easy, but it makes them possible. And possible beats avoided every single time.

Start with one conversation this week. Pick a situation. Name the behaviour. Describe the impact. Then see what happens when someone actually hears what you're saying.

Want to go deeper on the skills that separate good managers from great ones? Download the free New Manager Playbook.

 Frequently Asked Questions

‍