Disagree and Commit

You're seeing Disagree and Commit when a leadership team spends three hours debating a product roadmap, the CEO picks a direction that two VPs argued against, and those VPs walk out of the room and immediately begin resourcing the chosen plan with full energy. No whispered complaints in hallways. No slow-rolling the timeline. The debate was real. The commitment is real.

You're seeing Disagree and Commit violated when a decision gets made in a meeting but the dissenting executive continues lobbying against it in one-on-ones afterward. The team senses the lack of unity. Execution slows. People start hedging, unsure which direction will actually stick. The decision was technically made but never truly committed to — and uncommitted decisions are worse than no decision at all, because they consume resources without producing outcomes.

You're seeing Disagree and Commit when an engineering team debates whether to build on a monolith or microservices architecture. The CTO picks microservices. The lead architect, who argued passionately for the monolith, writes the migration plan and champions the new architecture to the team. Six months later, the architect identifies a genuine problem with the chosen approach and raises it — not as vindication, but as new information that warrants a new decision.

You're seeing Disagree and Commit when two co-founders argue about whether to raise venture capital or bootstrap. They disagree fundamentally on the right path. After a week of intense discussion, they decide to raise. The bootstrapping advocate becomes the most effective fundraiser in the room — because they understand the counterarguments better than anyone and can address investor concerns before they're raised.

Build the norm early and model it visibly. The first time you disagree with a co-founder's decision and then execute it wholeheartedly, you establish the culture. The first time you override someone and they see you later admit the decision was wrong, you earn the trust that makes the model sustainable.

This is harder than it sounds. Early-stage founders have strong opinions about everything — that's why they started a company. The temptation to use your position to win every argument is enormous. Resist it. Disagree and commit only works in environments where people trust that their dissent was genuinely considered — not just tolerated as a ritual before the predetermined outcome. That trust is built through repeated demonstrations, not declarations. You cannot announce a disagree-and-commit culture. You can only demonstrate one.

Your job is to protect both phases. Protect the disagreement by making it safe: never punish someone for arguing against your preferred direction. Never telegraph your preference before the debate begins — the moment people know what the boss wants, disagreement becomes career risk rather than intellectual contribution. Ask the most junior person in the room to speak first. Structure the discussion so that dissent has a seat at the table before consensus can take over.

Then protect the commitment by making it non-negotiable: once the decision is made, anyone who undermines execution through passive resistance or backchannel lobbying is violating the contract. Address violations directly and quickly — if a senior leader is sandbagging a committed decision, the entire organisation sees it and draws conclusions about whether the model is real. The model has teeth on both sides.

Disagree and commit gives you both a right and an obligation. The right: voice your strongest objections during the decision phase. Bring evidence. Be specific about risks. Don't soften your position to avoid discomfort — a politely hedged objection is worse than useless because it lets the decision-maker believe they've heard the full case against when they haven't.

The obligation: once the decision is made, execute with your full capability. Not 80% effort with 20% reserved for "I told you so." If the decision later proves wrong, that's new information for a new decision — not retroactive validation of your dissent. Your track record in a disagree-and-commit culture is built on two things: the quality of your disagreements and the completeness of your commitments. Both matter equally.

Bezos didn't just preach disagree and commit — he described being on the losing side of the argument. In his 2016 letter to Amazon shareholders, he recounted a specific Amazon Studios project where the team wanted to greenlight a show. Bezos disagreed with the creative direction. He thought the pitch was flawed.

But the team had conviction. They'd done the research. They had data Bezos didn't have about the audience, the content landscape, and the competitive dynamics of streaming originals. Bezos recognised that his disagreement didn't mean his judgment was better — it meant the decision involved genuine uncertainty, and the team closest to the problem was better positioned to evaluate it. He told them directly: "I disagree and commit and hope it becomes the most watched thing we've ever made."

The significance wasn't the show itself. It was the CEO of a trillion-dollar company publicly modelling what it looks like to lose an argument gracefully and execute anyway. By sharing the anecdote in a shareholder letter read by millions, Bezos was doing something deliberate: establishing that disagree and commit runs in both directions at Amazon. It's not just what leaders ask of their teams. It's what leaders practice themselves. That one anecdote did more to establish the norm than any leadership principle document could.

