Radical Candor

Contents

• Part 01 · A New Management Philosophy
  01Build Radically Candid Relationships
  02Get, Give, and Encourage Guidance
  03Understand What Motivates Each Person on Your Team
  04Drive Results Collaboratively
• Part 02 · Tools & Techniques
  05Relationships
  06Guidance
  07Team
  08Results

Build Radically Candid Relationships

Radical Candor lives at the intersection of two independent axes: Care Personally and Challenge Directly. The three other quadrants name the failure modes managers fall into when one or both dimensions is missing. You must earn the right to challenge by first proving you care.

Care Personally

The vertical axis. "Give a damn." Bring your whole self to work, acknowledge employees as full human beings with lives outside the office, share more than just your professional self. This is not about being friends — it is about basic human regard. Without it, criticism lands as an attack.

Challenge Directly

The horizontal axis. Tell people clearly and promptly when something isn't good enough — and be equally willing to hear it back. Challenging directly shows you care enough to engage seriously with someone's work. Silence is not kindness.

Radical Candor

The upper-right quadrant: high care + high challenge. Criticism and praise are both specific, sincere, and aimed at helping the person grow. Radical Candor is not brutal honesty — the word "radical" describes the cultural courage required, not the harshness of the delivery.

Obnoxious Aggression

The lower-right quadrant. You challenge directly but fail to show you care. Belittling, public embarrassment, "front-stabbing." Scott calls this the second-best quadrant — at least the person receives honest information they can act on, unlike the silent quadrants on the left.

Ruinous Empathy

The upper-left quadrant and the most common trap for "nice" managers. You care, but you won't challenge — withholding criticism to spare short-term feelings, allowing problems to fester, giving praise that isn't earned. The most insidious quadrant because it feels virtuous while quietly damaging careers.

Manipulative Insincerity

The lower-left quadrant: neither care nor challenge. Passive-aggression, backstabbing, political maneuvering, insincere flattery. Usually arises from self-protection or laziness — when you can't be bothered to care and can't be bothered to be honest.

Plot Behaviors, Not People

The 2x2 plots specific interactions, not personality labels. The same manager can land in different quadrants in different conversations. The framework is a coaching tool for individual moments, not a typology of human beings.

Care Personally

Genuine human regard for employees as whole people, not just functions.

Challenge Directly

Saying what you actually think, kindly and clearly.

Radical Candor

The upper-right quadrant; care and challenge combined.

Obnoxious Aggression

Challenge without care — brutal honesty, front-stabbing.

Manipulative Insincerity

Neither care nor challenge — political behavior, backstabbing.

Ruinous Empathy

Care without challenge — "nice" silence that harms long-term.

Front-stabbing

Scott's term for direct but uncaring criticism, contrasted with backstabbing.

Bring Your Whole Self to Work

The cultural condition that makes Radical Candor possible.

Multiple choice

A manager consistently tells reports their work is fine when it isn't, because she doesn't want to hurt their feelings. Over time her best report is passed over for promotion and is shocked to learn his work was below bar. Which quadrant is the manager in?

