I came out of the SBID session genuinely excited, and I want to name why. I’m a routine person. I love an explicit format. As an engineer, the practices that compounded for me — clean commits, structured PR descriptions, post-mortems that named the failure honestly — were all small formats I drilled until they became invisible. The SBID format is that, for feedback.
I’d been giving feedback in something close to this shape for a while, drawing on managers I’d worked under who gave good feedback well. But it was loose — I’d hit the four parts most of the time, miss one of them sometimes, and have no way to teach the move to my team because I couldn’t quite name what I was doing. SBID gives me the name, and it gives me the teachable shape.
The format, plainly
| Field | Question it answers | Why it’s there |
|---|---|---|
| S — Situation | Where and when did this happen? | Anchors the conversation in a specific moment, not a pattern accusation |
| B — Behavior | What did the person do that I can describe objectively? | Separates observation from interpretation |
| I — Impact | What was the effect on the work, the team, or me? | Names the cost without naming the person’s intent |
| D — Desired outcome | What would I like to see in the next similar moment? | Makes feedback actionable instead of regretful |
The four fields look mundane. The discipline of writing all four — every time, before the conversation — is where the value is.
Why each field matters
Situation seems trivial, but it does the job of moving the conversation from “you keep doing this” to “in our planning meeting yesterday”. The first is an accusation that the person will defend against. The second is a description of a moment they remember as clearly as I do. The conversation that follows is grounded in the same scene, and that grounding does a huge amount of work before anyone has said anything hard.
Behavior is the field I was most likely to skip when I was giving feedback informally. I’d jump straight from situation to impact and find myself saying things like “you interrupted the team because you weren’t really listening”. The first half is the behavior; the second half is my interpretation pretending to be a behavior. When I force myself to write only what I literally saw — “you finished a teammate’s sentence twice in the same five minutes” — the conversation gets dramatically easier to have, because there’s nothing to argue with. SBID closes the skip-this-field shortcut, and I’m grateful for it.
Impact is where care shows up, if I let it. The temptation is to make the impact about the person — “that made you look bad” — when the more useful version is about the work or the team. “It made it harder for two people to bring their idea, and we lost the second one’s angle entirely.” The person hears what they cost. They don’t have to defend their character to absorb it.
Desired outcome is the field that turns feedback from a verdict into a request. Without it, the person walks away knowing I’m unhappy and unsure what I actually want. With it, they walk away with a concrete next-time. The phrasing I use is next time, I’d like to see [X] — much easier to act on than don’t do [Y] again.
A worked example
A senior engineer on my team — sharp, well-respected, normally collaborative — pushed back hard on a peer’s design in a review last month, in front of three other people, in a tone that felt sharper than the situation needed. The peer went quiet for the rest of the meeting and walked out without raising any of the questions she’d planned to bring.
I had the feedback conversation that same afternoon. The version I gave him, written out as SBID:
- S: In this morning’s design review, when we were discussing the rate limiter approach.
- B: You interrupted twice and used the phrase “that’s just not how this works” about her proposal.
- I: She didn’t bring up the two follow-up questions she’d prepared, and I missed her angle on the failure mode. The team lost something we needed.
- D: Next time, I’d like us to push back on the design without phrases that close the door on the person, even when we’re sure we’re right.
His response was I didn’t realise the impact, and I want to talk to her directly about it. He did, that same day. He apologised, she brought the questions she hadn’t asked, the design improved. None of that happens if I open with “you were harsh today” — which is the version I’d have given before I’d internalised the four fields.
What SBID is doing for my preparation
The unexpected gift of the format is what it’s doing to my pre-conversation thinking.
The discipline of writing the four fields before the conversation forces me to check whether I actually have feedback or just an irritation.
If I can’t fill in the Situation, the feedback is about a pattern, not a moment, and the conversation is probably premature.
If I can’t fill in the Behavior cleanly without smuggling in interpretation, I haven’t separated what I saw from what I think it meant, and I need to do that work before I speak.
If I can’t articulate the Impact in terms of the work or the team, I’m probably giving feedback that’s really about my own discomfort, and I need to either find the real cost or let it go.
If I can’t write the Desired outcome concretely, I haven’t decided what I actually want, and the person can’t possibly read my mind better than I can.
When all four fill in cleanly, the conversation is almost easy to have. When they don’t, the discomfort of writing them is a sign that the conversation isn’t ready yet.
What I’m most excited about
I want to teach SBID to my team. That’s the multiplier I’m reaching for.
Feedback from the manager to the team is good. Feedback from the team to itself — clean, honest, structured — is much, much better. The team I lead already gives each other feedback in good faith; what they lack is the four-field shape that makes the feedback land cleanly under pressure. I’m going to make SBID the framework we use, model it openly in the next few weeks, and ask people to use it back on me first. The moment one of my engineers gives me SBID feedback on my own behaviour is the moment I’ll know the format has taken hold.
That, more than anything else, is what I’m taking back from this session.
The team effectiveness piece
SBID looks small and produces large compounding effects. Feedback that lands cleanly, without defensiveness, changes how often people are willing to receive it. A team where every piece of feedback used to take a thirty-minute conversation and now takes a five-minute one is a team that improves at twelve times the rate, just from the math.
The other effect — the one I find most interesting — is that SBID-style feedback is contagious. Once a team has heard it a few times, they start using it on each other and on me. The first time someone on my team gives me a clean SBID critique of a meeting I ran, I’ll feel it land as cleanly as I’ve ever felt feedback land, and I’ll know they took the format from how I’d been giving it. That’s the team I’m trying to build.
What I’ll still get wrong
I’ll rush the Desired outcome. The first three are easier; the last one forces me to commit to what I actually want, and sometimes I haven’t done that work yet. When I catch myself ad-libbing the D field, I know I’ve shown up to the conversation half-prepared.
The discipline of writing all four, every time, even for what looks like small feedback, is the practice I’m committing to. I’m a routine person — practices like this stick for me. SBID is one I’ll be running for a long time.