In Short
This article covers the S.B.I. Method, a three-part feedback framework that helps you give clear, behavior-focused feedback without triggering defensiveness or confusion.
- How to structure feedback using Situation, Behavior, and Impact
- Ready-to-use scripts for corrective, positive, and upward feedback
- How to pair S.B.I. with the G.R.O.W. Method when receiving feedback in return
The S.B.I. method is a structured feedback approach built on three components: Situation, Behavior, and Impact. It gives feedback a clear, observable foundation by separating what happened from personal interpretation, making it easier to deliver and easier to receive.
Most feedback conversations go wrong before the first sentence is finished. A manager sits down with every intention of helping, and within thirty seconds the other person has shut down, gone defensive, or started planning their counter-argument. Not because the feedback was wrong. Because it had no structure.
I have sat on both sides of that table more times than I care to count. In Say It Right Every Time, I describe feedback as a tool that can build or destroy. Given poorly, it is a weapon that can crush confidence and kill motivation. Given well, it is the most powerful instrument we have for genuine growth. The difference is almost never content. It is almost always structure.
The S.B.I. method, which I cover in depth in Chapter 8 of Say It Right Every Time, gives your feedback that structure. It tells you exactly what to say, in what order, and why each part matters. In this article, you will learn the full S.B.I. framework and the supporting methods that make it work: when to use each one, what scripts to reach for, and how to avoid the mistakes that make even well-intentioned feedback fall flat.
If you are also working on how feedback affects team cohesion, How Feedback Loops Boost Team Synergy is worth reading alongside this one.
Why Structure Matters More Than You Think in Feedback Conversations
Most people assume feedback is about natural ability. They think some people are just better at it, born with the right tone and instincts. That is not true. Feedback is a skill, and like every skill, it depends on having a reliable system when the pressure is on.
Under pressure, people default to their worst habits. They go vague to avoid conflict. They over-explain to soften the blow. They turn observations into verdicts. Structure prevents all of that.
Here is when having a feedback framework makes the real difference:
- When you need to address a recurring problem without it turning personal, a clear framework keeps you focused on behavior rather than character.
- When you are giving positive feedback and want it to land as more than a passing compliment, structure makes it specific and memorable.
- When you need to give upward feedback to a manager, a framework gives you the confidence to say it calmly and clearly without it feeling like an attack.
- When you are in a performance review and want the conversation to be a genuine dialogue, not a one-way verdict, a structured approach keeps both people engaged.
- When someone has just received corrective feedback and is visibly defensive, knowing your next move in the framework stops the conversation from collapsing.
The frameworks in this article give you that structure. Use them until they become instinct.
"The Conversation You're Avoiding Is the One You Need to Have."
"The Conversation You're Avoiding
Is the One You Need to Have."
Stop rehearsing conversations you'll never have. Say It Right Every Time gives you 115 word-for-word scripts and 16 proven frameworks to speak with confidence in every conversation that matters.
The S.B.I. Method: Situation, Behavior, Impact
The S.B.I. Method is a three-part feedback structure that I introduce in Chapter 8 of Say It Right Every Time. It works by separating what happened from what you think about what happened. That distinction is everything.
What it is designed for: The S.B.I. method is built for any moment when you need to give feedback that is clear, specific, and free of personal judgment. It works for corrective feedback, positive recognition, peer-to-peer feedback, and upward feedback to a manager.
How it works:
Situation. Name the specific context where the behavior occurred. This anchors the conversation in something observable and shared, not a vague pattern. Example: "In the leadership presentation this morning..."
Behavior. Describe exactly what the person did or said, using observable language only. No interpretations, no character judgments, no assumptions about motive. Example: "...you did not leave any time for questions at the end..."
Impact. Explain the effect that behavior had, whether on you, the team, the project, or the client. This is what makes the feedback meaningful. Example: "...and the impact was that several of the VPs had questions that went unanswered, which made us look unprepared."
When to use it: Use S.B.I. any time you need to deliver feedback that is tied to a specific, recent event. It works best in one-on-one settings where you have the other person's full attention and enough time for a genuine response.
When not to use it: S.B.I. is not the right tool for a crisis in the moment, when emotions are running high on both sides and there is no time for a structured conversation. In those situations, address the immediate issue first and return to the full framework when things are calmer.
A quick example in practice: "I would like to talk about the presentation you gave to the leadership team this morning. I noticed that you did not leave any time for questions at the end. The impact was that several of the VPs had questions that went unanswered, and it made us look like we were not prepared for their feedback. In the future, I would like you to plan to end all presentations with at least ten minutes for Q&A. How can I help you with that?"
Eamon's take: I have watched S.B.I. transform conversations that would have ended in silence or resentment into moments of genuine clarity. It works because it gives the other person something real to respond to, not just a feeling to defend against.
Applying S.B.I. to Positive and Upward Feedback
The S.B.I. structure does not belong only to corrective conversations. It is just as powerful for recognition and for giving upward feedback to a manager, where the stakes and the nerves both run high.
What it is designed for: This application of S.B.I. covers situations where you need to reinforce a behavior you want repeated, or where you need to raise a concern with someone who has authority over you.
How it works:
Situation. Name the setting precisely. Positive feedback without a specific context sounds hollow. Example: "In our one-on-ones over the past month..."
Behavior. Name exactly what the person did. For positive feedback, this tells them what to keep doing. For upward feedback, it keeps the conversation factual. Example: "...I have noticed that you are also checking your email while we talk..."
Impact. Tell them what effect that behavior had on you or the work. For recognition, this is what makes the praise feel real. For upward feedback, this is where you make the case. Example: "...and the impact on me is that I sometimes feel I do not have your full attention during the time we have set aside."
When to use it: Use this when giving positive recognition after a specific achievement, or when raising a concern with a manager you respect and want to preserve a strong relationship with.
When not to use it: Do not attempt upward feedback in a public setting, in a group meeting, or when your manager is under visible pressure. Choose your moment carefully.
A quick example in practice: "I really value our working relationship, and I have a suggestion for how we could make it even better. I have noticed that sometimes in our one-on-ones, you are also checking your email. The impact on me is that I sometimes feel like I do not have your full attention, and I want to make the most of our time together. Would you be open to making our one-on-ones a no-device zone? I am happy to do the same."
Eamon's take: Upward feedback is one of the clearest signs of a high-trust relationship, and S.B.I. gives you the structure to do it without it feeling like an accusation.
The G.R.O.W. Method: Turning Feedback Into a Development Plan
If giving feedback well is a craft, receiving it is a superpower. The G.R.O.W. Method gives you a framework for turning feedback, whether you asked for it or not, into a personal development plan.
What it is designed for: G.R.O.W. is for the person on the receiving end. It helps you convert feedback into forward movement rather than letting it sit as a judgment with no clear next step.
How it works:
Goal. Identify the key improvement this feedback is pointing toward. Translate the feedback into a specific growth target. Example: "Based on this, my goal is to improve my project management skills."
Reality. Acknowledge honestly where things stand today, without defensiveness. Example: "The reality is that I have let a few deadlines slip this quarter."
Options. Brainstorm real choices for addressing the gap. More than one path is almost always available. Example: "I could take a project management course, find a mentor, or be more disciplined about using our tracking software."
Way Forward. Commit to a specific action and a timeline. This is the step that separates people who grow from people who nod and forget. Example: "My plan is to start the online course this week and schedule a weekly project review with you."
When to use it: Use G.R.O.W. during or directly after a performance review, a corrective conversation, or any feedback exchange where you want to show genuine intent to improve.
When not to use it: Do not force G.R.O.W. when you are still processing the emotional weight of difficult feedback. Give yourself time to absorb it first; then sit down and work through the four steps.
A quick example in practice: "Based on this feedback, it sounds like my main goal for the next year should be to improve my project management skills. The reality is that I have let a few deadlines slip. Some options for me could be to take a project management course, find a mentor who is strong in that area, or be more disciplined about using our project management software. My plan is to start the online course and schedule a weekly project review with you. Does that sound like a good plan?"
Eamon's take: I have seen careers change on the back of this method. Most people receive feedback and do nothing structured with it. G.R.O.W. gives you a system for doing something real.
Handling Defensiveness: The C.O.R.E. Framework
Here is the truth of it: even the best-delivered S.B.I. feedback can land wrong. Some people hear specific, observable, factual feedback and still feel attacked. This is where the C.O.R.E. framework becomes essential.
What it is designed for: C.O.R.E. is for de-escalation. It is the method to reach for when someone responds to feedback with defensiveness, hurt, or counter-attack, and you need to keep the conversation open without abandoning your message.
How it works:
Clarify. Name what you observed in the other person's reaction without judgment. Show that you have noticed how they are feeling. Example: "I can see this is uncomfortable to hear."
Own. Take responsibility for your part, if any. This does not mean apologizing for honest feedback; it means acknowledging that delivery is never perfect. Example: "I may not have expressed this as clearly as I wanted to."
Restate. Return to your original message using calm, clear language. Do not retreat from the substance, but do soften the frame. Example: "What I want you to take away is that the impact on the client relationship has been real, and I want us to address it together."
Explore. Invite their perspective with a genuine question. This shifts the dynamic from confrontation to collaboration. Example: "Can you help me understand how you experienced the situation?"
When to use it: Use C.O.R.E. any time you can feel a feedback conversation beginning to slide into defensiveness or conflict. The earlier you apply it, the easier the recovery.
When not to use it: C.O.R.E. is not a loop you stay in indefinitely. If a conversation has genuinely broken down, it is better to pause and reschedule than to keep pushing through.
A quick example in practice: "I can see this is difficult to hear, and I want to acknowledge that. I may not have framed it perfectly. What I want to be clear about is that the impact on the team has been significant, and I am raising this because I believe you can address it. Can you share how you experienced that situation from your side?"
Eamon's take: Defensiveness is not a character flaw in the person receiving feedback. It is the amygdala doing exactly what it was built to do. C.O.R.E. works because it disarms that response before it takes over the room. For a deeper look at how psychological safety shapes these moments, see What Is Psychological Safety and How It Drives Team Synergy.
Asking for Specific Feedback When What You Receive Is Vague
Vague feedback is useless feedback. I wrote that plainly in Chapter 8 of Say It Right Every Time, and I will say it here too. When someone tells you that you need to "be more strategic" or "communicate better," you are left with a label and no map.
What it is designed for: This framework is for turning unhelpfully broad feedback into something you can actually work with. It is a structured way to ask for clarity without sounding defensive or dismissive.
How it works:
Acknowledge. Thank the person sincerely before you ask for more. This keeps the exchange open and shows you are not dismissing what they said. Example: "Thank you for that feedback, I genuinely want to work on it."
Seek an example. Ask for a specific instance where the behavior was visible. This is not a challenge; it is a request for the information you need to improve. Example: "Could you give me a specific example of a time when I was not being strategic enough?"
Ask what different looks like. Ask what they would have liked to see instead. This turns the feedback into a forward-facing target rather than a backward-looking verdict. Example: "And what would you have liked me to do differently in that moment?"
When to use it: Use this in any feedback conversation, formal or informal, where the input you receive is too broad to act on. It is especially useful in performance reviews.
When not to use it: Do not use this framework in the first five seconds of receiving difficult feedback. Let the person finish. Absorb the tone and intent first; then ask for specifics.
A quick example in practice: "Thank you for that feedback. I really want to work on that. To help me, could you give me a specific example of a time when I was not being strategic enough, and what you would have liked to have seen me do differently?"
Eamon's take: Asking for specific feedback is not weakness. It is the most direct route from a label to a plan. If someone cannot give you an example, that tells you something important too.
How to Choose the Right Feedback Framework for Your Situation
Knowing the frameworks is only half the work. Knowing which one to reach for is the other half.
| Situation | Best Framework |
|---|---|
| Giving corrective feedback to a direct report | S.B.I. Method |
| Recognizing a team member's strong performance | S.B.I. Method (positive) |
| Raising a concern with your manager | S.B.I. Method (upward) |
| Processing feedback you have just received | G.R.O.W. Method |
| Managing a defensive reaction mid-conversation | C.O.R.E. Framework |
| Vague feedback you cannot act on | Ask for Specific Feedback |
| Performance review preparation and follow-up | G.R.O.W. Method |
In practice, you will often use more than one framework in the same conversation. S.B.I. delivers the message; C.O.R.E. steadies the room if the reaction is defensive; G.R.O.W. gives the recipient a path forward. They work together, not in competition.
When you are unsure which to reach for, default to S.B.I. It is the foundation. Every other framework in this article builds from it or responds to what happens after it.
When in doubt, start with the simplest framework. Complexity is not strength.
Common Mistakes When Using S.B.I. and Feedback Frameworks
Frameworks only work when you use them with discipline, not as a script you recite on autopilot.
Skipping the Impact step. Many people deliver the Situation and Behavior clearly, then stop short of explaining the actual impact. Without that final step, feedback is just an observation. The Impact is what makes the other person care. Always finish all three parts.
Letting interpretation creep into the Behavior step. The moment you say "you were rude" instead of "you interrupted me three times," you have crossed from behavior to judgment. The other person can argue with a judgment; they cannot argue with what actually happened. Stay observable.
Giving feedback that is too old. Feedback delivered weeks after the event loses its power. The person cannot recall the details clearly, and the connection between action and consequence is broken. Deliver feedback when the situation is still recent, as outlined in How to Give Feedback That Strengthens Team Synergy Instead of Breaking It.
Using S.B.I. as a confrontation, not a conversation. The framework ends with an invitation, not a verdict. After you state the Impact, ask how you can help or invite their perspective. Feedback that closes the door is not feedback; it is a reprimand. Learn how to keep that door open in How to Start a Difficult Conversation That's Blocking Your Team's Synergy.
Only giving feedback during formal reviews. Performance reviews should be summaries, not surprises. If someone is hearing corrective feedback for the first time during an annual review, you have waited too long. The S.B.I. method works best when it is used regularly, not reserved for high-stakes moments.
A framework used badly is still better than no framework. But a framework used well is a genuine advantage.
How to Start Using These Feedback Frameworks Today
Do not try to master all of these at once. Pick one, practice it in a real situation this week, and build from there.
Start with S.B.I. on a low-stakes conversation. Pick a piece of positive feedback you have been meaning to give someone. Structure it using Situation, Behavior, and Impact before you say it. Notice how much more specific and meaningful it feels compared to what you would have said without the framework.
Write out a corrective conversation before you have it. If you have a feedback conversation coming up, draft each of the three components on paper first. Writing it down forces clarity and helps you catch any interpretation or judgment that has crept into the Behavior step.
Practice G.R.O.W. after your next piece of feedback. The next time someone gives you feedback, take ten minutes afterward to work through Goal, Reality, Options, and Way Forward. See How Psychological Safety Enables Honest Communication and Sustains Team Synergy for how to create the right conditions for this kind of honest exchange.
Follow up. After giving corrective feedback, check in with the person a week or two later. Acknowledge the progress you have seen. This closes the loop and tells them that the conversation mattered. For guidance on repairing the relationship if a conversation went poorly, see How to Apologize to a Team Member in a Way That Actually Restores Synergy.
Frameworks are tools. The more you use them, the less you have to think about them.
Key Takeaways
Here is what to carry with you from this article.
- The S.B.I. method works because it separates what happened from what you think about it, and that separation is what makes feedback hearable.
- Vague feedback is useless feedback. Specificity is not harshness; it is respect.
- Feedback is a responsibility, not a right. If it is not helpful, it is just noise.
- G.R.O.W. turns feedback from a verdict into a plan; it is the method that separates people who improve from people who simply nod.
- Defensiveness is a natural reaction, not a character flaw. C.O.R.E. gives you a way through it without abandoning your message.
- Giving and receiving feedback regularly throughout the year means no one should ever be surprised in a formal review.
Good feedback builds people up and moves the work forward. It is not about being comfortable; it is about being effective. Start with S.B.I., practice it consistently, and apply the supporting frameworks when the situation calls for them. This much I know for certain: the people who take the time to learn how to give and receive the S.B.I. method well, earn the trust and respect of the people around them in ways that no amount of talent alone ever could.
Frequently Asked Questions (FAQ)
What is the S.B.I. method for giving feedback?
The S.B.I. method is a three-part feedback structure built on Situation, Behavior, and Impact. You describe when something happened, what the person specifically did, and the effect it had. This removes personal judgment from feedback and makes it easier for the other person to hear and act on.
How do you use the S.B.I. method in a real conversation?
Start by naming the specific situation, then describe the exact behavior you observed without interpreting it, then explain the impact that behavior had on you, the team, or the work. Finish by inviting a response. Keep each part brief and factual, and avoid adding emotional language that puts the other person on the defensive.
When should you use the S.B.I. method for feedback?
Use the S.B.I. method when you need to deliver feedback that is specific, observable, and tied to real impact. It works best for both corrective and positive feedback, especially in one-on-one settings. It is most effective when the situation is still recent enough for the other person to clearly recall it.
What are the three parts of the S.B.I. method?
The three parts are Situation, Behavior, and Impact. Situation sets the context by naming when and where something occurred. Behavior describes what the person did in observable terms. Impact explains the effect that behavior had, making the feedback relevant and meaningful to the person receiving it.
Can the S.B.I. method be used for positive feedback?
Yes, the S.B.I. method works equally well for recognizing good performance. When you anchor positive feedback in a specific situation, name the exact behavior you valued, and explain the impact it had, the praise becomes far more meaningful and memorable than a vague compliment. It also reinforces the behavior you want to see repeated.
What is the difference between the S.B.I. method and general feedback?
General feedback tends to be vague, personal, and hard to act on. The S.B.I. method forces you to be specific about when something happened, what was actually done, and what effect it caused. This removes guesswork for the person receiving the feedback and gives them something concrete to change or repeat.