• ARuinous Empathy
• BObnoxious Aggression
• CManipulative Insincerity
• DRadical Candor (since she's protecting the relationship)

True / False

"Radical" in Radical Candor refers to delivering criticism with brutal, unsoftened harshness.

• TrueTrue
• FalseFalse

Spot the issue

In a status meeting, a director mocks an engineer's design in front of the whole team, getting laughs at the engineer's expense. The director later says, "At least I was honest — that's Radical Candor." What's actually going on?

• AThis is Radical Candor; honesty publicly delivered is the point.
• BThis is Manipulative Insincerity because the director used humor.
• CThis is Obnoxious Aggression — direct challenge with no demonstration of care, plus public humiliation.
• DThis is Ruinous Empathy because the engineer's feelings were spared by the laughter.

Multiple choice

Two managers attend the same workshop on the Radical Candor 2x2. Manager X says, "I'm finally going to label each of my reports by their quadrant." What's the correct way to apply the framework?

• ALabel each report by their dominant quadrant so 1:1s can be tailored to personality.
• BUse the quadrants to rank managers only, never individual contributors.
• CSkip the 2x2 for direct reports — it's a tool meant for peer feedback.
• DPlot specific interactions and behaviors, since the same person can land in different quadrants across conversations.

Get, Give, and Encourage Guidance

Guidance — Scott's umbrella term for praise and criticism — flows in a specific order: get it on yourself first, give it second, encourage it among the team third. Most managers under-invest in praise and over-personalize criticism; the HHIPP rules and a rehearsed go-to question fix both.

Get Guidance First

Solicit criticism from your team before offering yours. Ask a rehearsed go-to question like "What could I do or stop doing that would make it easier to work with me?" Then embrace the discomfort, listen, and reward the candor by acting on what you hear. Asking is performative; acting is what earns standing.

Embrace the Discomfort

After you ask for criticism, sit in the silence. Count to six. People need time to gather courage to say a hard thing; if you fill the silence to rescue them, you'll never hear the truth. The awkward pause is the price of admission.

HHIPP Guidance

Good guidance is Humble, Helpful, Immediate, delivered In Person, and follows Praise-in-public / criticize-in-private — and it does not Personalize. Critique the work and the behavior, never the character. This is the integrity check for any specific piece of feedback.

Praise Matters as Much as Criticism

Most managers under-invest in praise. Praise must be just as specific, sincere, and substantive as criticism — vague "great job!" drifts into Ruinous Empathy. Scott warns against prescribed praise-to-criticism ratios; sincerity beats arithmetic.

Impromptu Guidance

The atomic unit of Radical Candor is the two-to-three-minute conversation between meetings, not the scheduled review. Guidance has a short half-life — deliver it while the incident is fresh. Formal performance reviews should contain zero surprises.

Don't Personalize

Criticize the behavior or the work product, never the person. "Your slides were confusing" is fair; "you're a confusing person" is not. The fundamental attribution error — explaining others' behavior by personality rather than situation — is both usually wrong and renders the problem unsolvable.

Encourage Guidance Among Peers

Stamp out gossip by refusing to be a triangulating middleman. When person A complains about person B, send them to talk directly and follow up. The manager's job is to be the catalyst for candor between others, not its courier.

Guidance

Scott's umbrella term encompassing both praise and criticism.

HHIPP

Humble, Helpful, Immediate, In Person, Praise-public/criticize-private, not Personality.

Go-to Question

A pre-prepared question for soliciting criticism on yourself.

Impromptu Guidance

Short, in-the-moment 2-3 minute feedback delivered while it's fresh.

Embrace the Discomfort

Tolerating awkward silence after asking for criticism so the other person answers honestly.

Triangulation

Talking about someone instead of to them; the manager redirects it.

Situation–Behavior–Impact (SBI)

A template for humble criticism — describe the situation, behavior, and impact.

Fundamental Attribution Error

Explaining others' behavior by personality while explaining your own by situation.

Multiple choice

A new VP wants to install a culture of candor on her team. According to Scott's order of operations for guidance, what should she do first?

• AGive each report at least one piece of tough criticism in week one.
• BSolicit criticism of herself and visibly act on what she hears.
• CPair reports up and ask them to critique each other in 1:1s.
• DSchedule a workshop on the HHIPP framework.

Spot the issue

A manager asks his report, "Is there anything I could do or stop doing that would make it easier to work with me?" The report hesitates for three seconds. The manager jumps in: "No? Cool, didn't think so — anyway, about the deck..." What did the manager get wrong?

• AHe used the wrong go-to question; it should be about strengths, not friction.
• BHe should have asked the question over email instead, to give time to think.
• CHe failed to embrace the discomfort and sit in silence long enough for honesty to surface.
• DHe shouldn't ask the question at all until trust is established over months.

Multiple choice

An engineer ships a confusing design doc. Which of the following pieces of feedback best matches the HHIPP rules?

• AIn a 1:1 the next day: "Yesterday's design doc lost me at the data-flow section — can we walk through it so I can give you specifics?"
• BIn a team Slack channel: "This doc is confusing — you tend to be a confusing writer."
• CThree weeks later in the annual review: "Back in April your doc wasn't clear."
• DVia email that evening: "FYI your doc was hard to follow. No need to discuss."

True / False

Scott recommends managers maintain a roughly 5:1 ratio of praise to criticism to keep teams motivated.

• TrueTrue
• FalseFalse

Understand What Motivates Each Person on Your Team

Great teams are not built by hiring only "A-players" but by understanding each person's growth trajectory and managing accordingly. Rock star and superstar describe where a person is right now, not a permanent verdict. Russ Laraway's three career conversations are the primary tool for learning what drives each person.

Growth Trajectory, Not Talent Ranking

Every team needs a mix of people on different trajectories. Rock star and superstar are descriptions of current ambition, not quality — both are top performers. The old "performance vs. potential" grid wrongly implies rock stars are inferior; trajectory replaces potential.

Rock Stars

Excellent at what they do and deeply content in their current role. The Rock of Gibraltar of the team: stable, expert, reliable. Promoting them out of the role they love is a mistake (the Peter Principle). Reward them with awards, recognition, and pay — not forced upward movement.

Superstars

Hungry for new challenges and rapid advancement. They get bored fast, drive change, and need a constant stream of stretch opportunities. They are the engine of team growth — and a flight risk if under-challenged.

Trajectories Change

A person can be a superstar in one season of life and a rock star in another — after having a child, after a move, after a hard project. Treat the trajectory as fluid, not a permanent label. The annual Growth Management Plan re-evaluates each report's current trajectory.

Career Conversations

Russ Laraway's three 45-minute conversations with each direct report: (1) Life Story — trace transitions from kindergarten forward to surface values; (2) Dreams — identify 3-5 pinnacle visions, not one rigid plan; (3) 18-Month Plan — concrete skills, projects, and mentors connecting today's work to at least one dream.

Avoid the Promotion-Equals-Success Trap

A meritocracy that only rewards ambition demoralizes rock stars. Recognize and pay for excellence-in-role, not just upward movement. Otherwise you train every report to either chase promotions they don't want or quietly disengage.

Cohesive Team Failure Modes

Two opposite failures break a team: burnout from over-stretching rock stars who don't want the stretch, and boredom from under-challenging superstars who need the stretch. The cohesive team puts each person in motion at the slope they actually want.

Rock Star

A top performer on a gradual growth trajectory; excellent and content in the current role.

Superstar

A top performer on a steep growth trajectory; ambitious and change-oriented.

Growth Trajectory

The slope at which a person currently wants to grow; changes over time.

Life Story Conversation

The first career conversation, uncovering motivations through personal history.

Dreams Conversation

The second career conversation, identifying multiple aspirational endpoints.

18-Month Plan

The third career conversation — a concrete skill-and-project plan.

Stretch Assignment

A project deliberately beyond current ability, used to feed superstars.

Peter Principle

The risk of promoting a star into a role where they fail; the trap for unwanted promotions.

Multiple choice

According to Scott, what is the key distinction between a rock star and a superstar?

• ARock stars are mediocre performers while superstars are top performers.
• BRock stars work harder while superstars are more talented.
• CBoth are top performers; they differ in their current growth trajectory and appetite for change.
• DSuperstars deserve raises while rock stars deserve only verbal recognition.

Spot the issue

Priya has been an outstanding senior designer for four years. She tells her manager she loves her current role and has no interest in becoming a design lead. Her manager, eager to "develop" her, signs her up for a management bootcamp and starts handing her a lead's responsibilities. Within six months she's burned out and considering leaving the company. What's the issue?

• APriya wasn't ready for the workload yet — she should have been promoted more gradually.
• BThe manager pushed a rock star onto a superstar trajectory she didn't want, treating promotion as the only form of reward.
• CThe manager should have offered her a raise before the management bootcamp.
• DPriya should have been more enthusiastic about the growth opportunity.

True / False

Once someone is labeled a rock star, you should expect them to remain on a gradual growth trajectory for the rest of their career.

• TrueTrue
• FalseFalse

Multiple choice

What is the correct sequence of Russ Laraway's three career conversations?

• A18-Month Plan, then Dreams, then Life Story.
• BDreams, then Life Story, then 18-Month Plan.
• CLife Story, then 18-Month Plan, then Dreams.
• DLife Story, then Dreams, then 18-Month Plan.

Drive Results Collaboratively

The boss's third job is execution. The Get Stuff Done (GSD) Wheel is a seven-step cycle for collaborative decision-making that prevents both the dictator trap (deciding alone, then enforcing) and the consensus trap (debating forever). Move through every step without skipping any and without getting stuck on any.

The GSD Wheel

Seven sequential steps the team cycles through repeatedly: Listen → Clarify → Debate → Decide → Persuade → Execute → Learn, then back to Listen. Each step is necessary; the wheel's discipline is to keep moving and to keep the boss's ego out of every step.

Listen

Quiet listening (introverted style: stay silent, give the room space) and loud listening (extroverted style: state a provocative opinion to draw out dissent) are both valid. The boss's job is to create space for the *other* style — whichever one is not their default.

Clarify

New ideas are fragile and need protection before debate. The manager's job is to help the originator sharpen the idea before it goes to broader criticism. Pixar's "plussing" — building on an idea ("yes, and...") rather than killing it — is the canonical technique.

Debate

Focus the team on the idea, not the ego. Assign devil's advocates, depersonalize disagreement, and don't let the highest-paid opinion win by default. McKinsey's "obligation to dissent" rule: silent consensus is a red flag — someone *must* argue the counter-position.

Decide

A specific person — the decider — owns each decision. The decider should "get into the weeds" with the people closest to the facts rather than relying on filtered conclusions. Push decisions toward expertise, not hierarchy. Keep Debate and Decide as separate steps so debate isn't warped by who holds authority.

Persuade

Once decided, the decider must bring along everyone who wasn't in the room. Logic alone fails. Use Aristotle's three modes together: ethos (credibility), pathos (emotion — connect to what people care about), logos (logic). Skipping Persuade produces malicious compliance.

Execute and Learn

Execute: remove obstacles, minimize the collaboration tax, keep dirt under your fingernails. Learn: capture lessons honestly, including mistakes. Two enemies of learning are the pressure to be consistent (sunk-cost stubbornness) and the pressure to deliver results that punishes course-correction.

Don't Skip, Don't Get Stuck

The two failure modes of the wheel. Skipping debate produces bad decisions; getting stuck in debate produces no decisions. The wheel is a discipline, not a checklist — every cycle should move all seven steps forward.

GSD Wheel

Get Stuff Done Wheel — the seven-step collaborative execution cycle.

Plussing

The Pixar-borrowed clarification technique of building on an idea rather than rejecting it.

Obligation to Dissent

A McKinsey norm requiring someone to argue the opposing view.

The Decider

The named person accountable for a given decision after debate.

Quiet Listening / Loud Listening

Two valid managerial listening styles (introverted vs. extroverted).

Ethos / Pathos / Logos

Aristotle's three persuasion modes — credibility, emotion, logic.

Malicious Compliance

What happens when Persuade is skipped — people execute while wanting the plan to fail.

Collaboration Tax

The cost of group work when it drags; the wheel's discipline minimizes it.

Multiple choice

What is the correct order of the seven steps in the GSD Wheel?

• AListen, Clarify, Debate, Decide, Persuade, Execute, Learn.
• BListen, Debate, Clarify, Decide, Execute, Persuade, Learn.
• CClarify, Listen, Decide, Debate, Persuade, Learn, Execute.
• DDecide, Persuade, Listen, Clarify, Debate, Execute, Learn.

Spot the issue

A VP debates a strategy change in a small leadership meeting, names herself the decider, and announces the new direction in a one-line email to the org. Three months later, mid-level teams are working hard but quietly subverting the plan — re-prioritizing their own backlogs, slow-walking handoffs, complaining in side channels. What step of the GSD Wheel did she skip?

• ADebate — she should have re-opened the discussion before announcing.
• BClarify — the original idea wasn't sharpened enough before debate.
• CPersuade — she never brought along everyone who wasn't in the room, producing malicious compliance.
• DLearn — she should have run a retrospective immediately after the decision.

Spot the issue

An engineering lead floats a half-formed idea about restructuring on-call. Before he can finish the sentence, three senior engineers pile on with reasons it won't work, citing past failures and edge cases. The idea dies; later, two of the critics admit the underlying instinct was actually correct. What's the issue?

• AThe lead should have argued harder for his idea against the criticism.
• BThe team skipped Clarify and went straight to Debate, killing a fragile new idea before it could be sharpened.
• CThe senior engineers were obnoxiously aggressive and need a feedback session.
• DThe team should have voted on the idea before debating.

Multiple choice

Why does Scott insist on keeping Debate and Decide as separate, named steps?

• ABecause debate is for engineers and decisions are for managers.
• BSo the team can vote on each decision after debating it.
• CTo make meetings shorter by limiting debate to a fixed time-box.
• DSo debate isn't warped by who holds authority — the decider can engage the facts rather than have hierarchy short-circuit the argument.

Relationships

Trusting relationships are the bedrock that makes Radical Candor possible, and those relationships start with the manager taking care of themselves. The chapter unpacks practices for staying centered, sharing context about your own emotional state, integrating work and life, and respecting boundaries — all in service of creating bandwidth for candor.

You Can't Give a Damn About Others if You Don't Give a Damn About Yourself

The chapter's thesis. Self-care is not separate from management — it's a prerequisite for the emotional bandwidth required to care personally about others. Depleted managers cannot offer real attention to anyone.

Stay Centered

Identify the specific practices that keep you grounded (Scott's recipe: 8 hours of sleep, 45 minutes of exercise, family time, meals together). These matter more when you're busy, not less. Put them on the calendar like meetings you would never skip.

Work–Life Integration

Scott rejects "work-life balance" because it implies a zero-sum tradeoff. Integration means bringing your whole self to both spheres and letting the mix shift week to week. Some weeks tilt toward work, others toward life; both are fine.

Share Your Stories of Stress

When you're having a rough day, name it for your team. If you don't, they will assume your bad mood is about *them* and their work — and that projection corrodes trust. Honest context-sharing diffuses the misread.

Manage Your Reactions, Not Their Emotions

You can't (and shouldn't try to) control what other people feel. Your job is to master your reaction. Practical tactics: keep tissues within reach, offer water, take a walk outside, give the person time to compose. Don't talk them out of feelings.

Relationships Don't Scale, But Culture Does

A manager cannot have a deep individual relationship with hundreds of people. But the quality of the relationships you do have sets the cultural tone that ripples outward — your direct reports replicate your patterns with theirs.

Respect Boundaries

Not everyone wants to socialize the same way; not everyone shares your worldview. Don't mandate after-hours bonding, physical contact, or values conformity. Make space for difference; coerced intimacy isn't intimacy.

Stay Centered

The daily practice of maintaining physical and emotional equilibrium for good judgment.

Recipe

The personal set of practices (sleep, exercise, food, relationships) each individual needs to be at their best.

Stories of Stress

Honest, in-the-moment context-sharing so colleagues don't misread your mood.

Work–Life Integration

Bringing one whole self to both spheres rather than dividing finite hours.

Give a Damn

Scott's plain-language stand-in for "care personally"; applies to self-care and other-care.

Boundary Respect

Recognizing variance in comfort with touch, socializing, disclosure, and ideology.

Trust

The relational asset Chapter 5 builds — the thing that lets later candor land as a gift.

Cultural Tone

The downstream effect of a manager's relationship patterns on their reports' behavior.

Multiple choice

A director with three weeks of back-to-back launches stops exercising, skips meals at her desk, and starts sleeping five hours a night "until things calm down." According to Chapter 5, what's wrong with this approach?

• AShe should switch to "work-life balance" thinking and cut work hours by half until the launch ends.
• BSelf-care practices matter more during crunch periods, not less; the recipe goes on the calendar like an unmissable meeting.
• CThree weeks is fine — sustainable for a short sprint, only multi-month neglect erodes judgment.
• DShe should delegate the launch entirely to avoid burnout instead of adjusting her routine.

Spot the issue

A manager comes into the office Monday tense after a difficult weekend with a sick parent. He says nothing about it and runs a clipped, irritable staff meeting. By Wednesday, two reports are quietly updating their resumes because they're convinced he's furious with their work. What's the issue?

• AHe should have cancelled the staff meeting entirely until his mood improved.
• BHe should have stopped feeling the stress before walking into the office, since managers must control their emotions.
• CHe failed to share a story of stress, so the team filled the silence by assuming his mood was about them.
• DHe should have asked his reports for criticism on the spot to defuse the tension.

True / False

"Work-life balance" is Scott's preferred framing because it treats work and life as a zero-sum tradeoff that managers must carefully budget.

• TrueTrue
• FalseFalse

Multiple choice

A new VP mandates a Friday-night team dinner with mandatory toasts about "what your teammates mean to you," and is puzzled when one report keeps declining. What Chapter 5 principle is the VP violating?

• ARelationships don't scale — group dinners don't work past a certain headcount.
• BStay centered — Friday nights should be reserved for the manager's own recipe.
• CManage your reactions — the VP is reacting emotionally to the declined invitations.
• DRespect boundaries — coerced intimacy isn't intimacy; people vary in how they want to socialize.

Guidance

The operational core of the book: it translates Radical Candor from a 2x2 quadrant into the daily act of feedback. Solicit first, give second, encourage between others third. The HIP test — Humble, Helpful, Immediate, In person, Public praise / Private criticism, Not about Personality — is the integrity check for any individual piece of guidance.

Order of Operations — Get, Give, Encourage

The three manager obligations around guidance in a deliberate sequence: solicit criticism of yourself first, then give praise and criticism to your team, and only then encourage candid feedback between team members. Soliciting first earns you the standing to give.

The Go-To Question

Scott's killer question for soliciting criticism: "Is there anything I could do or stop doing that would make it easier to work with me?" Find the exact phrasing that rolls off your own tongue, but ask it relentlessly — and ask the same person multiple times across visits.

Reward the Candor

When someone gives you tough feedback, you must listen, find something to agree with and act on, and visibly change. If you punish (or even just absorb without responding to) candor, you will never get it again. Acting beats apologizing.

The HIP Test

Radically candid guidance is Humble, Helpful, Immediate, In person (or synchronous), and follows the public-praise/private-criticism rule — and is not about Personality. It's about the work and behavior. The mnemonic is the at-a-glance check before you open your mouth.

Praise in Public, Criticize in Private

Public praise multiplies the signal and models what "good" looks like for everyone watching. Public criticism triggers defensive posture and humiliation; deliver it in private. Exception: factual disagreements and debates can and should happen openly.

Forget the Praise-to-Criticism Ratio

Scott explicitly warns against prescribed ratios (5:1, 3:1). They push managers into insincere or ridiculous praise. The rule is simpler: worry more about praise than criticism, but above all be sincere. Ratio thinking corrupts both.

Guidance Is a Gift

Reframe both giving and receiving criticism as the act of offering clarity. You don't have to be omniscient or do the other person's work — you just have to be as clear as you can and hand that clarity over. The recipient gets to decide what to do with it.

Solicit / Get Guidance

Actively asking for criticism of yourself before offering it to anyone else.

The Go-To Question

The specific, rehearsed phrase you use to solicit criticism.

Reward the Candor

Visibly acting on solicited feedback so the giver knows it was worth the risk.

HIP / HHIPP

The integrity check for any specific piece of guidance.

Gift Mindset

Approaching guidance as offering or accepting a present, not a verdict.

SBI

Situation-Behavior-Impact, the structural template for impromptu criticism.

Praise-to-Criticism Ratio

A common prescription Scott rejects as a source of insincerity.

Impromptu Guidance

The two-to-three-minute, between-meetings conversation that is the atomic unit of management.

Multiple choice

A newly promoted manager wants to "build a culture of feedback" on day one. According to Chapter 6's order of operations, what should he do first?

• ASet up peer-feedback rounds so team members start critiquing each other immediately.
• BDeliver a round of impromptu criticism to each report so they know he takes the work seriously.
• CSolicit criticism on himself with a rehearsed go-to question and visibly act on what he hears.
• DSend a company-wide email announcing the new feedback norms before any 1:1 conversations.

Spot the issue

At the end of a 1:1, a manager asks, "Anything I could be doing better?" Her report says "Not really, everything's good." The manager nods, says "Great, thanks!" and moves to the next agenda item in under five seconds. What's the issue?

• AThe question itself is fine; the report simply has no feedback this week.
• BShe should have offered her own criticism first to model vulnerability.
• CShe didn't embrace the discomfort — she filled the silence instead of holding the pause that lets a hard answer surface.
• DThe question should never be asked in a 1:1; it belongs in formal performance reviews.

Multiple choice

A senior engineer made a strong architectural call in a Tuesday review. Her manager wants to use praise effectively. Which approach best fits Chapter 6?

• AMention it in the next all-hands with specifics about what she did and why it mattered.
• BSend a private Slack DM saying "great job today" so the engineer doesn't feel embarrassed.
• CWait for the next performance review to write it up formally so the praise carries weight.
• DHold the praise for now and balance it later with a piece of criticism to hit the 3:1 ratio.

True / False

According to Scott, maintaining a 3:1 or 5:1 ratio of praise to criticism is a reliable rule of thumb for managers because it ensures positive feedback stays dominant.

• TrueTrue
• FalseFalse

Spot the issue

After a director gives a report tough feedback about missed deadlines, the report shoots back: "Honestly, your meeting style is chaotic and I waste hours every week because of it." The director says, "I hear you, that's fair, I'll think about it," and never raises it again. Three months later the report has stopped offering any feedback at all. What went wrong?

• AThe director should have pushed back to defend her meeting style on the spot.
• BShe failed to reward the candor — she absorbed the feedback without visibly acting on it, so the report learned candor isn't worth the risk.
• CShe should not have given criticism first; soliciting must always precede giving.
• DThe report's feedback was about personality and should have been ignored under the HIP test.

Team

A manager's most important responsibility isn't motivation itself but understanding what already motivates each person and managing them according to their current growth trajectory. The chapter covers the Rock Star / Superstar reframe, career conversations, hiring for fit, firing as a kindness, and partnering with HR — all in service of growth management instead of performance ranking.

Growth Management Over Performance Management

Scott's replacement for "performance management." Instead of judging people on innate potential, evaluate each person's current growth trajectory (temporal, not fixed) and tailor development accordingly. Each report gets an annual Growth Management Plan.

Rock Stars vs. Superstars

Rock stars are on a gradual growth trajectory — excellent, expert, content. Superstars are on a steep trajectory — ambitious, change-oriented, flight-risk if under-challenged. Both are top performers. Managing them identically destroys the team: pushed rock stars burn out, neglected superstars leave.

Career Conversations

A three-meeting series with each new direct report: Life Story (transitions from kindergarten forward, surfacing values), Dreams (3-5 concrete pinnacle visions and the skills each requires), 18-Month Plan (working dreams backward into the next year and a half). Russ Laraway's framework, adopted as the chapter's core ritual.

Hire for the Trajectory the Role Needs

A precise job description, a diverse interview committee, and a structured debrief. Don't hire on gut feeling — but also don't put a superstar in a rock-star role, or vice versa. The trajectory match matters as much as the skill match.

Firing Is a Kindness

You're "not firing someone because they suck — you're firing them because the job they're doing sucks for them." Keeping a person in a role where they fail is cruel to them, unfair to teammates, and corrosive to culture. The Bob story (10 months of ruinous empathy ending in "Why didn't anyone tell me?") anchors this.

Promotions and Awards

Promote on demonstrated skills and growth, not tenure, charisma, or volume. Awards and public recognition often matter more to rock stars than promotions do — pay them for excellence-in-role. Opaque promotion criteria destroy trust; publish them.

Partner With HR, Don't Outsource To Them

HR is your ally for documenting performance issues, navigating firings legally, and structuring compensation — but it is not your substitute. The relationship is the manager's job; HR is the backstop, not the front line.

Growth Management

Managing each person to their current trajectory rather than ranking high/low performers.

Growth Management Plan

An annual plan a manager creates per direct report, tied to trajectory.

Rock Star

A top performer on a gradual growth trajectory, expert and stable.

Superstar

A top performer on a steep growth trajectory, ambitious and change-oriented.

Career Conversations

Russ Laraway's three-part series — life story, dreams, 18-month plan.

Firing as a Kindness

The reframe that ending a poor fit is mercy, not punishment.

Peter Principle

The risk of promoting a strong performer into a role where they fail.

Skip-Level Meeting

A once-a-year meeting with a manager's reports without the manager present, to surface upward feedback.

Multiple choice

Priya is a senior engineer who consistently ships excellent work, mentors juniors, and has told her manager three times that she has no interest in becoming a manager or a tech lead — she loves her current craft. Her manager keeps pushing her toward a staff-engineer track and adds management-prep stretch projects to her plan. What's the most accurate diagnosis?

• AThe manager is correctly applying growth management by pushing her toward higher impact.
• BThe manager is treating a rock star like a superstar, risking burnout and disengagement.
• CPriya has plateaued and the manager should put her on a performance plan.
• DPriya is a flight risk and needs more stretch assignments to stay engaged.

Spot the issue

A manager schedules the three Career Conversations with a new report but compresses them all into a single 60-minute meeting because "calendars are tight." She skips the kindergarten-onward life story ("too personal") and jumps to asking for one concrete five-year plan. What's the issue?

• AA single combined session is acceptable as long as all three topics are covered in order.
• BThe Life Story is meant to surface values across transitions, and Dreams should be 3-5 pinnacle visions — not a single rigid plan; collapsing the format defeats the purpose.
• CThe conversations should be conducted by HR, not the manager.
• DShe should have started with the 18-Month Plan and worked backward to dreams.

True / False

Firing an underperformer is a failure of management and should be framed as a punishment for poor work.

• TrueTrue
• FalseFalse

Multiple choice

A team has clear, published promotion criteria but a manager wants to reward an excellent rock star who has zero interest in moving up. What does Scott recommend?

• APromote her anyway — promotions are the only legitimate recognition.
• BWithhold all recognition until she agrees to a stretch role.
• CRecognize her with awards, public recognition, and pay for excellence-in-role rather than forcing a promotion.
• DMove her to another team where promotion is the only growth path.

Results

Chapter 8 inventories the meetings and rituals that operationalize the GSD Wheel without micromanaging. Each meeting type has a single job — staff meetings, big debate, big decision, all-hands, think time, walk-arounds, kanban. Don't mash them together. The chapter's discipline: every recurring practice maps to a step of the wheel.

Staff Meeting — Three Parts

One weekly meeting with three jobs only: (1) review key metrics (~20 min — what went well/badly and why); (2) share information via snippets read silently in "study hall" (~15 min); (3) identify the most important decisions and debates of the week (~30 min — surface, don't resolve). Resolution gets punted to dedicated meetings.

Big Debate Meeting

A meeting whose explicit and only purpose is to debate, not decide. Scott's rule: "Lower the tension by making it clear that you are debating, not deciding." Rotate roles, attack ideas not people, end with a written summary of facts and open questions — no decision required.

Big Decision Meeting

A separate meeting where the person closest to the facts presents a recommendation and the decider commits. Pushes "decisions into the facts and facts into decisions" so authority follows expertise, not hierarchy. The clean separation from debate is what keeps both honest.

All-Hands Meeting (Persuade Step)

Where leadership brings the broader org along after a decision is made. The job is persuasion, not announcement — explain the *why*, take real Q&A, acknowledge information asymmetry. Skipping this is the most common cause of org-wide malicious compliance.

Think Time on the Calendar

Blocked, defended hours (Scott blocked two per day) explicitly for thinking, not executing. Treat it as a meeting with yourself that cannot be moved. Without it, managers default to reactive mode and never get ahead of anything.

Walk-Arounds

Unstructured, unscheduled drop-ins to learn about small problems before they become big ones. The point is to *listen*, not inspect. Managers ask questions, take notes, and follow up later — the absence of an agenda is the feature.

Kanban for Managers

A visible board (physical or digital) that makes the manager's and team's workflow transparent. Surfaces bottlenecks, limits work-in-progress, and gives the manager something to *stop doing* rather than always more. Saying no becomes a visible discipline.

Meeting-Free Zones and Cultural Awareness

Protect maker time with no-meeting blocks (e.g., No-Meeting Wednesdays). And recognize that the manager's calendar, words, and rituals teach culture whether or not they intend to — every recurring practice is a statement about what the team values.

Snippets

Short written updates (last week / next week) read silently in staff-meeting study hall.

Big Debate Meeting

A meeting whose only output is a well-argued summary — no decision.

Big Decision Meeting

A meeting whose only output is a documented decision with an owner.

All-Hands Meeting

A whole-org meeting used to persuade the broader audience after a decision.

Think Time

Calendar-blocked, uninterruptible time for reflection rather than execution.

Walk-Around (MBWA)

Informal, unscheduled in-person check-ins to gather small-signal information.

Kanban Board

A workflow visualization with To Do / Doing / Done columns to limit WIP.

Meeting-Free Zone

A scheduled block (e.g., No-Meeting Wednesday) protecting maker time.

Spot the issue

At Friday's weekly staff meeting, the team spends the first hour debating whether to migrate to a new analytics vendor, then 20 minutes catching up on metrics, then runs out of time before sharing snippets. The lead says, "At least we made the migration decision in real time — that's efficiency." What's the issue?

• AThe staff meeting correctly resolved the biggest open question.
• BStaff meetings should surface decisions and debates, not resolve them; resolution belongs in a separate Big Decision meeting so neither metrics nor information-sharing get crowded out.
• CThe team should have skipped metrics entirely to leave more debate time.
• DSnippets should always come first, before metrics.

Multiple choice

A leadership team holds a single 90-minute meeting where they debate the pros and cons of a new pricing model and walk out with both a finalized decision and an action plan. Within a week, half the room is privately undermining the decision. What core discipline did they violate?

• AThey should have made the decision unilaterally to avoid groupthink.
• BThey held the meeting too early in the quarter.
• CThey collapsed Big Debate and Big Decision into one meeting, which warps debate by who holds authority and skips the clean handoff that keeps both honest.
• DThe recommendation should have come from the most senior person in the room, not the person closest to the facts.

True / False

Walk-arounds are essentially manager-led inspections — the goal is to spot-check whether people are doing their work correctly.

• TrueTrue
• FalseFalse

Multiple choice

A director's calendar is solid back-to-back meetings every day and her team complains she's perpetually reactive — missing emerging risks and never weighing in on strategy. Which Chapter 8 practice most directly addresses her root problem?

• AAdd more all-hands meetings to broadcast strategy.
• BBlock defended Think Time on the calendar as a meeting with herself that cannot be moved.
• CSchedule additional 1:1s with each report.
• DReplace her weekly staff meeting with an additional Big Debate session.