How to Give Feedback With the SBI+ Model (Without the Sandwich, in 90 Seconds)

Why Most Feedback Fails in the First Sentence

Feedback fails in the gap between behavior and judgment. "You were disrespectful in the meeting" is not feedback, it is a verdict about character, and verdicts trigger defense, not change. The recipient spends the conversation building a counter-case instead of hearing the effect. The original SBI model, popularized by the Center for Creative Leadership, exists precisely to close that gap: it strips the judgment out by anchoring every element in what a camera would record.

The plus in SBI+ is the upgrade most implementations miss: one genuinely curious question at the end. Without it, SBI is a monologue with better manners, the leader delivers a clean package and waits for agreement. With it, the recipient owns the floor, and the answer is usually where the actual fix lives. "You interrupted three times" becomes a different conversation when the reply is "I know, I was terrified the client would hear us disagree on the timeline."

The Four Beats, With Camera Rules

The full SBI feedback model runs on four beats and one hard rule: if you cannot film it, rewrite it. The beats take ninety seconds of speaking time when done correctly, and each one exists to remove a specific way the conversation can go wrong. Here is the structure, then the beats in detail.

Beats 1 and 2: Situation and Behavior

Beat one, Situation: pin the moment. "In yesterday's client review", specific and recent. The word "always" is banned; "always" converts feedback into a character trial, and nobody changes a character on a Tuesday afternoon. Beat two, Behavior: camera rules only, actions, words, silences. "Interrupted three times while she presented the timeline" is behavior; "was disrespectful" is a judgment wearing behavior's clothes.

Beat 3: Impact Without Mind-Reading

Beat three, Impact: the effect you actually observed, "she stopped adding points, and we lost two observations we needed." Report effects you witnessed, not motives you mind-read; "you undermined her authority" is your interpretation, not an impact, and it reopens the courtroom you spent two beats closing. If you cannot point to a visible consequence, deliver the Situation and Behavior and stop, impact you have not observed is speculation wearing a lab coat.

Beat 4: The Plus Question and the Silence

Beat four, the Plus: one curious question with genuine openness, "How did it look from your side?" Then the hardest part: silence. The loop only works if the floor actually changes hands, and the first seconds of that silence are where untrained leaders fill the air and hand the verdict back. Count to five; the answer that arrives after the pause is the one worth hearing, and the full hard-conversation method extends this beat into complete dialogue design when the stakes go up.

Worked Example: The Missed Deadline

The raw material most leaders carry: "He's careless with deadlines and it's affecting the team." Run it through the beats. Situation: "Tuesday's draft arrived Thursday at noon." Behavior: "This is the second time this month a milestone slipped without an early heads-up, both times it surfaced on the due date." Impact: "The client team has started building buffer into everything we touch, which costs us credibility we need for the migration." Plus: "What's happening from your side?"

Notice what changed: the character assessment ("careless") became two dated, filmable events; the vague damage ("affecting the team") became one observed effect. The version runs under ninety seconds of speaking time, with no sentence the recipient can factually dispute, which is exactly why they can hear it without defending. End the conversation with a Nail: "So: a one-line heads-up the moment a milestone is at risk, and the first two get a thank-you, not an interrogation."

Worked Example: The Defensive High Performer

Harder case: your strongest contributor dominated the junior analyst's presentation, and she has done it before. The temptation is to soften, high performers are valuable, and the sandwich instinct fires. Run the same four beats instead. Situation: "In this morning's design review." Behavior: "When Ana reached slide three, you took the cursor and walked the room through the model yourself, she presented two of her ten slides." Impact: "She stopped, and I watched her check everything with you for the rest of the deck, we just trained a lead analyst to need permission."

The plus question is doing more work here than usual: "I know the model is your work, how did it look from your side?" High performers respond to respect for their standards, and the genuine question acknowledges the motive while holding the behavior. Expect the answer to reveal something real, protectiveness, pace anxiety, a detail the room missed, and fold it into the Nail: "Next review, the deck is hers end to end; your model walkthrough becomes slide twelve, invited."

The 24-Hour Rule and the Composure Exception

Timing decides whether feedback is information or indictment. Inside a day, the conversation is about a specific event both parties remember. Past the window, your rerun has compounded the story and their memory has decayed, "we need to talk about how you've been lately" lands like a subpoena because it is one. The 24-hour rule has a second effect most leaders miss: it caps how many loops exist, because a structure that demands next-day delivery forces you to triage what is actually worth a conversation.

