Disagree and Commit

The commitment is the easy part to remember. The disagreement is the part worth keeping.

October 13, 2026 7 min read

March. A pricing thread in Slack runs long. The product lead wants to drop the free tier and move everyone to a 14-day trial. The head of support disagrees: free users file a large share of the bug reports that matter, and she expects quality signal to drop once they're gone. The thread can't settle it. The product lead asks, "Will you disagree and commit?" She says yes. The trial ships in April.

September. Escalations from paying customers are up, and they're about bugs that used to surface earlier. Someone asks whether removing the free tier had anything to do with it. Nobody in the room was in the March thread. The head of support has since moved teams. The decision record, if anyone can find it, says "Move to 14-day trial." It doesn't say anyone disagreed, or what she predicted.

The commitment survived. The disagreement didn't, and the disagreement was the part that could have helped.

What the phrase was meant to do

Jeff Bezos popularized the phrase in his 2016 letter to Amazon shareholders: "Use the phrase 'disagree and commit.' This phrase will save a lot of time." His example was an Amazon Studios original he had doubts about. He told the team his concerns, they wanted to go ahead, and he replied that he disagreed and committed and hoped it would become the most watched thing Amazon had made.

He was specific about what made it work. It was, in his words, "a genuine disagreement of opinion, a candid expression of my view, a chance for the team to weigh my view, and a quick, sincere commitment to go their way." The disagreement is stated in the open and heard, and then the commitment comes quickly. Nothing in that description asks anyone to forget the disagreement either.

Two ways it goes wrong

Disagree and commit has two failure modes, and they point in opposite directions.

The dissent goes underground. Someone says "commit" in the meeting but never stops disagreeing. The work assigned to them moves a little slower, the edge cases get raised a little later, and the decision gets relitigated in hallways. The team paid for a commitment and received compliance.

The dissent disappears. Everyone commits sincerely, and the disagreement leaves with the people who held it. That is the March thread. Nothing goes wrong at first. The cost shows up later, when the dissenter's prediction starts coming true and nobody recognizes it, because nobody remembers it was a prediction.

The first failure is a problem of trust. The second is a problem of memory, and it is the one that gets worse as teams grow, people move, and decisions outlive the conversations that made them.

Keep the disagreement, not just the decision

A useful disagreement has three parts, and all three fit in a few sentences:

1. Who disagreed. The team needs to know whom to ask when the question comes back.
2. What they expected to happen. "Quality signal will drop because free users find bugs that paying users don't report."
3. What would show they were right. "If escalations about previously unreported bugs rise for a full quarter, revisit."

Written that way, the dissent becomes something the whole team can watch for, which is the move a tripwire makes. It also changes what committing means. The dissenter backs the decision, and the record keeps her concern where the team can find it when the evidence arrives. That is a far easier promise to keep sincerely.

Where this fits at Brief

Disagree and commit asks two things of a team's memory: hold the commitment so everyone builds on the same decision, and hold the disagreement so the team knows what it bet against. Brief is built to keep that record.

The decision is captured where the argument happened. When someone logs a decision by mentioning Brief in a Slack thread, Brief reads the surrounding thread for context and proposes a structured decision to confirm or edit, as the Slack integration guide describes. The record carries the decision, the rationale, who logged it, when, and the channel. The March thread is where the head of support made her case. Capturing the decision from that thread puts the disagreement one edit away from the record, where a reorganization can't take it.

The dissent lives in the rationale. Brief has no separate dissent field, and it is worth being plain about that. The place for the disagreement is the rationale: "Move to a 14-day trial to improve conversion. Support disagreed: free users surface bugs paying users don't report. Revisit if escalations about previously unreported bugs rise for a full quarter." That sentence costs ten seconds in March. In September it turns "did this have anything to do with it?" from a guess into a lookup.

Reversing doesn't reopen the argument. If the prediction comes true, the team can record a new decision that replaces the old one. Brief tracks when one decision replaces another and keeps the earlier one as history, as the supersession post describes. The original call and the dissent stay readable side by side. Nobody has to win the March argument retroactively; the record shows the team made a reasonable bet, noted the risk, and acted when the risk showed up.

Everyone, including agents, builds on the commitment. A commitment is only real if the work follows it. Before an architectural change, a coding agent can ask Brief to check the plan against recorded decisions with brief ask --mode check. An agent asked to build a free-tier feature can have that plan checked against the trial decision. That is the same reason a recorded decision works as common knowledge: it sits in one place everyone knows the others are reading.

The limits are real. A record can't make a commitment sincere. Someone who says "commit" and slow-walks the work will do it with or without a record. What the record fixes is the second failure, the one where honest dissent simply disappears. It gives the person who disagreed a reason to commit in good faith, because her concern has a place to wait.

Think of the last decision your team made over an objection. Could you find what the objection predicted?

Frequently asked questions

What does disagree and commit mean? Backing a decision you argued against, after making your case openly. Jeff Bezos popularized the phrase in his 2016 letter to Amazon shareholders, and gave an example that combined a genuine disagreement of opinion, a candid expression of his view, a chance for the team to weigh it, and a quick, sincere commitment to go their way.

Does disagree and commit mean the disagreement should be forgotten? No. The commitment is to the decision. Recording who disagreed, what they expected, and what evidence would prove them right lets the team revisit the decision when that evidence arrives.

What goes wrong with disagree and commit? Two things. Dissent can go underground, where people say they commit but keep resisting through the work. Or dissent can disappear, where everyone commits sincerely but nobody records the disagreement, so the team doesn't recognize it when the dissenter's prediction comes true.

How does Brief help with disagree and commit? Brief records decisions with their rationale, who logged them, and when, can capture them when someone mentions Brief in the Slack thread where the discussion happened, and tracks when one decision replaces another, keeping the earlier one as history. Brief has no separate dissent field, so the disagreement is kept by writing it into the rationale.