How to Give Feedback That Actually Changes Behavior

Feedback that changes behavior is specific, tied to observable actions, and connected to a real consequence. The SBI model (Situation, Behavior, Impact) gives you a repeatable structure to deliver it. Master those three components and you eliminate the ambiguity that lets most feedback slide off without effect.

Why feedback usually fails

Most feedback conversations go wrong before the first sentence is finished. The manager says something like "You need to be more proactive" or "Your communication could be better." The employee nods, says thanks, and nothing changes.

That is not because they are resistant. It is because the feedback gave them nothing to act on. "Be more proactive" could mean 50 different things to 50 different people. Without a specific situation, a specific behavior, and a specific consequence, the employee has no way to know what they did, why it mattered, or what to do differently next time.

A second failure mode is feedback delivered as a verdict. "The problem is that you don't prioritize well." That framing puts the person on trial, and the conversation shifts from problem-solving to self-defense. The feedback lands as an attack, not as useful information.

There is also the timing problem. Many managers save feedback for annual reviews or quarterly check-ins, which means they are delivering a summary judgment on months of behavior instead of addressing a specific incident while it is still fresh. Feedback that references what happened eight weeks ago is hard to act on and easy to dispute.

The SBI model

SBI stands for Situation, Behavior, Impact. It was developed at the Center for Creative Leadership and has been used in management development programs for roughly three decades. The model works not because it is clever but because it forces precision. Each element removes a different way the conversation can go wrong.

Situation: anchor the feedback in time and place

The Situation is a specific, observable moment: "Last Tuesday during the client call" or "In the proposal you sent on September 10." The more specific it is, the harder it is to argue with.

Avoid situation descriptions that are really summaries. "Over the past few months" or "In general, when you talk to clients" both invite debate about whether the pattern even exists. A single, concrete instance does not.

Behavior: describe what you saw, not what you concluded

The Behavior is what the person actually said or did, not your interpretation of it. "You interrupted the client three times before she finished explaining the problem" is a behavior. "You were dismissive" is a conclusion.

This distinction is the most important one in the entire model. Conclusions invite defensiveness because they are debatable. "I wasn't being dismissive, I was just trying to move things forward." Behaviors are harder to deny. The employee can argue about whether they were dismissive, but they cannot easily argue about whether they interrupted someone three times.

If you find yourself using adjectives to describe the behavior, that is a sign you have slipped from observation into judgment. Stick to verbs and direct quotes where possible.

Impact: connect the behavior to a real consequence

The Impact is what happened as a result: to a client, a deal, a teammate, a metric. This is the component most managers skip, and it is the most important one.

Impact does two things. First, it answers the implicit question every employee has after hearing critical feedback: "Why does this matter?" Second, it makes the feedback feel fair rather than arbitrary. When someone understands the consequence of a behavior, they have a reason to change it. Without impact, feedback is just a preference.

Keep the impact tied to the work. The closer it is to a measurable outcome, the more seriously it will be taken.

Before and after: A real dialogue

Here is a concrete scenario. An account manager at a 12-person B2B SaaS company has $340,000 in open deals that have gone more than 18 days without documented follow-up activity in CRM. The company's average sales cycle is 42 days. The sales manager needs to address it.

The typical (ineffective) version

Manager: "I've been looking at your pipeline and I think you need to be more disciplined about your follow-ups. Deals are just sitting there."

Employee: "I've been following up. I just haven't logged everything. And some of those deals are in the client's court anyway."

Manager: "Okay, just make sure you're staying on top of it."

Nothing changes. The employee does not know which deals, which behaviors, or what "staying on top of it" means. The manager has not moved anything.

The SBI version

Manager: "I want to talk about something specific I saw in Salesforce this morning. You have 11 open deals totaling $340,000 that haven't had a logged touch point in over 18 days. [Situation] In five of those, the last activity was an outbound email that got no response, and there's been no follow-up attempt since. [Behavior] At our average 42-day cycle, deals that go two-plus weeks without contact close at a significantly lower rate. Based on our historical win data, we're likely leaving $50,000 to $80,000 on the table from pipeline we've already done the hard work to generate. [Impact] I want to work through this with you."

