Ceremony proportional to irreversibility: Type 1 vs Type 2 engineering decisions
By Decision Desk Every engineering team eventually has the same argument. One group says "we need more design review, we keep shipping things we regret." Another says "we need less process, it takes three weeks to change a config value." Both are usually right, about different decisions. The fix isn't more process or less. It's matching the process to how hard the decision is to undo. That idea…
Engineering teams often debate whether to use more or less process for software decisions. The key to resolving this debate lies in understanding the irreversibility of each decision. Amazon's 2015 shareholder letter introduced the concept of Type 1 "one-way doors" – consequential and nearly irreversible decisions requiring careful deliberation – and Type 2 "two-way doors" – quicker decisions that can be undone if needed.
Both approaches have merit, but the type of decision dictates the appropriate level of process and review. Operations rollback is a quick way to undo operational changes, but architectural reversal – the true cost of undoing a decision – can be significant. Type 1 decisions involve irreversible data, contracts, or ecosystem changes, and require more rigorous review.
Type 2 decisions are reversible, such as toggling feature flags or using temporary contracts. By assessing the potential for irreversible consequences, engineering teams can determine the appropriate amount of ceremony required for each decision, ensuring efficient yet responsible decision-making.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
