How to Give Feedback That Actually Lands (The SBI Framework, Explained)

There was a period early in my management career where I gave feedback so carefully hedged that people walked away not knowing they'd received it. I'd spend the whole conversation circling the thing I actually wanted to say, and by the time I got close to it, I'd softened it so many qualifiers deep that the message disappeared. The person would say "thanks, that's helpful" and leave, and I'd sit there knowing I hadn't actually said the thing.

Then I overcorrected. Got frustrated once, said something too directly, without context or warmth, and watched someone shut down mid-conversation. That didn't work either.

Both failures had the same root cause: I was improvising in a moment that required structure. Feedback is a high-pressure exchange. When you don't have a reliable framework, you default to whatever feels safer in the moment, which is almost never the thing that's actually useful.

The SBI framework is what I landed on after enough attempts to know that structure isn't a crutch. It's the thing that makes the conversation worth having at all.

Why most feedback doesn't work

"You need to be more proactive." "Your communication could be better." "I feel like you're not as engaged lately."

None of those are feedback. They're evaluations without evidence. They tell someone they're falling short without saying how, or when, or what effect it's actually having. And when people receive evaluations without evidence, they push back on the evaluation, because there's nothing specific enough to agree or disagree with.

Vague feedback produces defensiveness not because the person is difficult, but because you haven't given them anything concrete to work with. They're arguing the only thing they can argue: the characterization.

Specific feedback doesn't give them that opening. Specific feedback says: here is exactly what happened, here is the behavior I observed, and here is what it meant for the team. That's the whole structure. That's SBI.

The SBI model: Situation, Behavior, Impact

SBI was developed by the Center for Creative Leadership as a structured feedback model. It works for both positive and constructive feedback, the structure is the same either way.

Situation: When and where did this happen? Be specific. Name the meeting, the date, the context.

Behavior: What did the person actually do or say? This is observable, factual behavior, not an interpretation or a character judgment. "You interrupted Marcus three times during the Q3 review" is behavior. "You were dismissive" is an interpretation.

Impact: What effect did that behavior have? On you, on the team, on a client, on a project? This is where you make the feedback matter. The impact is what answers the question "why does this thing you're telling me actually matter?"

That's it. Three parts. The goal is to deliver all three in sequence, clearly, without editorializing.

Positive feedback examples using SBI

Positive feedback matters at least as much as constructive feedback, and it's just as often done badly ("great job today!" tells someone nothing useful). Here's what it looks like with SBI:

Example 1: "In the client presentation on Tuesday [Situation], you walked through the pricing objection without getting flustered and pivoted to our case study naturally [Behavior]. The client's tone shifted noticeably after that, I think that moment is what got us to yes [Impact]."

Example 2: "During the team retrospective last week [Situation], you raised the QA process issue even though it was uncomfortable to bring up in front of leadership [Behavior]. That kind of directness is what I need more of, it gave us a real conversation instead of a surface-level check-in [Impact]."

Notice what these do: they're specific enough that the person knows exactly what you're recognizing. They can repeat the behavior because they know what it was. "Great job" doesn't give anyone anything to replicate.

Constructive feedback examples using SBI

This is where the structure earns its keep. Constructive feedback without SBI drifts into judgment. With SBI, it stays grounded in observation.

Example 1: "In yesterday's project standup [Situation], when Marcus raised the timeline concern, you cut him off twice before he finished his point [Behavior]. I could see him shut down after the second time, and he didn't contribute again for the rest of the meeting [Impact]. I need you to let people finish before responding, especially in group settings."

Example 2: "On the Henderson account report that went out Friday [Situation], the executive summary was missing the financial variance analysis that the client specifically requested last quarter [Behavior]. I got an email from their CFO on Monday flagging it, which puts us in a position where we're explaining instead of leading [Impact]. Let's talk about the checklist process before reports go out."

Both of these are hard things to hear. But they're hard in the right way, they're specific, they're tied to real events, and they explain the consequence. The person receiving this feedback can either agree or disagree with the facts, which is a real conversation. "Your communication needs to be better" gives them nothing to engage with.

What to do when they get defensive

Even well-delivered feedback gets a defensive response sometimes. That's normal, receiving feedback is uncomfortable, and the first instinct for many people is to explain or push back.

When this happens:

Don't repeat yourself louder. If they push back, don't restate the feedback with more emphasis. That becomes a debate.

Acknowledge the emotion. "I can hear this is frustrating" is not a concession, it's a way to stay in the conversation instead of escalating it. You can acknowledge someone's reaction without abandoning your observation.

Stay on behavior, not character. If they say "I'm not dismissive," you agree: "I'm not saying you're dismissive as a person. I'm saying in that specific moment, the effect was that Marcus shut down." Keep it tied to the observable facts.

Give them time to sit with it. Some feedback doesn't land in the room. It lands two days later when they replay the conversation. That's fine. End the discussion, give them space, and check back in.

How often should you be giving feedback?

More often than you are right now.

The research on this is consistent: managers people rate highest for development give feedback frequently and specifically, not just in formal reviews. A study by Gallup found that employees who receive regular, meaningful feedback are nearly four times more likely to be engaged than those who receive feedback rarely. Feedback that comes only in quarterly reviews is feedback that comes too late to change anything.

The goal is to make feedback so regular that it stops feeling like an event. When someone only hears from you twice a year about how they're doing, every piece of feedback carries enormous weight, which means every piece of feedback feels high-stakes. Weekly, specific, low-intensity feedback normalizes the conversation and makes the harder conversations less charged when they need to happen.

Build a habit of one piece of feedback, positive or constructive, in every 1:1. It doesn't need to be long. The SBI format takes 45 seconds when you know what you're going to say.

One thing I've noticed: the more you use SBI, the less you need to consciously run through the steps. You start hearing your own feedback differently in the moment. "That was great" starts to feel incomplete before you've even said it. You catch yourself reaching for the specific situation, the specific behavior. The structure becomes instinct.

That's when feedback stops feeling like a task on your list and starts feeling like part of how you actually manage.

The New Manager Starter Pack at cadencehq.co/starter-pack includes a Feedback Framework with SBI templates and ready-to-use examples for common feedback situations: positive, constructive, and everything in between.

Ready to build a consistent feedback habit? Try Cadence free at app.cadencehq.co: structured 1:1s, feedback tracking, and the weekly rhythm to make it stick.

Build a feedback habit your team can count on.

The New Manager Starter Pack includes a Feedback Framework, 1:1 template, and 30/60/90 Day Plan. $37: everything you need in one place.