SBI Feedback Framework: Give & Receive Constructive

Overview

Imagine a scenario where a critical project deadline is missed, and you need to provide feedback to a team member. Your immediate impulse might be to express frustration, perhaps stating, 'You always miss deadlines, which makes the team look bad.' While this conveys your dissatisfaction, it's highly likely to trigger defensiveness, shut down dialogue, and fail to address the root cause of the issue. The feedback, though well-intentioned, focuses on character and generalization, making it impossible for the recipient to process constructively.

This is a common communication breakdown that costs companies millions in lost productivity and talent turnover. Professionals often struggle to deliver feedback that is both candid and constructive, leading to misunderstandings, resentment, and unresolved performance gaps. In high-stakes environments like tech and consulting, where collaboration and rapid iteration are crucial, effective feedback is not just a 'nice-to-have', it's a core competency.

This is where the SBI (Situation-Behavior-Impact) Feedback Framework, developed by the Center for Creative Leadership (CCL), becomes indispensable. SBI provides a structured, non-judgmental approach to delivering feedback by focusing on objective, observable facts. Instead of making subjective accusations, you describe a specific situation, the observable behavior that occurred, and the concrete impact of that behavior. This methodology shifts the conversation from personal blame to actionable observation, making it significantly easier for recipients to hear, understand, and act upon.

This module will equip you with the precise language patterns and strategic thinking to apply SBI effectively across various professional contexts. You'll learn how to craft feedback that reduces defensiveness, fosters growth, and strengthens professional relationships. We will explore the core components of SBI, its powerful SBII variation, practical applications from peer reviews to upward feedback, and how to receive SBI feedback constructively. By mastering SBI, you'll transform challenging conversations into opportunities for clarity, performance improvement, and career advancement.

Why It Matters

Key Concepts

Frameworks

Practical step-by-step methods you can apply immediately in meetings, interviews, and stakeholder conversations.

Framework 1

SBI (Situation-Behavior-Impact) Feedback Framework

The SBI framework is used to deliver objective, non-judgmental feedback that focuses on observable actions and their concrete consequences. Its purpose is to foster constructive dialogue, reduce defensiveness, and facilitate behavioral change by anchoring feedback in specific facts.

S

1. Situation: Set the Context

Start by describing the specific time and place the behavior occurred. Be precise about the context so the recipient can easily recall the event. This grounds the feedback in reality and avoids broad generalizations that can trigger defensiveness. Focus on recent events to ensure relevance and accurate recall.

“During our team’s weekly sync on Tuesday morning, around 10:15 AM, when we were discussing the Q3 roadmap…” or “In the client presentation last Thursday, specifically during the Q&A segment…”

B

2. Behavior: Describe the Observable Action

Clearly articulate what the person said or did. This must be an objective, verifiable action, not an interpretation, assumption, or judgment. Avoid words like 'you were' (followed by an adjective) and instead focus on 'you said' or 'you did.' Stick to the facts as you observed them.

“…you interrupted Sarah three times while she was explaining the technical dependencies…” or “…you submitted the project proposal with five grammatical errors in the executive summary…”

I

3. Impact: Explain the Consequence

Articulate the concrete effect of the behavior on you, the team, the project, or the organization. This step clarifies 'why' the feedback is important and helps the recipient understand the significance of their actions. Focus on measurable or tangible outcomes, not just feelings.

“…which meant she couldn't complete her explanation, and we left the meeting without a clear understanding of critical integration risks, potentially delaying our launch timeline.” or “…which created an unprofessional impression with the client and required me to spend an extra hour proofreading and re-sending it, delaying the official submission.”

