Handling Architectural Disagreement

Unresolved architectural disagreement is more damaging than either option being chosen, because it produces a system built by people going in different directions, and the incoherence costs more than whichever choice was worse.

The techniques that resolve rather than suppress. Separate the disagreement into facts, forecasts and values, because they need different treatment — a factual dispute is testable, a forecast can be made concrete by asking what would confirm or refute it, and a values disagreement is a genuine difference in priority that must be surfaced and escalated rather than argued.

Steelman the other position before responding. This is not politeness; it frequently reveals that the disagreement is about an unstated constraint one party can see and the other cannot, and the real resolution is usually there.

Make the disagreement testable. A spike, a load test, a prototype settles more arguments in two days than a fortnight of debate, and both parties can accept the result without loss of face.

Disagree and commit when a decision must be made without consensus. State the reservation, record it in the ADR, and then implement wholeheartedly. The written reservation is what makes this honourable rather than passive — it is a documented position that can be revisited with evidence, not a grudge.

And know who decides. An argument with no decision-maker continues until someone tires, which selects for persistence rather than for the better answer.