Two-Way Door Decision

A two-way door decision can be reversed at a cost and within a time acceptable for its context. A one-way door describes a commitment whose consequences cannot practically be undone on those terms. Amazon and GitLab use this metaphor to encourage lighter review where experimentation is appropriate. Reversibility is one input to review effort; potential harm, uncertainty, obligations, and valid authority also matter.

Distinguish changing a decision, restoring a system, and undoing effects already produced. Stopping a claims-processing pilot does not retrieve information already disclosed or reverse an external payment. A reversible data transformation may be recoverable if mappings, backups, and dependent records support it. Discarding irreplaceable records is different. Contract exit clauses and dependencies matter more than the contract’s duration alone. Set a useful recovery window for the actual service; one year is not a universal boundary.

Two ways to misclassify

A small experiment can inherit a large commitment through automatic contract renewal, production writes, or sensitive-data access. Conversely, a well-isolated experiment may not need the full review appropriate to a major purchase. Specify the scope, exposure, spending limit, stop conditions, reversal steps, responsible parties, and evidence that recovery will work. If the recovery evidence is missing, reversibility is unverified. That is a reason to investigate, not proof that reversal is impossible.

No classification grants approval rights. A budget holder may still need procurement, data, security, or release authorization. In a fictional claims-engine comparison, the executive committee had authority to fund a cross-functional test. The CTO could not alone commit all teams or approve their data use. The committee’s bounded approval therefore complemented separate control approvals. Production rollout and a long-term purchase remained later decisions.

GitLab’s commitment principle permits questioning and changing a decision through the person with authority to change it. Follow the current governance, including authorized emergency suspension and escalation routes where applicable; repeating the original meeting is not always necessary. Record the change and its reason, while recognizing that past effects may remain. Forty Slides and No Ask connects this assessment to a decision document; decision rights explains the mandate independently of reversibility.

References

• GitLab Handbook, Values.
• Amazon, Leadership Principles.