(

4. (Optional) Intent: Seek Understanding (SBII Variation)

After delivering S-B-I, if appropriate, ask about the recipient's intention. This opens a dialogue, demonstrates empathy, and can uncover underlying reasons or misunderstandings. It shifts the conversation from a one-way judgment to a two-way coaching opportunity, fostering collaboration and trust.

“...What was your intention or what were you hoping to achieve by interrupting?” or “...Can you tell me more about your thought process when you submitted the proposal?”

In Practice

Read each scenario and pick the tab that matches how you would have responded, then check the annotation to see why it works, or where it falls short.

Scenario 1: Workplace Context - Missed Deadline Communication

You really dropped the ball on the Q4 report. Everyone's waiting, and now we're behind. You need to be more reliable.

"Dropped the ball" is vague and judgmental, not specific. "Everyone's waiting" creates pressure without defining impact. "You need to be more reliable" is a character judgment, not actionable behavior.

I noticed the Q4 report wasn't submitted by Friday. This caused a bit of a delay for the executive review. Please try to get it in on time next time.

"I noticed the Q4 report wasn't submitted by Friday" sets the situation and behavior but lacks specificity about *when* the deadline was or the actual observable behavior. "This caused a bit of a delay" is vague; the impact isn't quantified or clearly explained. "Please try to get it in on time next time" is a weak call to action, lacking specific guidance for improvement and not addressing the 'why'.

“During our project check-in on Monday morning (Situation), I saw that the Q4 financial projection report was not in the shared drive, which was due by Friday EOD (Behavior). This meant the executive leadership team couldn't review it as planned over the weekend, causing a 2-day delay in our budget finalization process and potentially impacting resource allocation decisions for Q1 (Impact). What happened that prevented you from submitting it on time?”

**Specific Situation:** 'During our project check-in on Monday morning... due by Friday EOD' provides precise context. **Observable Behavior:** 'I saw that the Q4 financial projection report was not in the shared drive' describes a factual, verifiable action (or lack thereof). **Concrete Impact:** '2-day delay in our budget finalization process and potentially impacting resource allocation decisions for Q1' clearly links the behavior to business consequences. **Open-ended Question (SBII):** 'What happened that prevented you from submitting it on time?' invites dialogue, demonstrates empathy, and seeks understanding of intent.

Scenario 2: Workplace Context - Poor Communication in a Meeting

You always dominate meetings. It's really annoying, and others can't get a word in.

"You always dominate" is a generalization and judgmental, likely to trigger defensiveness. "It's really annoying" expresses personal feeling without linking to professional impact. "Others can't get a word in" is a vague consequence, lacking specific examples.

In yesterday's planning meeting, you spoke a lot. I think it might have prevented others from contributing. Maybe try to speak less?

"You spoke a lot" is a soft description of behavior, not precise enough. "I think it might have prevented others from contributing" is hedged and speculative impact. "Maybe try to speak less?" is vague and lacks actionable steps for improvement.

“In yesterday's project planning meeting, specifically when we were brainstorming solutions for the database migration (Situation), I observed that you spoke for about 70% of the discussion time, and you interrupted both Maria and David twice each (Behavior). This meant that Maria couldn't fully explain her proposed alternative, and David's concern about data integrity wasn't fully explored, leading us to table a decision that could have been made then (Impact). What was your goal in contributing so actively in that segment?”

**Specific Situation:** 'In yesterday's project planning meeting... brainstorming solutions for the database migration' provides a clear, recallable context. **Quantifiable Behavior:** 'spoke for about 70% of the discussion time, and you interrupted both Maria and David twice each' provides objective, measurable actions. **Clear Impact:** 'Maria couldn't fully explain... David's concern... wasn't fully explored, leading us to table a decision' links directly to project outcomes and wasted time. **Seeking Intent:** 'What was your goal in contributing so actively...?' fosters understanding and constructive dialogue.

Scenario 3: Workplace Context - Code Quality Feedback

Your code is messy and hard to read. You need to improve your coding standards.

"Your code is messy and hard to read" is subjective and judgmental, not specific. "You need to improve your coding standards" is a vague directive without specific examples or guidance. Lacks any situation or specific impact, making it feel like a personal attack.

I saw some areas for improvement in the `UserAuth` module you submitted for review. Some functions were quite long, which made them a bit hard to follow. Maybe consider breaking them down.

"Some areas for improvement" is too soft and generalized. "Some functions were quite long, which made them a bit hard to follow" describes behavior and impact but lacks specificity (which functions? how long is too long?). "Maybe consider breaking them down" is a weak suggestion, not a clear recommendation based on best practices.

“In the pull request you submitted yesterday for the `UserAuth` module (Situation), I noticed that the `processLoginRequest` function was over 200 lines long and contained multiple responsibilities, including validation, database lookup, and session management (Behavior). This violates our team's single-responsibility principle, makes the code harder to test, and increases the risk of introducing bugs when changes are made, potentially slowing down future development (Impact). Could you walk me through your design choices for that function?”

**Specific Situation:** 'In the pull request you submitted yesterday for the `UserAuth` module' provides a precise reference point. **Observable Behavior:** 'the `processLoginRequest` function was over 200 lines long and contained multiple responsibilities' describes concrete, verifiable code characteristics. **Technical Impact:** 'violates our team's single-responsibility principle, makes the code harder to test, and increases the risk of introducing bugs... slowing down future development' clearly links behavior to technical debt and project risks. **Coaching Question:** 'Could you walk me through your design choices for that function?' invites discussion and understanding of the engineer's perspective.

Scenario 4: Workplace Context - Customer Escalation Handling

You handled that customer escalation terribly. They were furious, and it made us look bad.

"Handled... terribly" is a judgmental, subjective assessment. "They were furious" describes the customer's emotion, not the employee's behavior. "Made us look bad" is vague impact, lacking specific consequences.

I reviewed the transcript from the customer escalation call on Tuesday. It seemed like you interrupted the customer a few times. This might have made them more upset. Next time, try to let them speak more.

"It seemed like you interrupted" is an interpretation, not a direct observation. "Might have made them more upset" is speculative impact. "Try to let them speak more" is general advice, not tied to specific techniques.

“When I listened to the recording of the customer escalation call you handled on Tuesday at 3 PM (Situation), I noted that you interrupted the client four times while they were describing their technical issue, and you immediately offered a workaround before they finished explaining the full impact (Behavior). This led to the client expressing increased frustration, feeling unheard, and ultimately demanding to speak with a manager, which required my intervention and an additional hour of my time to de-escalate (Impact). What was your strategy for that call?”

**Specific Situation:** 'When I listened to the recording... on Tuesday at 3 PM' provides undeniable evidence and context. **Observable Behavior:** 'interrupted the client four times... immediately offered a workaround before they finished' describes precise actions. **Clear, Multi-faceted Impact:** 'client expressing increased frustration, feeling unheard, and ultimately demanding to speak with a manager, which required my intervention and an additional hour' details the cascading negative effects. **Seeking Strategy:** 'What was your strategy for that call?' invites the employee to reflect on their approach, opening a coaching opportunity.

Scenario 5: Workplace Context - Credit-Sharing

You always take credit for other people's work. It's not fair.

"You always take credit" is a harmful generalization and accusation. "Not fair" is an emotional judgment, not a professional impact statement. Lacks any situation or specific behavior, making it impossible to address.

In the team meeting yesterday, when we discussed the success of the new feature, you only mentioned your contributions. The rest of the team also worked hard. Maybe you could acknowledge them next time.

"You only mentioned your contributions" is a factual behavior but could be perceived as accusatory without context. "The rest of the team also worked hard" is a statement of fact, not an impact on the feedback recipient. "Maybe you could acknowledge them next time" is a weak suggestion, not a clear expectation.

“In yesterday's Q2 performance review meeting, specifically when you presented the success metrics for the 'Project Nexus' feature (Situation), I observed that you highlighted your personal contributions to achieving the 15% user engagement increase, but did not explicitly mention the significant contributions of the UX design team or the backend engineers (Behavior). This led to several team members feeling their efforts were overlooked and undervalued, potentially impacting team morale and future collaboration on cross-functional initiatives (Impact). Can you share your thinking behind focusing on your individual contributions in that presentation?”

**Specific Situation:** 'In yesterday's Q2 performance review meeting... when you presented the success metrics for the 'Project Nexus' feature' sets a precise, public context. **Observable Behavior:** 'highlighted your personal contributions... but did not explicitly mention the significant contributions of the UX design team or the backend engineers' describes the specific actions and omissions. **Clear Impact:** 'several team members feeling their efforts were overlooked and undervalued, potentially impacting team morale and future collaboration' details the interpersonal and team-level consequences. **Seeking Intent:** 'Can you share your thinking behind focusing on your individual contributions...?' invites a non-defensive explanation, allowing for coaching on recognition and team dynamics.

Common Mistakes

Spot which of these you recognise in yourself. Each entry explains why it happens, what to do instead, and shows the exact script difference.

Interview Perspective

Why interviewers ask about this

Interviewers ask about giving and receiving feedback, particularly using structured methods like SBI, to assess a candidate's emotional intelligence, communication skills, and ability to handle difficult conversations professionally. They want to see if you can provide constructive criticism without alienating colleagues and if you can absorb feedback without becoming defensive, both critical for collaborative, high-performance teams. It also reveals your capacity for self-improvement and developing others.

What interviewers evaluate

Ability to articulate a structured feedback process, using SBI as the delivery model, specific behavior, concrete impact, and a clear improvement request.
Demonstration of empathy and non-judgmental language when giving feedback.
Capacity to link specific behaviors to tangible business impacts.
Openness to receiving critical feedback and willingness to learn from it.
Maturity in separating feedback from personal identity.
Skill in coaching others toward improvement rather than simply pointing out flaws.

Common interview questions

“Certainly. I recall a situation last quarter where a junior engineer, Alex, was consistently submitting pull requests with incomplete documentation, causing delays for our QA team. I decided to use the SBI framework to ensure my feedback was objective. I approached Alex privately and said, 'Alex, in your last three pull requests for the payment gateway module (Situation), I noticed that the API endpoint descriptions and error handling procedures were either missing or incomplete in the documentation (Behavior). This meant our QA team had to spend an extra hour per review trying to understand the changes, which delayed our testing cycle by a day and pushed back our sprint commitment (Impact). What was your process for preparing the documentation?' We then discussed his approach, and I coached him on integrating documentation into his development workflow, which significantly improved his subsequent submissions.”

The strong answer clearly outlines the SBI framework, providing specific details for each component. It demonstrates empathy by asking about intent and shows a coaching mindset by following up with actionable guidance, leading to a positive outcome. It's structured and professional.

“I once received feedback from my manager regarding my participation in cross-functional meetings. She observed that in the weekly product syncs (Situation), I tended to hold back my opinions and didn't speak up, even when I had valuable insights (Behavior). The impact, she explained, was that the team was missing out on my perspective, and it sometimes gave the impression that I wasn't fully engaged, which could affect my executive presence (Impact). My immediate reaction was to pause and listen actively. I asked for a specific example, which she provided. I then reflected on it, realizing it stemmed from a desire to process information fully before speaking. I committed to a specific action: for the next month, I would aim to contribute at least one specific insight or question in every cross-functional meeting. I tracked this, and my manager later noted a significant improvement in my engagement and visibility.”

The strong answer demonstrates active listening, specifically asking for examples, and a structured approach to self-improvement. It acknowledges the feedback, outlines a concrete action plan, and highlights a positive outcome, showing growth and a receptive attitude. It applies the 'receiving SBI' principles.

“To ensure objectivity, I strictly adhere to the SBI framework. First, I focus on the 'Situation,' making sure it's a specific, verifiable event, like 'In Tuesday's stand-up.' Then, I concentrate on the 'Behavior,' describing only what I directly observed or heard, avoiding interpretations. For example, instead of saying 'You were dismissive,' I'd say 'You folded your arms and shook your head when I presented the idea.' Finally, I quantify or clearly articulate the 'Impact' on the project or team, rather than expressing personal feelings. If I find myself judging the person, I take a step back and rephrase my thoughts to describe only observable actions. This disciplined approach helps depersonalize the feedback and keeps it factual.”

This answer directly references the SBI framework as a tool for objectivity. It provides specific examples of how to distinguish between observable behavior and subjective interpretation, demonstrating a deep understanding of the framework's principles and practical application.

Red Flags

Using accusatory language ('You're always late,' 'You never listen').
Focusing on personality traits rather than observable behaviors.
Lacking specific examples to support the feedback.
Failing to articulate the impact of the behavior on the team or project.
Becoming defensive or argumentative when asked about receiving feedback.
Blaming external factors or other people for negative feedback received.
Showing no clear plan for improvement after receiving feedback.

Interview Tips

Practice converting judgmental statements into SBI statements: This builds the muscle memory for objective, fact-based feedback, crucial for clear communication under pressure.
Script answers to common feedback questions using SBI: Prepare concrete examples of giving and receiving feedback, detailing the Situation, Behavior, and Impact to demonstrate structured thinking.
Anticipate follow-up questions about intent: If you mention giving feedback, be ready for 'What was their reaction?' or 'How did you handle their response?' to showcase your coaching ability.
Actively listen and ask clarifying questions when discussing receiving feedback: This demonstrates your ability to process information, avoid assumptions, and engage constructively with critical input.
Prepare a specific example of how you acted on feedback: Interviewers want to see growth. Show that you didn't just receive feedback but implemented changes that led to a positive outcome.
Use 'I' statements when describing your personal impact: This shows you own your perspective without casting blame, making your feedback sound more professional and less confrontational.

Workplace Perspective

Read each scenario and the recommended approach, then check what your manager and stakeholders silently expect from you every day.

Scenario 1

You are a mid-level manager leading a cross-functional project. One of your direct reports, Sarah, a talented data analyst, has a habit of presenting her findings in team meetings using highly technical jargon without explaining it, which alienates non-technical stakeholders and causes confusion.

Schedule a private 1:1 meeting with Sarah. Start by setting the stage: 'Sarah, I wanted to chat about our last two project update meetings, specifically the one on Monday where you presented the Q2 data insights (Situation).' Then, describe the behavior: 'I noticed that you used terms like 'polymorphic relationships,' 'ETL pipelines,' and 'data normalization' without providing any context or simplified explanations (Behavior).' Explain the impact: 'This meant that several key business stakeholders, particularly from marketing and sales, appeared disengaged and later approached me to clarify the report, which slowed down our decision-making process and caused frustration (Impact).' Finally, ask about her intent: 'What was your approach to tailoring your language for that mixed audience?' Based on her response, coach her on identifying audience technical literacy and translating complex concepts.

Scenario 2

You are a senior individual contributor (IC) providing peer feedback during a code review for a fellow engineer, David. You've identified a recurring pattern of inefficient database queries that could lead to performance issues in production.

In the code review comments or a private Slack message, structure your feedback using SBI. 'David, in the pull request you submitted for the UserProfile service update (Situation), I observed that the fetchUserPreferences function makes a separate database call within a loop for each user (Behavior). This approach, if scaled to hundreds of users, could lead to N+1 query problems, significantly increasing database load and potentially causing latency for end-users in production (Impact). Could you explain your reasoning for this data retrieval pattern?' This opens a technical discussion without judgment, allowing David to explain or recognize the inefficiency.

Scenario 3

You need to give upward feedback to your manager, Alex, who frequently sends last-minute meeting invites with no agenda, making it difficult for you to prepare or prioritize your work.

Choose a private moment, perhaps during your regular 1:1. 'Alex, I wanted to provide some feedback regarding meeting invitations. For example, this morning (Situation), I received an invite for a 'Project Alpha Sync' scheduled for 10 AM, sent at 9:45 AM, without an agenda (Behavior). This meant I had to drop what I was doing, rush to join without any context, and couldn't contribute as effectively as I would have liked, as I didn't know what to prepare (Impact). Moving forward, would it be possible to send invites with at least an hour's notice and include a brief agenda, even if it's just two bullet points?' This frames it as a request based on impact, not a complaint.

Practical Exercises

Attempt each before revealing the answer.

Exercise 1

Rewrite the following judgmental statement into a clean SBI statement for a colleague.

Original statement: 'Tom, your reports are always late and it's really frustrating. You're completely unreliable and it makes the whole team look bad when we can't deliver on time because you can't meet a simple deadline. This needs to stop.'

Model Answer

“In our team's bi-weekly sync yesterday morning (Situation), I noted that the 'Market Trends Analysis' report was not in the shared drive, which was due by EOD last Friday (Behavior). This meant I couldn't include the up-to-date figures in my executive summary, and the leadership team had to reschedule their review, delaying our strategic planning by two days (Impact). What prevented you from submitting it on time?”

✓ Did you replace generalizations ('never get reports in on time') with a specific, recent situation?
✓ Is the 'behavior' purely observable ('not in the shared drive') rather than an interpretation ('unreliable')?
✓ Is the 'impact' concrete and professional ('leadership team had to reschedule,' 'delaying strategic planning') instead of emotional ('frustrating')?
✓ Did you include an open-ended question to understand intent, if appropriate?

Exercise 2

Improve the Response: You are a manager giving feedback to a direct report about their presentation skills. Refine the given feedback to be more SBI-compliant.

Model Answer

“In your 'Q3 Product Strategy' presentation to the leadership team last Tuesday (Situation), I observed that you spent 15 minutes on the introductory slides and then rushed through the key strategic recommendations, presenting them as bullet points with no supporting data (Behavior). This meant the leadership team didn't get a clear understanding of our proposed direction, and they left with more questions than answers, delaying critical approvals for our Q4 initiatives (Impact). Can you walk me through your preparation process for prioritizing content in that presentation?”

✓ Does the improved response specify the exact presentation and audience?
✓ Are the behaviors concrete and observable (e.g., 'spent 15 minutes,' 'rushed through,' 'no supporting data')?
✓ Is the impact clearly linked to business outcomes ('didn't get a clear understanding,' 'delaying critical approvals')?
✓ Does it invite dialogue to understand the presenter's choices, rather than just stating flaws?

Exercise 3

Scenario Analysis: A colleague, Sarah, consistently arrives 5-10 minutes late to team meetings, which often start with her apologies. How would you provide SBI feedback?

Model Answer

“Sarah, I wanted to share some observations from our team's daily stand-up meetings. Specifically, for the last three stand-ups, including this morning's (Situation), you've joined 7-10 minutes after the scheduled start time, and each time the meeting has been paused for your arrival (Behavior). This means we're losing valuable time at the beginning of each stand-up, sometimes having to re-cover points, which can disrupt our flow and delay the overall progress update for the team (Impact). What's been challenging for you to make it to stand-up on time recently?”

✓ Is the situation specific and recent enough to be easily recalled by Sarah?
✓ Is the behavior described objectively and quantifiably ('7-10 minutes late,' 'meeting paused')?
✓ Does the impact clearly explain the consequences for the team and meeting effectiveness?
✓ Does the question encourage Sarah to share her perspective without defensiveness?

Exercise 4

Communication Correction: Identify and correct the SBI mistake in the following feedback delivered by a manager to a team member.

Model Answer

The mistake here is combining personal emotion ('I'm really annoyed') with an accusation ('You just ignored it') and vague impact ('huge mess'), instead of focusing on objective facts. A corrected SBI statement would be: “In the latest design iteration for the 'Project Nova' dashboard, which you submitted for review yesterday (Situation), I observed that the client's requested changes regarding the data visualization for the 'Performance Metrics' section were not incorporated (Behavior). This meant we had to revert to an earlier version, losing a day of development work, and now we risk missing our internal sign-off deadline (Impact). What was your understanding of the client's feedback for that section?”

✓ Was the emotional accusation removed and replaced with objective observation?
✓ Is the 'behavior' clearly defined as an action/omission, not an assumption of ignoring?
✓ Is the 'impact' specific and measurable ('losing a day of development work,' 'risk missing deadline')?
✓ Does the corrected version invite a non-defensive explanation of intent?

Exercise 5

Professional Rephrasing: You need to inform a senior stakeholder, who is consistently late to meetings they organized, about the impact. Rephrase your internal thoughts into a professional SBI statement suitable for a private conversation.

Model Answer

“Sarah, I wanted to provide some feedback regarding the team's weekly budget review meetings you host. For the last three meetings, including the one this morning at 9 AM (Situation), you've joined 5-10 minutes after the scheduled start time (Behavior). This means that all five attendees were waiting for you to start, collectively losing about 30 minutes of productive time each meeting, which delays our agenda and pushes back our critical budget allocation discussions (Impact). What challenges are you facing that lead to these late starts?”

✓ Did you eliminate all emotional and judgmental language from your internal thoughts?
✓ Is the situation clearly tied to specific, recent occurrences of the meetings Sarah organizes?
✓ Is the behavior precisely described and, ideally, quantified (e.g., '5-10 minutes after')?
✓ Does the impact clearly explain the collective time loss and its effect on meeting objectives?
✓ Does the closing question invite an explanation from Sarah in a respectful manner?

Open-Ended Practice Scenario

Read the scenario, respond out loud or in writing, then reveal the model answer and honestly pick which rubric tier matches your response.

Your Scenario

You are a Product Manager. Draft an SBI feedback message to a junior UX Designer, Alex, who recently submitted a design mockup for a new feature. The mockup did not follow the established brand guidelines regarding color palette and typography, requiring significant revisions and delaying developer handoff. Your goal is to provide clear, actionable feedback while maintaining a positive coaching relationship.

Model Answer

Subject: Feedback on 'Project Nova' Mockup - Brand Guidelines

Hi Alex,

I wanted to provide some feedback regarding the 'Project Nova' dashboard mockup you submitted yesterday (Situation). I noticed that the color palette used for the data visualizations and the typography chosen for the headings did not align with our established brand guidelines, specifically Version 2.1 (Behavior). This meant that the development team couldn't begin implementing the design as planned, and we've had to allocate an extra day for revisions and re-approval from marketing, which now pushes back our developer handoff and risks delaying our sprint commitment (Impact).

Could you walk me through your design process for selecting those specific elements? What were you hoping to achieve with those choices?

I'm happy to review the brand guidelines with you if anything was unclear, and we can discuss how to integrate them seamlessly moving forward.

Best,
[Your Name]

Scoring Rubric

Excellent

Response flawlessly applies all SBI/SBII principles: Situation, Behavior, and Impact are highly specific, objective, and clearly articulated. The language is entirely non-judgmental, professional, and fosters a strong coaching relationship. The Intent question is perfectly placed, and the feedback offers clear, actionable next steps, demonstrating deep strategic communication skill.

Good

Response effectively applies SBI/SBII, with clear Situation, Behavior, and Impact. The language is mostly objective, and the tone is professional. There might be minor areas where the specificity could be enhanced, or the Intent question could be more precisely phrased, but the overall feedback is constructive and actionable.

Developing

Response attempts to use SBI but shows some weaknesses. Either one of the S-B-I components is vague or missing, or there are instances of subjective language or mild judgment. The Intent question might be present but not fully effective. The tone is generally professional but might lack strong coaching elements, making the feedback less actionable.

Needs Improvement

Response largely misses the core principles of SBI. It contains significant generalizations, subjective judgments, or accusations. The Situation, Behavior, or Impact are poorly defined or absent. The tone may be confrontational or unhelpful, likely to trigger defensiveness and fail to achieve positive behavioral change. Little to no actionable guidance is provided.

Quiz: Test Your Knowledge

🧠

SBI Feedback Framework Quiz

Test your knowledge of SBI Feedback Framework across vocabulary, scenario-based, error detection, and professional judgment questions.

5Per Round

Key Takeaways

Always start feedback with a specific, recent 'Situation' that both parties can recall, grounding the conversation in fact.

Describe 'Behavior' using only observable actions or words, avoiding interpretations, assumptions, or character judgments.

Clearly articulate the 'Impact' of the behavior on the project, team, or business, explaining the 'why' behind the feedback.

Utilize the SBII variation by asking 'What was your intention?' after delivering S-B-I to foster understanding and coaching.

Deliver feedback privately and as close to the event as possible to maximize relevance and accuracy.

Avoid generalizations like 'you always' or 'you never'; stick to specific instances.

Frame feedback around improvement and learning, not blame or accusation.

When receiving feedback, pause, listen actively, and ask for specific examples to ensure clarity.

Separate the feedback from your identity; focus on the behavior, not your self-worth.

Practice converting judgmental thoughts into objective SBI statements to build your communication muscle memory.

SBI is a tool for all levels of a professional hierarchy, effective for peer, upward, and downward feedback.

For non-native speakers, focus on scripting key phrases and translating abstract concepts into specific, observable language.

Remember that the goal of SBI is to foster productive dialogue and behavioral change, not to win an argument.

Always end feedback conversations with a clear path forward or agreed-upon next steps for improvement.

Frequently Asked Questions

Is SBI only for negative feedback? Can I use it for positive feedback?⌄

While often highlighted for constructive criticism, SBI is incredibly powerful for positive feedback too. Using SBI for positive recognition makes it specific, impactful, and memorable, reinforcing desired behaviors. For example: 'In yesterday's client presentation (Situation), you proactively addressed the unexpected technical question with a clear, concise explanation (Behavior). This not only resolved the client's concern immediately but also showcased our team's expertise and strengthened client trust (Impact).' This makes positive feedback far more meaningful than a general 'Great job!'

What if the person denies the behavior or disputes the impact?⌄

If the person denies the behavior, re-state your observation calmly. If possible, reference objective evidence (e.g., meeting notes, code logs, email threads). If they dispute the impact, explain your perspective using 'I' statements and focus on the logical chain of events. For instance, 'I understand that wasn't your intention, but the impact I observed was that...' The goal is not to 'win' the argument, but to ensure mutual understanding of different perspectives. If a complete agreement isn't possible, agree to disagree on the interpretation but acknowledge the different perspectives.

How can I give SBI feedback to someone who is much more senior than me?⌄

When giving upward feedback, timing and tone are crucial. Schedule a private 1:1. Frame the feedback around its impact on your ability to perform or on team effectiveness, not as a personal critique of their leadership. Use deferential but clear language. For example: 'I wanted to share an observation that's impacting my workflow. In our team meeting on Monday (Situation), when you assigned the 'Alpha Project' task directly to Sarah, a junior engineer on my team (Behavior), it meant I was unaware of her new workload, which prevented me from properly allocating resources and prioritizing tasks for our team (Impact). Would you be open to routing tasks through me in the future so I can manage workload effectively?'

I'm a non-native English speaker and worry about misphrasing SBI feedback. Any tips?⌄

Focus on simplicity and directness. Script common SBI phrases in advance and practice them. Prioritize clear, concise verbs and nouns over complex sentence structures or idioms you're unsure of. For example, instead of 'Your discourse was rather circuitous,' say 'You took a long time to get to your main point.' Don't hesitate to use written SBI (email, Slack) for important feedback, as it allows you more time to formulate your message accurately. Ask a trusted colleague or mentor to review your drafted feedback for clarity and tone before delivery.

How does SBI apply to virtual or asynchronous feedback in the AI era?⌄

SBI is exceptionally well-suited for virtual and async feedback. In Slack, email, or Loom videos, the specificity of Situation, Behavior, and Impact prevents misinterpretation that can easily occur without in-person cues. For example, a Loom video can show the 'Situation' (e.g., a specific part of a document or UI), then narrate the 'Behavior' (e.g., 'this button is missing a label'), and explain the 'Impact' (e.g., 'which violates accessibility guidelines and confuses users'). AI tools like Gemini or Copilot can also help you draft and refine SBI statements, ensuring they are objective and clear before you send them.

Should I use SBI for performance reviews or just informal feedback?⌄

SBI is highly effective for both informal, real-time feedback and formal performance reviews. For performance reviews, using SBI ensures your feedback is well-documented, objective, and defensible, preventing reviews from becoming subjective or emotional. It provides concrete examples that managers can use to justify ratings and help employees create clear development plans, making the review process much more productive and fair.

What if the behavior is culturally influenced, especially for international teams?⌄

When dealing with culturally influenced behavior, deliver SBI feedback with an enhanced focus on the 'Intent' (SBII). After describing the S-B-I, ask 'What was your intention?' or 'Can you help me understand your approach here?' This opens a dialogue to uncover cultural norms or communication styles that might be at play. The impact might still be real (e.g., 'it delayed our decision'), but understanding the underlying cultural context allows for more empathetic coaching and finding mutually agreeable solutions that respect diverse backgrounds.

Does AI replace the need for human SBI feedback?⌄

No, AI does not replace the need for human SBI feedback; it augments it. While AI tools can analyze communication patterns, summarize interactions, and even help draft SBI-compliant messages, the empathy, nuance, and judgment required to deliver feedback effectively (especially the 'Intent' component and subsequent coaching) remain uniquely human. AI can help you prepare better feedback, but the delivery and the relationship-building aspect are still your responsibility. It can help you make your feedback more precise, but not replace the human connection.

How do I ensure my SBI feedback is actionable?⌄

Actionability comes from the specificity of the 'Behavior' and the clarity of the 'Impact.' If the behavior is vague, the person won't know what to change. If the impact isn't clear, they won't understand why they should change. After delivering S-B-I (and possibly asking about intent), shift to collaborative problem-solving. Ask: 'What do you think you could do differently next time?' or 'What support do you need to ensure this doesn't happen again?' Agree on specific, measurable next steps.

How do I avoid sounding robotic when following the SBI structure?⌄

The SBI framework provides a structure for clarity, not a script to be delivered robotically. Think of it as a skeleton for your message. You can infuse it with your natural tone, empathy, and coaching style. The key is to ensure the core S, B, and I elements are present and objective. Practice makes it sound more natural. The goal is to be clear and kind, not cold. The SBII 'Intent' question is particularly helpful for adding a human, empathetic touch to the conversation.