08 · Feedback Basics (Giving and Receiving)¶
Feedback is where servant leadership either builds trust or spends it. Vague praise builds nothing; harsh, poorly delivered criticism damages trust (Module 5) even when the content is correct. This module covers a simple, repeatable structure for giving feedback that's specific and actionable, and — just as important for a servant leader — how to receive feedback well yourself, since a leader who can't take feedback graciously undermines their credibility to give it.
1. The SBI framework for giving feedback¶
Situation - Behavior - Impact is a compact structure that keeps feedback specific and non-judgmental:
| Component | What it captures | Example |
|---|---|---|
| Situation | The specific context — when and where | "In yesterday's client call..." |
| Behavior | The specific, observable action — not a character judgment | "...you interrupted the client twice before they finished their question..." |
| Impact | What effect it had | "...which made it seem like we weren't fully hearing their concern, and I saw them get visibly frustrated." |
Compare the full SBI statement — "In yesterday's client call, you interrupted the client twice before they finished their question, which made it seem like we weren't fully hearing their concern, and I saw them get visibly frustrated" — against a character judgment like "you're too aggressive in client calls." The SBI version describes something the person can recognize and change; the character judgment invites defensive disagreement about identity ("I'm not aggressive") instead of a conversation about the specific behavior.
2. Positive feedback needs the same specificity¶
A common mistake is treating positive feedback as needing less structure than critical feedback — "great job!" is nice to hear but teaches nothing about what to repeat. SBI works the same way for reinforcing behavior: "In the retro yesterday, when you asked Ben to walk through his reasoning before the group weighed in, it meant the quieter voices got heard before the loudest opinion anchored the discussion — that's exactly the kind of facilitation this team needs more of." This tells the person precisely what to do again, which is the actual point of positive feedback.
3. Timing and setting¶
- Give it close to the event. Feedback saved up for a quarterly review loses the specific context and feels like an ambush; both praise and correction land better close to when they happened.
- Praise can be public; correction should usually be private, unless the person has explicitly said they prefer direct feedback in the moment regardless of setting — public correction almost always triggers a defensive reaction that blocks the message from actually landing.
- Ask permission for unsolicited feedback when it's not part of a formal process: "I noticed something in that meeting — want to hear it?" respects the other person's readiness to hear it right then, and measurably increases how receptively feedback is heard.
4. Receiving feedback well¶
A servant leader models the same openness to feedback they ask of others. A simple three-step response to receiving feedback, especially critical feedback:
- Listen fully before responding (Module 3) — resist the urge to explain or defend before the other person has finished.
- Ask a clarifying question if any part is vague — "can you give me a specific example?" — rather than either accepting or rejecting an unclear statement.
- Thank them, specifically for the act of telling you, separate from whether you agree with the content — "thanks for telling me that directly" — since the goal is to make people feel safe giving you feedback again, which many leaders unintentionally discourage by reacting defensively even once.
5. A worked example¶
A manager, Diego, needs to give a report, Sam, feedback that his written updates are too long and buried the key point.
- Character-judgment version: "Your updates are disorganized" — vague, and Sam has no clear idea what to change.
- SBI version: "In this week's status update (situation), the key risk — that the vendor contract isn't signed yet — was in the fourth paragraph after three paragraphs of background (behavior), which meant I almost missed it and had to re-read the whole thing to find the actual ask (impact). Could you lead with the risk and the ask next time, background after?" Sam now has a specific, actionable change to make, and the next update leads with exactly that.
How It Actually Works¶
The Situation-Behavior-Impact structure works because it deliberately keeps feedback out of a specific neural danger zone: identity threat. Feedback framed around traits ("you're disorganized") is processed by the brain similarly to a social-status threat — it activates overlapping circuitry with physical threat response (this is the basis of Eisenberger's social pain research showing social rejection lights up some of the same regions as physical pain) — which triggers defensiveness before the listener has processed the content. SBI's trick is to anchor the feedback to an observable event and its measurable effect, deliberately routing around the identity/trait layer entirely: "in yesterday's client call (situation), when you interrupted the client twice (behavior), they stopped offering details for the rest of the call (impact)" describes what happened without asserting anything about who the person is, which leaves less surface area for a threat response to attach to.
Why timing changes whether feedback is usable at all, not just how comfortable it feels. Memory consolidation research shows episodic detail — the specific sensory and contextual texture of an event — decays within hours to days, while a compressed, evaluative summary ("that didn't go well") persists much longer. Feedback given days later forces the receiver to reconstruct a summary judgment they've already half-formed on their own, which triggers a genuine disagreement about facts, not just tone. Feedback given the same day still has access to the receiver's actual episodic memory of the event, so the two parties can examine what actually happened rather than negotiating between two competing summaries.
Why receiving feedback well requires a distinct skill, not just an absence of defensiveness. Interpreting feedback correctly requires holding two things simultaneously that the identity-threat response wants to collapse into one: "this specific behavior had this effect" and "I am not defined by this one data point." Stanford's Carol Dweck's research on growth vs. fixed mindsets shows the difference is largely about which of these two framings a person's implicit theory of ability defaults to under stress — someone with a fixed-ability mindset hears feedback as a verdict on a stable trait, while someone with a growth mindset hears it as information about one instance of a skill still being built, which is why the same sentence produces wildly different reactions in different people, and why receiving feedback well is trainable independent of the feedback itself.
Exercise¶
Think of one piece of feedback you've been meaning to give someone but haven't, because it felt awkward or you weren't sure how to phrase it. Write it out fully using the SBI structure — situation, behavior, impact — and check it doesn't slide into a character judgment anywhere. Then deliver it this week, in person or on a call rather than in writing, and afterward write 2-3 sentences on how it landed and what, if anything, you'd phrase differently next time.