The most common failure is the escalation that escalates to the wrong level. An irreversible architectural decision is escalated to a manager who resolves it by authority rather than analysis. The manager’s resolution is binding but not reasoned. Engineers who disagreed continue to disagree. The decision is implemented, but the dissenting engineer has not committed — they have complied. FM9 (Silent Data Corruption) at the organisational level: the decision is on paper but the implementation quietly diverges from the decision in ways that surface later as architectural inconsistency.
FM4 (Data Consistency) in the technical disagreement context: different teams have different beliefs about what was decided, because the resolution was communicated verbally without an ADR. Three months later, a new design decision depends on the earlier resolution. The teams proceed with different assumptions. The integration fails.
The disagree-and-commit failure mode is the most damaging: a technical leader announces a decision and requests commitment from the team, but the commitment is not genuine. The dissenters comply publicly and resist privately. The implementation is technically correct but subtly suboptimal in the ways that would have been obvious if the disagreement had been resolved rather than overridden. The leader has purchased compliance at the cost of the team’s actual engagement.
Concept: Managing Technical Disagreements Thread: T12 (Tradeoffs) ← disagreement about correctness → disagreement about preference → name the tradeoff, choose the context Core Idea: Technical disagreements are almost always disagreements about unnamed tradeoffs; naming the AT code both parties are optimising for converts a correctness dispute into a preference negotiation that can be resolved by context. Tradeoff: AT6 — case-by-case resolution (flexible, inconsistent) vs process-based resolution (consistent, higher overhead) Failure Mode: FM9 — silent data corruption; decisions resolved by authority without genuine commitment are implemented with quiet divergence from the stated decision Signal: When the same technical disagreement recurs with different participants — the previous resolution did not name the tradeoff; write the ADR now with the tradeoff and reversal conditions Maps to: Reference Book, Framework 4