Radical Candor
by Kim Malone Scott
A genuinely useful 2x2 buried in a long book — care personally, challenge directly.
- Status
- Read · May 2026
- Bought
- May 22, 2026
- For
- New and second-time engineering managers · Tech leads who avoid hard conversations · Anyone whose feedback lands as either vague or cruel
Where it earned its place
The one-paragraph verdict
The core is a 2x2: caring about someone and being blunt with them are not opposites, and dropping either one gives you a named failure mode — ruinous empathy, obnoxious aggression, or the worst, manipulative insincerity. That vocabulary alone changed how I run one-on-ones. Where it earns the lower public rating is padding: it’s a long book for one idea, heavy on Apple-and-Google war stories that don’t always travel, and the brand has been widely misread as permission to be harsh while quietly skipping the “care” half. Scott knows this and spends real pages pushing back, but the dilution is real.
Who should read it
Read it if you’re a new or second-time manager, or a tech lead who keeps swallowing feedback to avoid an awkward afternoon. The framework gives you words for what you’re already doing wrong. Skip it if you already give direct feedback inside trusting relationships — you’ll recognize everything and resent the page count.
Where it earned its place
The “challenge directly” half is exactly what makes building a low-drama engineering team possible — drama comes from problems left unsaid, not from saying them. And the care/challenge balance is the backbone of no news is good news: you only earn that kind of trust by being someone who’d tell people the truth if it weren’t.
Skip it if…
Skip it if you want a tight treatment of the idea — this isn’t it. The signal-to-page ratio is poor, and a sharp blog summary covers eighty percent of the value in ten minutes.