How to Give Feedback That Doesn't Sound Like an Attack (SBI Model Explained)

Key Takeaways

Feedback is easier to hear when it describes a specific moment, an observable action, and its effect rather than making a judgment about someone’s character.

• Name the situation clearly so the other person knows which moment you mean.

• Describe what you saw or heard without guessing at intent.

• Explain the impact accurately, and leave room for context you may not know.

• Invite a response and agree on a practical next step together.

• Use one recent example at a time, then follow up respectfully.

Why feedback can feel like an attack

A conversation about one difficult moment can quickly feel like a verdict on someone’s whole character. That shift often happens when feedback is vague, personal, or delivered at a tense moment. A little structure helps keep the discussion focused on what happened and what could be different next time. For people navigating the professional landscape, USchool provides career planning eLearning resources on resumes, interviews, and career development.

How vague criticism puts people on the defensive

“Your communication needs work” gives someone little to act on. They may wonder which conversation you mean, what they did, or whether the criticism is about a recurring pattern you have not explained. Specificity narrows the discussion to something both people can examine, such as a missed update or an unanswered question.

Why judgments about character can overshadow specific actions

Calling someone careless or difficult turns a conversation about an action into an argument about identity. Even if the label reflects your frustration, it does not tell the person what to change. Describing the observable behavior instead—such as “the draft was sent without the figures we agreed to include”—leaves more room to understand what happened and decide what to do next.

How timing, tone, and power dynamics shape the conversation

Feedback delivered in front of colleagues, during a rush, or immediately after a heated exchange can feel more like a reprimand than an attempt to solve a problem. A private, calm setting usually gives both people more room to listen. Power differences matter, too: a manager’s words may carry consequences even when they are intended as a casual suggestion, so clarity and respect are especially important.

What makes feedback feel fair and useful

Fair feedback connects a specific event to an effect without claiming more than you know. It also makes space for the other person to explain details you may have missed. For a practical companion on this topic, see this guide to constructive feedback, which covers specific examples, “I” statements, and collaborative next steps. The goal is a shared understanding, not a courtroom-style case against someone.

What the SBI feedback model means

SBI is a simple structure for talking about a concrete event: Situation, Behavior, and Impact. The sequence helps keep feedback grounded in what happened, rather than in assumptions about why someone acted that way. It can be useful for both corrective feedback and recognition, as long as the description stays specific and honest.

Situation: identify when and where it happened

The situation gives the conversation a clear starting point. Name the meeting, task, or moment and, when helpful, the date or setting. “In Monday’s project check-in” is more useful than “the other day,” because it gives the other person a fair chance to recall the same event.

Behavior: describe what you observed without labeling intent

Behavior is what someone said or did that another person could have seen or heard. “You interrupted twice while Maya was explaining the timeline” describes an action; “you were trying to shut her down” guesses at a motive. The distinction matters: you can report your observation, but only the other person can tell you what they intended.

Impact: explain the effect on people, work, or outcomes

Impact explains why you are raising the issue. It might be that a teammate could not finish sharing a concern, a decision was delayed, or a client received an incomplete update. Keep the effect proportionate to what you know, and distinguish your experience from a fact about everyone else. The SBI method for feedback offers further guidance on using the framework to explore intent and impact without relying on assumptions.

How SBI differs from praise, advice, and performance reviews

SBI is a way to frame feedback about a particular moment; it is not a complete performance review or a substitute for advice. Advice suggests what someone might do next, while SBI first clarifies the event and its effect. The same habit of naming context before drawing a conclusion can help in many settings, from sales team motivation and cookie consent to basic plumbing repairs, business-model planning, and Baden-Powell’s leadership lessons. Those subjects differ, but clear descriptions still help people understand what is being discussed. Here is a quick comparison of what each part contributes:

SBI part	What to include	Example prompt
Situation	A specific time and setting	When did it happen?
Behavior	An observable action or words	What did you see or hear?
Impact	The effect you noticed	What changed as a result?

