A decision discipline that respects dissent while preventing endless debate. The right response when you've voiced your objection, been overruled — and now must back the decision fully.
▸ Try the interactive toolThe Disagree and Commit Protocol is a decision-making discipline that respects dissent while preventing endless debate. It's the correct response when you disagree with a product decision and have stated your objection — but have been overruled. It's also the protocol you ask of others when you've made a call they dispute. It resolves the tension between genuine disagreement and the need to move.
The discipline has two halves, and both matter. Disagree: voice your objection clearly and fully, with your reasoning, while the decision is still open — dissent that's swallowed isn't honoured, it's wasted. Commit: once the decision is made (and made against you), back it genuinely and visibly — not sabotage it, not 'I told you so,' not quiet undermining. The protocol fails if either half is skipped: no disagreement means groupthink and unexamined decisions; no commitment means a team that can never move because every decision is relitigated forever.
Disagree — voice your objection fully, with reasoning, while the decision is open.
Commit — once it's made (even against you), back it genuinely and visibly. Both halves required: dissent without commitment paralyses; commitment without dissent is groupthink.
Teams get stuck at both extremes — either decisions are relitigated endlessly because the overruled won't commit, or genuine objections are never voiced and bad decisions sail through unexamined.
| The shortcut | What it costs | What it gives you instead |
|---|---|---|
| Relitigating decisions | The overruled keep fighting; the team can never move. | Committing after losing lets the team execute. |
| Quiet undermining | Backing a decision in words while sabotaging it in deeds. | Genuine, visible commitment makes execution real. |
| Swallowing dissent | Objections never voiced mean unexamined, groupthink decisions. | Disagreeing fully while it's open surfaces the risks. |
| 'I told you so' | Gloating when an overruled decision falters poisons trust. | Genuine commitment means owning the outcome together. |
Voice your objection clearly, with your reasoning, before the call is made. Honour dissent by expressing it properly — a swallowed objection helps no one and breeds resentment.
If you're overruled after a fair hearing, the debate is over. Continuing to fight relitigates a settled decision and stops the team from moving — the failure mode commitment exists to prevent.
Back the decision in deed, not just word — no sabotage, no half-effort, no quiet undermining. Visible commitment is what lets the team execute with full force despite the prior disagreement.
If the decision falters, resist gloating. You committed; you own the outcome together. 'I told you so' poisons the trust the protocol depends on.
When you make a call others dispute, give them the full Disagree (a real hearing) and then ask for the genuine Commit. The protocol is reciprocal — it works as a shared team norm.
A PM strongly disagreed with a product decision, voiced their objection with clear reasoning — and was overruled after a fair hearing. The tempting response was to keep relitigating it, or to comply outwardly while quietly withholding effort and waiting to be proven right. Either would have stopped the team from executing the decision properly.
Instead they applied Disagree and Commit fully: having had their say while the decision was open, they accepted the overruling and backed the decision genuinely — visibly, with full effort, no undermining, no 'I told you so' held in reserve. The team could execute at full force, and the PM's credibility rose: they'd shown they could disagree honestly and still commit completely, which is exactly what makes their future dissent worth listening to.
The deliverable is the discipline applied both ways — disagreeing fully while open, committing genuinely once decided, and asking the same of others.
| Phase | Do | Don't |
|---|---|---|
| While decision is open | Voice objection + reasoning | Swallow your dissent |
| Once overruled | Accept it; debate's over | Keep relitigating |
| Execution | Commit genuinely & visibly | Undermine or half-effort |
| If it falters | Own it together | Say 'I told you so' |
Disagree and Commit resolves the core tension of team decision-making: how to honour genuine dissent without being paralysed by it. The discipline is that both halves are non-negotiable — and the harder, more telling half is the commit.
Most teams fail one half or the other. Some never get the disagreement — objections are swallowed, dissent is read as disloyalty, and decisions sail through unexamined into groupthink. Others never get the commitment — the overruled keep fighting, comply grudgingly, or quietly undermine, so every decision is effectively relitigated forever and the team can't move. The protocol demands both: full, honest disagreement while the decision is open (which surfaces risks and honours the dissenter), and genuine, visible commitment once it's made (which lets the team execute). The commit half is the real test, because backing a decision you argued against — with full effort, no sabotage, no 'I told you so' — is hard. But a PM who can do it earns enormous credibility: it proves their disagreement is honest rather than obstructive, which is exactly what makes their future objections worth hearing.
The debate's over once decided. Continuing stops the team moving.
Genuine commitment is visible and full-effort. Quiet sabotage breaks the protocol.
Unvoiced dissent means unexamined decisions. Disagree fully while it's open.
Gloating when it falters poisons trust. You committed — own the outcome together.
It's a specific protocol within productive conflict (Tool 19).
Committing to a team decision connects to self-organising team norms (Module 4).
Genuinely committing after losing is a major capital deposit (Tool 12).
The disagree half needs an environment where dissent is safe to voice (Tool 17).
Recall a decision you disagreed with and were overruled on. Honestly: did you commit genuinely, or did you relitigate, half-effort it, or hold an 'I told you so' in reserve?
If you fell short on the commit, what would genuine, visible commitment have looked like — and how would it have changed the team's execution and your credibility?
If the hard part was committing to a decision you'd argued against, you've found the discipline's real test — and why doing it well is what makes your future disagreement worth hearing.