After the Decision
Nemawashi builds alignment before the decision. SPADE structures the decision itself. But what happens after the decision, when someone still disagrees? This is where Disagree and Commit completes the framework.
The concept — popularized by Andy Grove at Intel and later adopted as an Amazon Leadership Principle — is straightforward: once a decision has been made through a legitimate process, everyone, including those who argued against it, commits fully to executing it. You do not sabotage. You do not say "I told you so" when problems arise. You do not half-heartedly implement. You execute as if it were your own idea.
This is not blind obedience. It requires two preconditions:
- You had a genuine opportunity to be heard. This is why Nemawashi and the Consulted role in SPADE matter so much. If people feel the process was fair, they can accept an outcome they disagree with.
- The decision was made by someone with clear accountability. This is why SPADE's single Decider matters. If a faceless committee decided, there's no one to hold accountable, and commitment erodes.
The failure mode engineers must avoid: passive resistance. This looks like attending implementation meetings but not contributing ideas. Implementing the decision but not investing in making it succeed. Privately telling other teams "I didn't agree with this." This behavior is more destructive than open disagreement because it's invisible and corrosive — it poisons team culture without ever surfacing as a conflict that can be resolved.
The healthy pattern: "I argued for Option B and I still think it had merit. But the Decider chose Option A after hearing all perspectives, and I'm going to make Option A succeed. If it doesn't work, we'll have a retrospective and adjust."
Key Point: Disagree and Commit is not about suppressing dissent — it's about separating the debate phase from the execution phase. During debate, maximum disagreement is healthy. During execution, maximum alignment is essential. The framework boundary — the moment the Decider decides — is what separates the two phases. Engineers who can't make this transition, who carry debate energy into execution, become organizational bottlenecks regardless of their technical skill.