radical-candor
Radical Candor
What It Is
Radical Candor is a framework for giving feedback that builds trust and drives results. The core insight: great feedback happens when you Care Personally AND Challenge Directly at the same time.
Most people fail at feedback because they choose one or the other. They're either so focused on being nice that they don't say what needs to be said (ruinous empathy), or they're so focused on being direct that they forget to show they care (obnoxious aggression). Radical Candor isn't about finding a middle ground—it's about doing both fully.
The key shift: Move from "How do I deliver this feedback?" to "How do I help this person succeed?"
When to Use It
Use Radical Candor when you need to:
- Give feedback (both praise and criticism) that actually lands
- Have difficult performance conversations with direct reports
- Build a culture of honest communication on your team
- Solicit feedback from others about your own performance
- Coach employees through growth and development
- Address problems before they become crises
- Build trust in professional relationships
When Not to Use It
- When you don't actually care — if you just want to vent or hurt someone, that's obnoxious aggression with extra steps
- When the feedback is about unchangeable personal traits — focus on behavior, not personality
- When you haven't solicited feedback first — always start by asking for feedback before giving it
- When you're saving it for a performance review — Radical Candor happens in the moment, not quarterly
- When you haven't built any relationship — you need some foundation of care before challenging directly
Patterns
Detailed examples showing how to apply Radical Candor correctly. Each pattern shows a common mistake and the correct approach.
Critical (get these wrong and you've wasted your time)
| Pattern | What It Teaches |
|---|---|
| ruinous-empathy | Being "nice" by withholding feedback isn't kind—it's harmful |
| obnoxious-aggression | Challenging without caring puts people in fight-or-flight |
| manipulative-insincerity | Saying what people want to hear destroys trust |
| soliciting-before-giving | Always ask for feedback before you give it |
High Impact
| Pattern | What It Teaches |
|---|---|
| feedback-sandwich | The praise-criticism-praise pattern backfires |
| vague-praise | "Great job!" teaches nothing—use CORE instead |
| feedback-via-text | Slack and email are feedback train wrecks waiting to happen |
| waiting-for-better-moment | If you're waiting for the right time, you're never going to say it |
| asking-why | "Why did you do that?" triggers defensiveness—ask about what happened instead |
| personality-not-behavior | "You're disorganized" vs "The report was missing three sections" |
| accepting-no-answer | Never accept "everything's fine" when soliciting feedback |
Medium Impact
| Pattern | What It Teaches |
|---|---|
| gauging-how-it-lands | Watch for sad or mad—then adjust, don't retreat |
| public-criticism | Praise in public, criticize in private |
| people-pleasing-trap | Your job is to care, not to be liked |
Deep Dives
Read only when you need extra detail.
references/radical-candor-playbook.md: Expanded framework detail, checklists, and examples.
Resources
Books:
- Radical Candor by Kim Scott — the complete framework
- Radical Respect by Kim Scott — the prequel on building respectful workplaces
- When They Win, You Win by Russ Laraway — deep dive on career conversations
Other:
- radicalcandor.com — tools, workshops, and additional resources
- The Radical Candor podcast — ongoing examples and coaching
More from wdavidturner/product-skills
strategic-narrative
Use when asked to "strategic narrative", "Andy Raskin", "tell our company story", "write a pitch deck", "explain why customers should care", or "movement narrative". Helps craft compelling narratives that define movements rather than just selling products. The Strategic Narrative framework (created by Andy Raskin) transforms pitches from feature lists into stories about change.
32thinking-in-bets
Use when asked to "thinking in bets", "make decisions under uncertainty", "think probabilistically", "avoid resulting", "separate decision quality from outcomes", or "reduce bias in decisions". Helps make explicit bets and evaluate decisions on process, not results. The Thinking in Bets framework (from Annie Duke) applies poker strategy to business and life decisions.
30okrs
Use when asked to "set OKRs", "objectives and key results", "quarterly OKR planning", "align objectives", "measure OKR progress", or "focus priorities with OKRs". Helps teams focus on what matters most and create a cadence of progress. The OKR framework (originated by Andy Grove at Intel, popularized by John Doerr at Google) creates alignment, focus, and learning cycles. Christina Wodtke's Radical Focus approach emphasizes simplicity and avoiding common pitfalls.
29design-sprint
Use when asked to "run a design sprint", "5-day sprint", "prototype in a week", "test ideas before building", or "Jake Knapp sprint". Helps teams go from problem to tested prototype in five days. The Design Sprint framework (created by Jake Knapp at Google Ventures) compresses months of work into one focused week.
24hierarchy-of-engagement
Use when asked to "define our core action", "North Star metric", "accruing benefits", "improve retention mechanics", "hierarchy of engagement", or "Sarah Tavel framework". Helps consumer products identify the actions and benefits that drive long-term retention. The Hierarchy of Engagement framework (created by Sarah Tavel at Benchmark) maps progression from core action to mounting loss.
24hooked-model
Use when asked to "build habit-forming products", "Hooked model", "trigger action reward investment", "create sticky behavior loops", or "design habit loops". Helps design products that form unprompted user habits. The Hooked Model (created by Nir Eyal) explains how products create habits through Trigger, Action, Variable Reward, and Investment.
21