Listen-Challenge-Commit
The wisdom to know when to stop arguing and get on board
Borrowed from Andy Grove's Intel and adopted at Apple, Listen-Challenge-Commit provides a disciplined approach to navigating disagreement in hierarchies. A strong leader listens with genuine humility to understand opposing perspectives, challenges with confidence to make sure the best thinking is heard, and then commits with wisdom even when the final decision goes against their position.
This framework solves the middle manager's Catch-22: if you tell your team you agree with a decision you actually oppose, you feel inauthentic. If you tell them you disagree, you look weak or insubordinate. The solution is transparency about the process: 'I had an opportunity to argue. Here is what I said. Here is what I learned about why we are going this direction. Now it is time to commit.'
The framework also applies to the leader's own role in getting decisions right. Steve Jobs was famous not for being always right, but for always getting it right by insisting that people challenge him vigorously enough that his wrong ideas were corrected before execution. When a colleague backed down too easily and events proved the colleague right, Jobs's response was not gratitude but anger: 'It was your job to convince me I was wrong, and you failed.'
- Listening is not passive agreement. It is active work to understand perspectives you may not share.
- Challenging is not insubordination. It is a responsibility. If you fail to voice your disagreement, you have failed the team.
- Commitment after disagreement is not weakness. It is the maturity to prioritize team execution over personal ego.
- Transparency about the process resolves the middle manager's authenticity dilemma.
- Getting it right matters more than being right.
- Listen with HumilityBefore forming or expressing your opinion, genuinely listen to understand the perspectives of others, especially those you disagree with. Resist the urge to plan your rebuttal while the other person is talking. Repeat back what you hear to confirm understanding.Pro tipIf you find yourself unable to articulate the strongest version of the opposing argument, you have not listened enough.WarningQuiet listening does not mean agreement. Make sure people know you are still forming your view, not capitulating.
- Challenge with ConfidenceOnce you understand the opposing view, make your case clearly and directly. Do not soften your argument to avoid conflict. If you believe the decision is wrong, say so with evidence and reasoning. Keep arguing until you are either convinced you are wrong or you have genuinely exhausted your case.Pro tipSteve Jobs expected people to argue until one party was genuinely convinced. If you back down too easily, you have not fulfilled your obligation.WarningThere is a difference between challenging on substance and challenging on ego. Keep the debate about the issue, not about winning.
- Commit with WisdomOnce the decision is made, commit fully regardless of whether you won the argument. Execute as if it were your own decision. When your team asks about it, be transparent: 'I argued my case, I was heard, and now we are going this direction for these reasons.'Pro tipIf you cannot commit to a decision even after genuine challenge, you may need to escalate or, in extreme cases, consider whether you are in the right organization.WarningDo not undermine the decision through passive resistance, eye-rolling, or telling your team 'I disagreed but was overruled.' That destroys both your credibility and the team's execution.
A colleague argued with Steve Jobs about a direction but eventually backed down, not because he was convinced but because he was tired of fighting. When events proved the colleague right, Jobs marched into his office and yelled: 'It was your job to convince me I was wrong, and you failed!'
Scott describes the common situation where a middle manager must execute a decision they disagreed with. Rather than pretending to agree (inauthentic) or openly dissenting (insubordinate), the Listen-Challenge-Commit framework provides a third option: transparency about the process.
Andy Grove developed this as a leadership mantra at Intel, where it became shorthand for how leaders should handle disagreement. Scott encountered it at Apple, where it was used to describe the leadership expectations for managers at all levels. The framework crystallized for her through observing Steve Jobs, who embodied the challenge phase so intensely that colleagues learned to argue until one party was genuinely convinced, not just until the boss got tired of debating.