Day 02 · 2026.05.27

The Craft of Feedback: From "It's Fine" to "Here's What I Saw You Do"

Topic: Giving Feedback·4 Principles
"When you criticize someone without taking the time to show that you care, your guidance feels obnoxiously aggressive." — Kim Scott
This week's premise: Most managers get feedback wrong at one of two poles — swallowing the truth to spare feelings (Ruinous Empathy) or hurling "objective" criticism (Obnoxious Aggression). Both send the team in the wrong direction. The moment Sheryl Sandberg told Kim Scott "you said 'um' a lot" wasn't an attack on her professionalism — it was care delivered straight. This week we unpack the craft: use Kim Scott's 2x2 to locate your own default style, replace personality verdicts with SBI (Situation–Behavior–Impact), treat "now vs. later" as a deliberate design choice rather than a reflex, and set a channel protocol — what belongs in Slack, what must be face-to-face. Get these four right, and a report will tell you, for the first time, that they finally feel seen.
PRINCIPLE 01

Radical Candor 2x2: Care Personally × Challenge Directly Care Personally + Challenge Directly

Kim Scott2x2 matrixSelf-locate
One-line principle
Feedback isn't a single axis from "gentle" to "harsh." It has two axes: do you genuinely care about this person, and are you willing to challenge them directly? Both required for Radical Candor. Drop one, and you fall into one of three failure quadrants.
In the author's own words
"Radical Candor is what happens when you put 'Care Personally' and 'Challenge Directly' together. It builds trust and opens the door for the kind of communication that helps you achieve the results you're aiming for." — Kim Scott, Radical Candor, Ch. 1
Radical Candor 2x2
Challenge Directly → Care Personally → Ruinous Empathy Kindness without honesty Care ✓   Challenge ✗ "You're doing great, just tweak it" → Six months later, PIP is a shock → The kind person's biggest sin Radical Candor The target Care ✓   Challenge ✓ "I noticed X. Here's the impact." → 5 minutes of discomfort now → Three months later, growth Manipulative Insincerity The worst quadrant Care ✗   Challenge ✗ Backchannel, passive-aggressive email → Politics, trust destroyed → The toxic floor Obnoxious Aggression "Brutal honesty" Care ✗   Challenge ✓ "This analysis is garbage." → Short-term output, long-term attrition → Subtler toxicity than silence
Scene
Setup: Your senior engineer A presents a rushed design doc at a cross-team review. The logic skips around; the PM looks visibly lost. You walk back to your desks together after the meeting.
✗ Ruinous Empathy (the most common trap)

When the report says "Eh, that meeting was rough," don't say "Don't worry, the doc was thorough, the PM just didn't have the context." Because what they hear is "I'm fine," and two weeks later they ship another doc with the same flaw.

✗ Obnoxious Aggression

"Did you even read your own doc? It's a mess, the PM had no shot at following it." They remember your tone, not what to fix. Next round, they're more defensive, not less.

✓ Radical Candor

Open with real care (not flattery): "I know you were trying to ship launch and write the doc in the same week — the timing was brutal."

Then challenge plainly: "But honestly, the PM losing the thread wasn't on him. Section 2 jumped straight to the implementation without setting up the core conflict we're solving. I've seen the same pattern in your last three docs."

Give a concrete next move: "Next time, write the draft, sleep on it, and reread before sending — or ping me and I'll do a pass. This is a structure issue, not a wording one. Worth fixing."

Self-location checklist (do this weekly)
  • How many of my negative feedback moments in the past 7 days were delivered to the person's face (or video)?
  • Is there anything I've vented about in a Slack DM with a peer but haven't said directly to the person? (Manipulative Insincerity signal.)
  • Have I substituted "you're too X" personality labels for specific behavior descriptions? (Aggression signal.)
  • Have I confused "being kind" with "staying silent"? (Ruinous Empathy signal.)
  • Does this report actually believe I care about them? When did I last give them specific, concrete positive recognition?