The three parts make feedback easier to follow, but they do not require a stiff script. You can use ordinary language and still give the other person enough detail to understand your point. For a deeper explanation of why the approach can protect working relationships, read about why SBI helps managers.

How to prepare feedback with the SBI model

A little preparation helps prevent a difficult conversation from turning into a list of old frustrations. Before you speak, write down the event, the behavior you observed, and the effect you noticed. USchool’s career planning eLearning resources address resumes, interviews, and navigating the professional landscape; clear communication is one part of that broader professional context.

Choose one specific, recent example

Pick one incident that is recent enough for both people to recall and relevant to the issue you want to discuss. If the concern is about meeting interruptions, use one meeting rather than saying “you always interrupt.” A single example makes the conversation easier to check and less likely to feel like a broad attack.

Separate observable facts from assumptions

Before the conversation, divide what you know from what you suspect. You may know that a message arrived after the agreed time; you may not know why it was late. This quick distinction can keep your wording fair:

• Record the time, setting, or task connected to the event.

• Write down the words or actions you directly observed.

• Note the impact you experienced or can verify.

• Mark any explanation of intent as a question, not a fact.

That short check is not about making feedback sound formal. It helps you avoid treating a guess as evidence, and it gives the other person a clear opening to add context.

Consider the other person’s perspective and context

Ask yourself what you might not know: Was a deadline changed? Did the person have conflicting instructions? Was there a technical problem? You do not need to dismiss the impact or excuse an action before you have the conversation. A genuine question can reveal context that changes the next step.

Decide what change or conversation would be helpful

Think about what you want to happen after the discussion. Perhaps you want an earlier status update, uninterrupted time for each speaker, or simply to understand why an event unfolded as it did. If you are working through feedback from an instructor, these tips for handling instructor feedback can help you listen, ask clarifying questions, and turn criticism into practical steps. The aim is a useful conversation, not a demand that the other person agree with every interpretation.

How to deliver feedback without sounding accusatory

The SBI structure is a guide, not a line to recite. Use a calm tone, speak plainly, and leave time for the other person to respond. Feedback is more likely to stay constructive when it describes a specific event and makes room for discussion rather than presenting a final judgment.

Open with a neutral description of the situation

Start with a short, identifiable reference: “In yesterday’s planning meeting, when we reviewed the launch schedule…” This tells the person what you want to discuss without leading with blame. If the topic is sensitive, ask whether it is a good time to talk privately before moving into the details.

Use precise, nonjudgmental language for the behavior

Describe the action rather than attaching a label. “You spoke while I was still outlining the proposal” is more precise than “you were disrespectful.” If you need to refer to exact words, quote only what you remember accurately. Helpful guidance on speaking up in meetings can also support clearer contributions and calmer responses to interruptions.

Explain the impact without exaggerating or assigning blame

Connect the behavior to an effect you can explain: “I lost my place and did not finish the budget question.” Avoid sweeping claims such as “everyone was uncomfortable” unless you know that is true. A useful impact statement may be personal and modest; it does not need to make the incident sound larger to matter.

Invite the other person to share their perspective

After you have explained your observation and its impact, pause. You might ask, “How did you see that moment?” or “Is there context I’m missing?” Listening does not mean withdrawing the feedback; it means checking whether your account is complete. If the exchange becomes tense, practical suggestions for handling a passive-aggressive coworker may help you keep the focus on work impact and respectful boundaries.

SBI feedback examples for common situations

Examples can help you find natural wording, but they should not become scripts delivered without thought. Adjust the details to match what actually happened, and say only what you can stand behind. The useful pattern is steady: identify the moment, describe the behavior, and explain its impact.

Addressing interruptions in a meeting

“In today’s planning meeting, you began speaking while I was still explaining the customer concern. I wasn’t able to finish the point, and the group moved on without discussing it. Could we make sure each person has a moment to finish before we respond?” This names an event and a concrete effect, then offers a workable request rather than a judgment about the speaker’s personality.

Discussing a missed deadline with a teammate

