One-Way Door Decision

The classification exists to allocate scarce deliberation. Most decisions are two-way doors — reversible at modest cost — and treating them as though they were permanent is how organisations become slow without becoming safer. A small number genuinely are one-way, and treating those casually is how they acquire constraints they carry for a decade.

The one-way doors in architecture are recognisable. A data model in a system with millions of records and dozens of consumers. A public API contract with external clients. Service boundaries, since redrawing them means redistributing data and ownership. A cloud provider choice for the data layer, given egress economics and managed service dependencies. Encryption and identity foundations. And anything involving data that has left your control.

The two-way doors that get over-deliberated: internal library choices, frameworks within a single service, deployment tooling, most infrastructure configuration — all replaceable with contained effort.

The genuinely useful move is not just classifying but converting: designing so that a decision becomes reversible. An abstraction over a datastore, a versioned contract, a feature flag, a strangler facade, or a pilot in one region rather than a full commitment. An architect who consistently turns one-way doors into two-way ones is providing more value than one who deliberates well, because the organisation gets to be wrong cheaply.