In 1985, Intel was haemorrhaging money in the memory chip business. Japanese competitors had undercut Intel on price and quality simultaneously. Grove and Gordon Moore faced a decision that split the company's leadership. Many senior executives — people who had built their careers in the memory division — believed Intel should double down, invest in better fabrication, and fight for market share. Grove famously asked Moore: "If we got kicked out and the board brought in a new CEO, what do you think he would do?" Moore answered without hesitation: "He would get us out of memories." They walked back into the building and did exactly that. The dissenting executives, some of whom had spent fifteen years building Intel's memory business, committed to the pivot. Intel's microprocessor revenue grew from a small fraction to virtually the entire business within five years. The constructive confrontation culture Grove had built made the disagreement fierce and honest — and then made the commitment total. Years later, several of those dissenting executives acknowledged that the pivot saved the company. But at the time, they believed it was a mistake. Their commitment wasn't based on agreement. It was based on trust in the process and the willingness to let the market, not internal politics, determine who was right.

When Nadella became CEO of Microsoft in 2014, the company's identity was built around Windows. The previous decade had been defined by Steve Ballmer's famous mantra — "Windows, Windows, Windows" — and the organisational structure reflected that priority. Pivoting to cloud-first meant telling thousands of employees that the platform they'd spent their careers building was no longer the centre of the company's strategy.

Entire divisions disagreed. The Windows team argued that abandoning their platform advantage was reckless. The Office team worried about cannibalising lucrative license revenue with cheaper cloud subscriptions. Enterprise sales leaders who had spent decades selling perpetual licenses saw the subscription model as a threat to their commission structures and client relationships.

Nadella listened to the dissent. He held town halls, took feedback seriously, and adjusted timelines based on legitimate operational concerns. He didn't dismiss the objections — many of them were correct about short-term costs. Then he made the call. Azure became the priority. Office 365 would replace perpetual licenses. The commitment was non-negotiable. Leaders who couldn't commit to the new direction were quietly replaced. Azure revenue grew from roughly $4 billion in 2015 to over $80 billion by 2024 — a transformation that required thousands of people who disagreed with the strategy to execute it with full commitment. The disagreement made the strategy better. The commitment made it real.

Pixar's Braintrust meetings are disagree and commit made institutional. In these sessions, the director of a film-in-progress screens their work for a group of senior creative leaders — including John Lasseter, Andrew Stanton, Pete Docter, and others — who then deliver candid, unvarnished feedback. The criticism can be devastating. Entire storylines get torn apart. Character arcs that consumed months of work get questioned at a fundamental level.

But two rules make the Braintrust function where similar processes at other studios collapse into either groupthink or creative paralysis. First, the feedback must be honest and specific — no vague encouragement, no pulling punches to protect egos. The disagreement must be genuine. Second, the director has final authority over what to do with the feedback. They own the commitment. The Braintrust is advisory, not executive. This means directors sometimes reject the Braintrust's consensus view and proceed with their original vision. Nobody retaliates. Nobody slow-rolls production to prove the director wrong.

Catmull described this structure in Creativity, Inc. as essential to Pixar's ability to produce consistently excellent films over two decades. The disagreement is mandatory. The commitment belongs to the person accountable for the outcome. The separation of those two responsibilities is what keeps the system healthy.

Lincoln assembled a cabinet of political rivals — William Seward, Salmon Chase, Edwin Stanton — men who believed they should have been president instead. Cabinet meetings were famously contentious. Seward, who had been the frontrunner for the Republican nomination, initially viewed Lincoln as an inferior. Chase actively schemed for the presidency while serving as Treasury Secretary. Stanton had publicly humiliated Lincoln in a legal case years earlier.

On the Emancipation Proclamation, the disagreements were fundamental: Seward argued the timing was wrong — issuing it after a string of Union military defeats would look like a desperate measure rather than a position of strength. Chase wanted the proclamation to go further. Montgomery Blair warned it would cost the party seats in the midterm elections. Lincoln heard every argument. He incorporated Seward's tactical concern and delayed the announcement to wait for a Union military victory. When the Battle of Antietam provided that opportunity in September 1862, he issued the Proclamation. The cabinet members who had disagreed — some vehemently — committed to defending and implementing the policy. Seward, who had argued most forcefully for delay, became one of the Proclamation's most effective advocates to foreign governments. The strength of the disagreement phase made the commitment credible. No one could claim the decision was made in an echo chamber.