“On the design handoff due Tuesday, I received the files Wednesday morning. I had to move the review to the afternoon, which left less time for revisions. Can we agree on a quick update if a deadline looks at risk?” The example explains the impact without assuming the teammate did not care or was avoiding the task.

Giving feedback about written communication

“In the project update you sent this morning, the revised date was included near the end of the message. I missed it on my first read and shared the earlier date with the team. Could you put schedule changes near the top next time?” The wording points to a specific message and a specific consequence; it does not turn one confusing update into a claim that someone writes badly in general.

Recognizing a helpful contribution with positive SBI feedback

Positive feedback can use the same structure. “During yesterday’s handoff, you added a short list of open questions to the document. That helped me spot the unresolved items before the review, so I could prepare answers.” Specific recognition tells someone which action was helpful and why it mattered, making praise more useful than a general “great job.”

Common SBI mistakes and how to handle the response

SBI can make a conversation clearer, but it cannot guarantee agreement or prevent discomfort. People may remember an event differently, and an impact that feels obvious to one person may not be clear to another. Stay open to correcting your account while keeping the conversation respectful and focused.

Avoid combining multiple incidents into one critique

Bringing up several unrelated moments can make the person feel that the conversation is a verdict on their overall performance. Choose the most relevant example and discuss it first. If a broader pattern needs attention, describe it carefully and use specific examples one at a time rather than piling them together.

Don’t present assumptions about intent as facts

A delayed response does not, by itself, prove someone was ignoring you. A sharp comment does not tell you everything about why it was said. State what happened, explain the effect, and ask about intent if it matters. That keeps the discussion honest even when you are frustrated.

Adapt the conversation when the impact is unclear or disputed

If the other person questions the impact, do not insist that they experienced it the same way you did. Clarify what you personally noticed, ask what they saw, and check whether there is a practical consequence you can both identify. If you discover that your first interpretation was incomplete, say so and adjust it. The point is to understand the event, not to win an argument about whose memory is perfect.

Agree on a next step and follow up respectfully

Close by identifying one useful action, then check back at an appropriate time. A next step might be a clearer handoff, a brief status update, or a pause before responding in meetings. Where a concern is about routine work, keep the follow-up direct and private; written complaints can sometimes create an unhelpful record, so learn about safer ways to address coworker concerns when you need to choose how to raise an issue. For further practice, you can explore career learning as part of developing professional skills. A follow-up should check whether the agreed change helped, not reopen the conversation as a fresh accusation.

Conclusion

To give feedback that doesnt sound like attack SBI model, keep your words close to the event: name the situation, describe observable behavior, explain the impact, and invite the other person’s perspective. The structure cannot make every conversation easy, but it can make your point clearer and fairer—and help both people leave with a more useful next step.

Frequently Asked Questions

What does SBI stand for in feedback?

SBI stands for Situation, Behavior, and Impact. It is a way to describe when something happened, what someone did, and the effect you noticed.

How do I give feedback without sounding accusatory?

Describe a specific action rather than labeling the person, explain its effect without exaggerating, and ask for their perspective. A calm, private conversation can also help reduce the sense of being put on the spot.

Should I use SBI for positive feedback?

Yes. You can describe a moment when someone took a helpful action and explain the effect it had. Specific recognition makes it clearer what you appreciated.

What if the other person disagrees with my feedback?

Listen to their account and separate what you directly observed from your interpretation. You can acknowledge a different perspective while still explaining the impact you experienced.

How specific should an SBI example be?

Specific enough that both people can identify the moment and the action being discussed. A recent meeting, message, or handoff is usually clearer than a general claim about someone’s habits.

Should I give feedback in private?

For sensitive or corrective feedback, a private conversation is usually more respectful and gives the other person room to respond. Public recognition may be welcome, but consider the person’s preferences and the setting.

What should I do after giving SBI feedback?

Agree on a practical next step if one is needed, then follow up respectfully. Check whether the change helped rather than treating the follow-up as another opportunity to repeat the criticism.