Employee: "I didn't realize so many had slipped. Some of those I'm genuinely waiting on the client."

Manager: "Fair. For the ones waiting on the client: what's your next planned touch if you don't hear back by Friday?"

Employee: "I don't have one scheduled."

Manager: "That's the gap. Let's set a default: if a deal goes 10 days without inbound activity, you send a short check-in. Can you set that up for those five deals before end of day today?"

Employee: "Yeah, I can do that."

The second version gives the employee something specific to act on, connects the behavior to a business consequence, and ends with a concrete commitment. The employee is not defensive because they were never accused of a character flaw.

How to give feedback that changes behavior

Step 1: Prepare your three elements before the conversation

Do not walk into a feedback conversation with a general concern. Write down the specific situation, the observable behavior, and the measurable or observable impact before you sit down. This takes about five minutes and prevents you from fumbling mid-conversation or sliding into generalizations when the employee pushes back.

Step 2: Replace interpretive language with observable language

Review your phrasing carefully. Replace any interpretive words like "disrespectful," "lazy," or "not committed" with observable ones: "missed the deadline," "did not respond to the message," "left the meeting before the action items were recorded."

If you cannot find the observable version, you are probably not ready to give the feedback yet. The inability to name what happened specifically is almost always a sign you are reacting to a feeling rather than an event.

Step 3: Deliver all three elements before asking for a response

State the situation, the behavior, and the impact fully before inviting the employee to respond. If you stop after the behavior, you give them the opening to explain it away before they understand why it matters.

Step 4: Ask a question, not for an apology

After the SBI statement, open with a genuine question: "What was going on on your end?" or "How did you see that situation?" You are not looking for an apology. You are opening a conversation about what actually happened and what needs to change. Often the employee has context you do not have, and the conversation becomes more useful as a result.

Step 5: End with a specific next action

Every feedback conversation needs to close with something concrete. "What will you do differently next time?" or "What specific step can you take this week?" are both good closers. If the same issue keeps surfacing across multiple team members, a clear RACI matrix can prevent role confusion from recreating the problem.

The most common mistake: turning impact into a feeling

The single most common error managers make with SBI is turning the Impact into an emotional complaint. "When you do that, it makes me feel like you're not committed" or "It really affects my ability to trust you."

Those statements are not impact statements. They are pressure tactics. They put the employee in the position of managing your feelings rather than solving a business problem.

Real impact is external. It references what happened to a client, a metric, a deadline, a teammate's workload, or a project outcome. The closer you can get to something measurable, the more the feedback feels like a professional conversation and the less it feels like a personal attack.

If feedback consistently triggers defensiveness in your team, this is almost always the root cause. Swap "it makes me feel" for "what happened was" and watch the conversation change.

Template: SBI feedback structure

Use this table as a prep sheet before any feedback conversation. Fill in each row. If you cannot complete the Behavior row with something you directly observed, you are not ready to have the conversation yet.

When feedback is tied to broader team performance goals, it lands better if your team already has shared context on priorities. A quarterly planning process creates that context and makes individual feedback easier to connect to team-level outcomes.

For managers who want to turn feedback into a broader execution habit, the same principle applies when you build an execution plan your team will actually follow: observable behaviors tied to measurable outcomes, with clear ownership and follow-up.

If feedback conversations surface disagreement about direction or priorities, a structured strategy discussion with your team can surface the underlying misalignment before it shows up again in the next review cycle.

Key takeaways

• Feedback changes behavior when it names a specific situation, an observable behavior, and a real consequence. Vague feedback produces vague results.
• The SBI model forces you to separate what you observed from what you concluded. That separation is the single biggest factor in whether the other person hears the feedback or defends against it.
• Impact statements should reference business outcomes, not personal feelings. Connect the behavior to revenue, client experience, team throughput, or cycle time.
• Deliver all three elements before asking for a response. Stopping after the behavior gives the employee an opening to explain it away before they understand why it matters.
• Every feedback conversation should end with a specific next action owned by the employee, not a vague directive to do better.
• Preparation matters more than delivery. If you cannot write down the specific situation, behavior, and impact before the conversation, you are not ready to have it.