The composure exception: if you are still activated at hour two, delivering now means delivering your adrenaline. Run your regulation stack, log the trigger, and deliver tomorrow morning inside the window. The rule exists to prevent avoidance, not to force delivery from a surge, feedback delivered at volume trains teams to fear the messenger, not to trust the message.

What the Feedback Numbers Say

The data behind the method is more encouraging than most leaders expect. In the Zenger Folkman survey published by Harvard Business Review in 2014, 92 percent of respondents agreed that corrective feedback, delivered appropriately, improves performance, and 57 percent actively prefer it to praise. Yet the Interact/Harris Poll found 69 percent of managers uncomfortable communicating with the people they manage. The appetite exists; the delivery is the bottleneck, which is precisely the problem a structure like SBI+ solves.

The coaching-specific numbers tell the same story from another angle, organizations that train managers to hold structured conversations see engagement and retention move, which is why the workplace coaching statistics belong in any proposal that funds feedback training.

The Praise Version Nobody Runs

The same structure, pointed at what went right: "In the outage call, you gave the timeline before anyone asked" (Situation + Behavior). "That bought us fifteen calm minutes and killed the panic spiral" (Impact). "How did you know to lead with that?" (Plus). Fifteen seconds, and the recipient now knows the exact behavior to repeat, and that you noticed it. Vague praise is a mood; specific praise is training data.

Run several specific praise loops for every corrective one. Gallup's engagement research attributes roughly 70 percent of the variance in team engagement to the manager, and the everyday currency of that variance is small conversations, praise and correction in roughly healthy proportion. Leaders who only run SBI+ when something breaks train their teams to associate their approach with dread, a reputation that quietly erases the technique's value.

The Five Mistakes That Sink SBI+

The method is simple, which means the failure modes are mostly self-inflicted. Five account for nearly every failed loop we see in practice, and each one has a mechanical fix you can apply in the moment.

• Stacking three loops in one sitting, one behavior, one loop, one next step; three issues means three conversations
• Fake curiosity, the plus question asked with a verdict already written reads as worse than no question
• Skipping the Nail, people forgive hard feedback; they do not forgive hard feedback that changes nothing
• Judgments in camera clothing, "you were dismissive" is not filmable; rewrite until it is
• Delivering from a surge, at volume, teams hear the adrenaline, not the content; regulate first, deliver inside 24 hours

SBI+ in Writing: Chat, Email, and Async Teams

The loop survives in writing, with adjustments, and the adjustments matter more than most remote managers realize, because written feedback loses the warmth cues that make a live loop land. Two sub-rules do most of the work: compress the beats, and protect the channel.

The Two-Line Written Loop

Cut the beats to two lines: the filmable observation and its effect, then the question, "In today's review, Ana presented two of ten slides before you took the cursor; I worry we trained a lead analyst to check everything with you first. How did it look from your side?" Email carries tone poorly, so the plus question is not optional in writing, it is the only signal that this is a conversation and not a citation.

The Async Rules

Never deliver corrective feedback in a group channel, and never in the same message as a decision the person must act on, the loop needs its own space to work. For distributed teams, written SBI+ plus a fifteen-minute call is the pattern that survives async work: the written loop does the thinking, the call does the connecting. And keep a copy in your own log, written loops are searchable, which makes the praise ledger easier to keep honest.

Rehearse It Before It Counts

SBI+ fails in delivery, not design. The structure is learnable in an afternoon; the composure to run it while someone deflects is the actual skill. That is why rehearsal matters: play the defensive version, "everyone does it," "well, YOU did worse in March", with an AI practice partner or a peer, and find the line you will hold when it happens for real.

If you want the coaching craft beyond feedback, questions that develop people rather than correct them, that is a different discipline with its own training path, up to and including the Leadership Coaching Mastery certification. Start with the loop; the deeper toolkit will make itself obviously necessary or not.

The 30-60-90 Feedback System

Install the method on a schedule and it becomes a system. First thirty days: run one SBI+ loop per week, praise or corrective, and log each in a line: date, behavior, nail. Days 31 to 60: add rehearsal before every corrective loop and start counting your praise-to-correction ratio. Days 61 to 90: coach a peer through their first loops, because teaching the model is what installs it permanently. By day ninety you will have a personal ledger of conversations, and the data habit that sustains all of it.

The Emotional Intelligence for Leaders program builds SBI+ on Day 9 as one of its three spine frameworks, with the trigger-log composure work underneath it and the hard-conversation scripts above it. Day 1 runs free with an account if you want the complete system, but the loop above, rehearsed once and delivered this week, is already better feedback than most managers ship in a quarter.

Frequently asked questions