Listen, Challenge, Commit
Disagree fully first, then commit fully — never fake agreement.
- Difficulty
- Moderate
- Time to result
- ~ongoing to results
- Steps
- 3
- Confidence
- 88%
Listen, Challenge, Commit is Scott's sequence for handling disagreement. First you listen to understand, then you challenge directly — voicing your real disagreement so the other person can explain why you might be wrong. Only after the challenge is exhausted do you commit, and you commit fully even if the decision went against you. The failure modes are skipping the challenge (faking agreement, which is dishonest and deprives everyone of your dissent) and committing too early (backing down before the debate has done its work).
Origin
Scott illustrates the principle with Steve Jobs, who demanded to be challenged and once berated a report who caved too soon: 'it was your job to convince me I was wrong and you failed.' She contrasts it with her own false apology to Larry, where she skipped an honest challenge entirely.
Core principles
- 01When you disagree, voice the challenge before you commit — don't skip the challenge.
- 02Challenging gives the other person the chance to explain why you may be wrong.
- 03Once a decision is made, commit fully even if you'd have chosen differently.
- 04Committing too soon deprives the team of the friction that produces better decisions.
How to run it
- 1
Listen to understand
Take in the other person's position with the intent to understand it, not merely to counter it.
- 2
Challenge directly
Voice your genuine disagreement and make your case. You can say 'I'll do it your way, but I want to explain why I have questions about this.'
Pro tip Challenging invites the other person to explain why you may be wrong — you both learn.
Watch out Skipping the challenge and faking agreement is dishonest and robs the decision of your dissenting input.
- 3
Commit fully
Once the decision is made, commit even if it went against you: 'I'm still not sure I agree, but we'll do it your way.'
Watch out Committing too soon, before the debate has run, produces worse decisions — as Jobs told the report who caved.
In the wild
A direct report argued with Steve Jobs three times about a feature, then committed to Jobs's way. The decision turned out wrong. Jobs charged in demanding to know why they did it that way; the report said 'it was your idea.' Jobs replied it had been the report's job to convince him he was wrong, and he'd failed.
→ Jobs used the episode to enforce that people must challenge him hard enough and long enough before committing.
Common mistakes
Faking agreement to avoid conflict
Pretending to agree when you don't is a lie, and it deprives the decision-maker of the chance to hear your dissent and possibly change course.
Committing before the debate is done
Backing down too soon removes the productive friction that stress-tests a decision and produces a better outcome.
Is it for you?
Best for
Teams and individuals navigating disagreement with a boss or peers before a decision is locked.
Not ideal for
Trivial decisions where the friction cost of a full challenge outweighs any benefit.
From the transcript
“you want to make sure that you're communicating your willingness to listen, challenge, commit. But don't skip that challenge part”
“Yes, and it was your job to convince me I was wrong and you failed.”
From the episode
Kim Scott: Radical Candor, How to Say What You Mean Without Being A Jerk
Kim Scott