Common pitfalls
  • Reading "Radical Candor" as "license to be blunt." Kim Scott has spent years correcting this — it's the most-abused part of her framework. Care Personally is the prerequisite, not the optional flavor.
  • Hiding behind "I'm critiquing the work, not you." That sentence is often Obnoxious Aggression in costume. The work and the person both need care.
  • Waiting until perf review to deliver negative feedback. That's not Radical Candor. That's delayed Manipulative Insincerity.
  • Thinking positive feedback doesn't need Radical Candor. Wrong. "You did a great job" is the positive flavor of Ruinous Empathy. "Here's the specific behavior you executed and the impact it had" is the real thing.
Women's perspective
Female Leader's Note Research (Stanford VMware Women's Leadership Lab and others) consistently shows that the same direct feedback, delivered by a woman, is more often labeled "too harsh" or "emotional." Classic double bind — too soft is dismissed, too direct is punished. Two counters: (1) Use SBI (next card) to reduce feedback to pure observable behavior, which is nearly impossible to dismiss as "emotional"; (2) Frame the feedback with care explicitly: "I'm telling you this because I want you to succeed here." Your male peers don't need to do this; you do. Acknowledge the unfairness, then play the move. Sheryl Sandberg walks through this exact arc in Lean In — from being labeled "too aggressive" to learning the upfront framing.
Key references
Kim Scott, Radical Candor (Ch. 1–2) — the original 2x2 and the famous Sandberg "um" story.
Sheryl Sandberg, Lean In (Ch. 4 "It's a Jungle Gym, Not a Ladder") — the particular bind women face when giving feedback.
Language to steal
Phrases worth keeping verbatim

"Care personally, challenge directly." — Kim Scott's mantra. Memorize it.

"I'm telling you this because I want you to win." — Upfront frame; activates trust in one sentence.

"That came across as obnoxious." — Kim Scott's word choice. More precise than "rude" — it names "thought you were being direct, but you were unbearable."

PRINCIPLE 02

SBI: Three Specifics Instead of "You're Too X" Situation · Behavior · Impact

CCL frameworkBehavior, not characterFeedback structure
One-line principle
Never give personality feedback ("you're too negative / too dominant / too passive"). Always give behavior feedback: in this specific situation (S), I observed this specific behavior (B), and here's the specific impact it had (I). All three required.
In the author's own words
"Effective feedback is specific, focuses on observable behavior, and describes impact rather than attributing motive or character." — Center for Creative Leadership, SBI Feedback Model
SBI in three parts
S Situation When & where Specific to a date, meeting, or thread "Yesterday's design review" B Behavior What a camera saw Actions or words — not motive, not character "You interrupted the PM 3 times" I Impact Real consequences On people / project / team — and on you "She told me afterward…"
Scene: translating personality verdict into SBI
Setup: You want to tell a report "you're too dominant — no one else gets a word in." Say that as-is, and they'll either deny or be wounded — with no path forward.
✗ Personality feedback (a closed door)

"You've been too dominant in meetings lately, no one else can speak. You need to learn to listen more."

Why it fails: "Dominant" is a verdict — they can just say "no I'm not." "Listen more" is vague — they don't know what to change.

✓ SBI translation

S: "Yesterday's 2pm sprint planning,"

B: "I tracked it — in 50 minutes, you spoke for about 25, Maria and Tom together less than 5. Maria tried to jump in three times and you kept the floor."

I: "End result, the two decisions in that meeting were basically yours alone. Maria told me in our 1:1 she didn't get to surface her alternative — and next week she'll probably stop preparing one."

Close by opening a dialogue (not issuing an order): "Does that match what you saw? How did the meeting look from your side?"

SBI prep checklist
  • Can I name the Situation down to a date / meeting / Slack thread? A vague "lately" is an SBI failure signal.
  • Is my Behavior something a camera could record? If I'm using words like "negative / aggressive / defensive," rewrite.
  • Is my Impact something that actually happened? Or am I worrying about something that might happen? Stick to what happened.
  • Have I smuggled in attribution? "You did this because you wanted to…" — that's mind-reading. Cut it.
  • Am I ready to leave the last word to them? SBI is not a verdict; it opens a conversation.
The SBI-Q variant: add "what was your intent?"
Many coaches add a Q after SBI: "what was your intent?" When your interpretation of motive is wrong, this question saves you from a false accusation. Example:

After delivering SBI: "That's the impact I observed. I want to understand — what were you trying to do when you cut Maria off?"

They might say: "Honestly, I thought she was stuck and I was trying to help her finish — but I see now that backfired." That's when you've got a real handle for behavior change.

Common pitfalls
  • S too wide. "Over the last few weeks…" — they can't locate it, so they reconstruct the most innocent version they remember and defend that.
  • B contains character. "You interrupted her, because you don't respect her" — you've fused observable behavior with motive interpretation.
  • I is prediction, not fact. "If you keep doing this, the team will fall apart" — that's a threat, not feedback. Stick to impact that has already happened.
  • SBI as a vehicle for venting. Wrapping "I'm pissed" in three-part structure isn't SBI; it's a dignified release of resentment. Cool down first.
Women's perspective
Female Leader's Note SBI has an underappreciated protective effect for women leaders. When you're accused of being "too emotional," SBI notes are your defense: dates, observable behaviors, observable impact — pure fact, zero personality verdict. It becomes very hard to dismiss as "she's being emotional." Recommendation: before any negative-feedback conversation, spend 60 seconds writing S / B / I in your notebook — not just for them, but as evidence-of-record for yourself. Lara Hogan in Resilient Management calls these "feedback receipts." Managing your feedback paper trail is managing your defensive position when you're attacked for caring enough to give feedback at all.
Key references
Center for Creative Leadership, Feedback That Works — the official SBI manual, used by 3,000+ organizations.
Douglas Stone & Sheila Heen, Thanks for the Feedback — the receiver-side complement, explains why SBI works.
Language to steal
Phrases worth keeping verbatim

"I want to share an observation, not a judgment." — Softer opener than "I want to give you feedback."

"What I saw was… What I noticed was…" — First-person framing; avoids the "objective truth" tone.

"The impact on me / on the team was…" — Use "impact" instead of "made me feel." More professional, equally honest.

PRINCIPLE 03

Now vs. Later: Treat Feedback Timing as a Design Choice Real-Time, Same-Day, or Scheduled?

TimingDesign choiceCool-down
One-line principle
"Give feedback ASAP" is the simplified version. The accurate version: default to 24 hours, but make a deliberate choice based on three variables — your emotional temperature, the receiver's capacity to absorb, and the stakes. The wrong timing turns the right content into poison.
In the author's own words
"Feedback is best delivered as close to the event as possible, but never when you're angry. If you can't deliver it within a week, you've waited too long; if you deliver it in the heat of the moment, you've waited too little." — adapted from Marshall Goldsmith, What Got You Here Won't Get You There
Timing decision matrix
Stakes / severity → Your emotional temperature ↓ Calm + low stakes → Immediate / same day Small nit, mention on the walk back "Slide 3 could be clearer next time." Faster = more natural Calm + high stakes → Scheduled meeting, 24–48 hrs Affects perf / relationship / major miss Not hallway-casual, but don't wait until next 1:1 Heated + low stakes → Sleep on it, then decide They tripped your trigger, but didn't actually do anything wrong 70% of the time you won't deliver it Heated + high stakes → 12–24 hr cool-down, then schedule Most dangerous quadrant Now = blowup, too late = ambush
Scene
Setup: Monday afternoon all-hands. Your report B cites an inaccurate number in front of a customer, who calls it out on the spot. You're so angry after the meeting you can't form a sentence.
✗ Letting it rip immediately

"Where did you get that number? Did you not realize the customer would check? You just torched the project's credibility!"

At emotional temperature 9/10, they'll remember your face, not your words. Even if every word is correct, their defense system is up.

✗ Waiting until next perf review

"Oh, also, that customer meeting three months ago…" — they've either forgotten, or it lands as ambush.

✓ The 12–24-hour designed version

Right after the meeting: Say only one neutral thing: "Thanks everyone. Let's debrief tomorrow morning." Don't make decisions at temperature 9.

That night, alone: Write SBI in three lines. If possible, have a partner or trusted peer sanity-check the language.

