The SBI Framework: Optimizing Communication and Delivering Objective Feedback

Step 2: The Camera Check (Isolating the Behavior)

• Objective: Present facts and eliminate judgmental adjectives.
• Execution: Describe only what you heard and saw. Avoid using absolutes like "Always" or "Never."
• Example: Instead of saying "You are very stubborn," say: "When I presented the user drop-off data at the checkout stage, you interrupted me three times and dismissed the Mixpanel data without further explanation."

Step 3: Articulating the Impact

• Objective: Connect the behavior to business outcomes, user experience, or team morale.
• Execution: Use structures like "This resulted in..." or "I felt / The team had to...".
• Example: "This caused the team to spend 20 minutes in a circular debate, we failed to finalize the API specs, and personally, I felt disrespected when presenting the data."

Step 4: Extending with a second 'I' - Intent/Inquiry (Optional but critical) After delivering the SBI, pass the microphone back to the receiver with an open-ended question: "What is your perspective on this?" or "Were you facing any specific challenges at that moment?"

4. Real-world Example (Case Study Application)

Context: You are a Senior PM at a Tech Unicorn (e.g., Grab, Shopee). Your Tech Lead (Alex) has consistently skipped Daily Standups over the past week. Consequently, the QA team doesn't know which features are ready for testing, creating a bottleneck for the Friday release.

• Typical Feedback (Emotional & Ineffective): "Alex, you've been slacking off lately. You're skipping standups and leaving everyone in the dark. You need to be more responsible for this release." (Impact: Alex gets defensive, blames a heavy coding workload, and the conflict escalates).
• SBI Framework Feedback (Data-driven):
• • Situation: "Alex, during the three Daily Standups from Tuesday to Thursday this week..."
  • Behavior: "...you were absent and did not leave a status update in our team's Slack channel."
  • Impact: "Because of this, the QA team was unaware of the Payment module's status, leaving them idle all of yesterday morning. As a result, the risk for our Friday release has now escalated to Red."
  • Inquiry: "Are you bogged down by a critical bug or is there another blocker preventing you from syncing up with the team?"

5. Anti-patterns & Pitfalls to Avoid (Trade-offs)

Despite its power, SBI can backfire if practitioners fall into these systemic errors:

1. The Sandwich Feedback Trap: Sandwiched negative feedback between two hollow compliments. This dilutes the severity of the Impact and makes the praise feel insincere. If you need to deliver constructive criticism, use SBI directly.
2. Mind-Reading: Confusing "Assumptions" with "Behaviors." Instead of saying "Because you don't care about the project..." (assumption), stick strictly to "Because you didn't reply to the requirement approval email..." (behavior).
3. Vague Impact: Using broad phrases like "It affected our quality." Be highly specific: "It increased system latency by 200ms," or "It caused Client B to threaten to cancel their contract."
4. Over-scripting (The Robot Effect): Reciting SBI like a memorized script strips the conversation of empathy. It requires practice to naturally assemble the S-B-I blocks within conversational language.

Ready to master the toughest Behavioral interview scenarios?

Join Product Decode today to practice the SBI framework in simulated interview rooms. Our AI will play the role of "Difficult Stakeholders" and score your choice of words, feedback structure, and conflict resolution skills against Big Tech standards!