Next morning, send the calendar invite: "Want to spend 30 minutes debriefing yesterday's customer meeting — 11am OK?" Telegraphed, not ambushed.

Open the meeting: "Let me name something first — I had a strong reaction in the room yesterday. That's why I chose to wait a day rather than say something then. The actual feedback is about the data source. Let's start with how you sourced the number…" Naming your cool-down explicitly is modeling how you want the team to handle high-stakes moments.

"Now vs. later" checklist
  • What's my emotional temperature, 1–10? Above 6 — do not deliver now.
  • What are the stakes? Affects a single demo (low) vs. perf review / team trust (high)?
  • What's their capacity right now? Just got chewed out, exhausted, sick — capacity is 0.
  • If I wait 24 hours, will I still want to give this feedback? (If not, it shouldn't be given at all.)
  • Will waiting for the next 1:1 (maybe 5 days away) make it an ambush? If yes, book a 30-minute slot now.
Common pitfalls
  • "When I'm calm, I just won't give it." That's not calm — that's Ruinous Empathy. Calm + silent ≠ healthy.
  • Reading "immediate" as "in front of others." Negative feedback delivered in front of a third party, no matter how gently, is public humiliation. Praise in public, criticize in private.
  • Long Slack message in the heat of the moment. No tone, no eyes, no pauses. Your "urgency" reads as "anger." (More in Card 4.)
  • Always waiting for the next 1:1. Unless your next 1:1 is within 48 hours, that's too late. Book a dedicated slot.
Women's perspective
Female Leader's Note "Emotional" is the most weaponized label against women leaders. But suppressing all feeling makes you read as cold, which is worse. The middle path: acknowledge the feeling, separate it from the content. "I noticed I had a strong reaction yesterday — that's information, not the message. The actual feedback is…" You're naming the emotion as data, not venting or burying it. As a bonus, you're modeling for your male reports that emotional intelligence is not weakness. Brené Brown calls this "rumbling with vulnerability" in Dare to Lead — putting the emotion on the table is the strong move, not the soft one.
Key references
Marshall Goldsmith, What Got You Here Won't Get You There — the "Feedforward" concept and counterintuitive insights about feedback timing.
Brené Brown, Dare to Lead — "Rumbling with vulnerability": emotion as a leadership tool, not a liability.
Language to steal
Phrases worth keeping verbatim

"Let me sleep on it and follow up tomorrow." — The graceful 24-hour buffer.

"I'd like to debrief tomorrow morning — 11am OK?" — "Debrief" is neutral. No judgment in the word.

"Praise in public, criticize in private." — Never wrong. Memorize.

PRINCIPLE 04

Written vs. Spoken: The Channel Is Part of the Message The Channel Is The Message

ChannelSlack vs in-personWritten follow-up
One-line principle
The channel isn't a neutral container. The same sentence in Slack, email, a 1:1, or a doc gets decoded completely differently. Default rules: negative feedback face-to-face or video; positive feedback as public as possible; high-stakes feedback needs a written follow-up for the paper trail. Three rules, no exceptions.
In the author's own words
"Written feedback feels harsher than spoken; spoken feedback feels harsher than the same words shared in a context of evident care. Choose your medium with the same care you choose your words." — Lara Hogan, Resilient Management
Channel decision table
Feedback type Default channel Paper trail Never Positive · small Public Slack channel / DM only Positive · big All-hands / skip-level mention In perf doc Only privately Negative · small 1:1, spoken One line in 1:1 doc Slack DM Negative · big Dedicated meeting (in-person/video) Recap email after DM / email first PIP / warning In-person + HR present Formal document Any informal channel Sensitive relationship Video 1:1 (not in-person) None yet (avoid premature record) Slack thread Code / doc PR review / doc comments Async = paper trail Re-litigated in 1:1
Scene
Setup: Senior engineer C and junior engineer D have a 30-comment back-and-forth on a PR. C's tone is getting colder. D DMs you on Slack: "Does C hate me?"
✗ Slacking C the feedback

"Hey C — D mentioned your tone on his PR was a bit… can you watch it?"

Problems: (1) You're giving negative feedback over Slack — wrong default. (2) You're quoting D's private DM — D's trust just broke. (3) "Watch it" is vague — C has no idea what to change. (4) Text has no tone — C might read this as you talking behind their back.

✓ Layered by channel

To D (Slack DM is fine): "I see it. I'll go look at the PR comments myself and decide how to handle it — your name won't come up. You focus on the PR. We'll talk more in our next 1:1."

To C (dedicated 1:1, video, 30 minutes): Don't drop it on Slack. Schedule it: "Want to spend 30 min on mentorship next session — tomorrow 2pm?"

In the meeting (spoken SBI): "I went and read PR #847. In comments 23–29 you wrote 'this is not how we do it,' 'you should know better.' Those are behaviors — I don't need you to explain the motive. Impact: I observed D spent three days iterating, and in the end he just pasted in your version. He didn't learn anything, you spent the time anyway — both lose."

After the meeting (one line in 1:1 doc): "2026-05-29 — discussed PR review tone with juniors. Agreed to pair on one review next month." Paper trail without ambush.

Channel discipline checklist
  • If this Slack message were screenshotted six months from now, would I be comfortable? (If not, don't send it.)
  • Am I using Slack as a way to "go faster," when the real reason is avoidance? (Speed is usually avoidance.)
  • Have I delivered positive feedback publicly? Private-only positive feedback has half the impact.
  • For high-stakes negative feedback — did I write a one-line recap in the 1:1 doc afterward?
  • For PIP / warning-level feedback — is HR in the room and is there a formal document? If not, don't start the conversation.
Common pitfalls
  • Long Slack message for negative feedback. No tone, no eyes, no pauses. They'll reread it five times, each pass worse than the last.
  • Positive feedback that lives only in your head. "They know I appreciate them" — they don't. Say it. Write it. Mention it publicly.
  • High-stakes feedback with no written follow-up. Three months later they say "you never told me." A single line in 1:1 doc would have saved you.
  • Written substitution for in-person. Using a long email as a shield against the hard conversation. They'll feel even worse — you didn't show up.
  • Citing one person's private complaint as another's feedback source. Quoting D when giving C feedback — D will never tell you anything again.
Women's perspective
Female Leader's Note There's a counterintuitive channel trap for women leaders: written feedback is safer for you, and also more easily weaponized against you. A professionally written negative-feedback email can be screenshotted three months later and sent to HR / a skip-level, framed as "she has a pattern of being critical." Your male peers, saying the same things verbally in a hallway, leave no record to be weaponized. Two counters: (1) For important negative feedback, deliver it verbally, then you write the neutral recap in 1:1 doc — you define the record, rather than letting the other party define it for you; (2) Never send written feedback at temperature 5+. Anne-Marie Slaughter in Unfinished Business describes always waiting overnight before sending. That isn't weakness — it's navigating the double bind as craft.
Key references
Lara Hogan, Resilient Management — "Feedback Equation" and chapters on channel selection.
Patrick Lencioni, The Five Dysfunctions of a Team — Trust and Conflict chapters; why the channel determines the quality of team conflict.
Language to steal
Phrases worth keeping verbatim

"Let's jump on a quick video call." — More concrete than "let's talk." Stops Slack drift.

"I'd rather say this in person than write it." — Naming your channel choice signals care.

"Just to recap what we discussed:" — The opening for a written follow-up. Creates a record without being cold.

"Public praise, private critique." — Four-word rule.

This Week's Practice · Your Day 2 Action

One concrete action this week — not reflection, not reading:

Pick the report you've swallowed feedback for in the last 30 days — the one who pulled you into Ruinous Empathy.

(1) By Tuesday, write SBI in three lines (for you, not them yet): specific situation, specific behavior, specific impact.
(2) Use Card 3's timing matrix: what's your temperature, what are the stakes? Decide: within 24 hours, or later this week?
(3) Pick the channel from Card 4: default to in-person or video, not a long Slack message.
(4) The night after, write two lines of recap in 1:1 doc: what you said, what they responded.

Look back next Monday. If you delivered zero feedback this week, it wasn't because you were busy. Ruinous Empathy was protecting your comfort — at the price of another week of them on the wrong path.