Reversible vs Irreversible Decisions
Jeff Bezos's framework for distinguishing one-way door decisions (irreversible) that require careful analysis from two-way door decisions (reversible) that can be made quickly.
Disciplines
Origin Story
Jeff Bezos introduced the Type 1 vs Type 2 framework in Amazon's 2015 shareholder letter. He observed that large organizations tend to treat all decisions like heavy one-way doors, when most decisions are actually two-way doors that can be reopened. Bezos used the example of opening Amazon's marketplace to third-party sellers in the early 2000s. Many Amazon executives opposed it, fearing internal competition. Bezos viewed it as a reversible decision worth testing quickly. The result: third-party sellers grew from 3% to 58% of Amazon's total GMV by 2018.
Core Principles
- 1Identify whether a decision can be easily reversed or cannot be undone
- 2Reversible decisions are made quickly by high-judgment individuals or small teams
- 3Irreversible decisions require deep analysis, broad consultation, and careful consideration
- 4Most organizations treat too many decisions as irreversible, resulting in slowness and lost innovation
When to Use
Use this framework for every strategic or operational decision. Speed up reversible decisions with 70% data and small teams. Slow down irreversible decisions with full analysis and broad consensus. Avoid treating reversible decisions as irreversible, it will kill execution speed and experimentation. Avoid treating irreversible decisions as reversible, the risk of expensive mistakes is too high.
Step-by-Step Guide
Classify the Decision
Ask how much it would cost to reverse this decision in 3-6 months. If the cost is low (time, money, reputation), mark it as reversible. If the cost is high or impossible to reverse, mark it as irreversible.
Determine Information Threshold
For reversible decisions, gather 60-70% of ideal information then decide. For irreversible decisions, gather 90%+ information and conduct complete scenario analysis.
Choose Decision-Maker
Reversible decisions are delegated to individuals or small teams with good judgment. Irreversible decisions involve senior leadership and cross-functional consultation.
Execute at Appropriate Speed
Reversible decisions are executed in days or weeks. Irreversible decisions are given weeks or months of analysis time based on complexity.
Setup Feedback Loop
For reversible decisions, set up fast metrics (daily or weekly) for error detection. For irreversible decisions, set up long-term monitoring (monthly or quarterly).
Review and Iterate
Reversible decisions that prove wrong are reversed immediately when data shows a bad direction. Irreversible decisions that prove wrong become expensive lessons for future decisions.
Reversible vs Irreversible Decisions
Overview
Imagine you're standing in front of two doors. The first door is labeled "One-Way" and the second door is labeled "Two-Way." If you go through the one-way door and don't like what you find, you can't go back. If you go through the two-way door and realize you made a mistake, you simply turn around.
The Reversible vs Irreversible Decisions framework helps you identify which door you're facing. Most organizations treat nearly every decision like a one-way door. The result: processes slow down, meetings drag on, and innovation dies from fear of making mistakes.
Jeff Bezos introduced this framework to accelerate Amazon. He called irreversible decisions Type 1 and reversible decisions Type 2. The principle is simple: move fast on Type 2 decisions, be careful with Type 1 decisions. Most decisions are Type 2.
This framework transforms how teams make decisions. Instead of waiting for perfect consensus, teams learn to identify which decisions deserve execution today with 70% data versus which decisions require months of deep analysis.
Origin Story
Jeff Bezos wrote Amazon's 2015 shareholder letter with a critical observation: large organizations tend to slow down because they treat all decisions with heavy processes. He saw this pattern at Amazon itself. As the company grew, simple decisions that once took one meeting now required layered approvals and lengthy analysis.
Bezos distinguished between two types of decisions. Type 1 is consequential decisions that are difficult or impossible to reverse. Type 2 is decisions that can be changed easily. He wrote: if you walk through a one-way door and don't like what you see on the other side, you can't get back to where you were before. These decisions must be made methodically, carefully, slowly, with great deliberation and consultation.
Conversely, most decisions are two-way doors. If you make a suboptimal Type 2 decision, you don't have to live with the consequences for long. You can reopen the door and go back through. Type 2 decisions can and should be made quickly by high-judgment individuals or small teams.
Bezos gave the example of opening Amazon's platform to third-party sellers in the early 2000s. Many Amazon executives opposed it. They worried external sellers would steal customers, lower quality, and damage Amazon's brand. Bezos saw this as a Type 2 decision. If it failed, Amazon could shut down the program. If it succeeded, the potential was huge.
The decision was made. The result: the marketplace grew exponentially. By 2018, third-party sellers contributed 58% of Amazon's total physical GMV, up from 3% in 1999. Bezos wrote in his 2019 shareholder letter: "Third-party sellers are kicking our first-party butt. Badly."
The key lesson: speed on reversible decisions creates experiments that generate valuable insights. Slowness kills momentum.
Core Principles
1. Reversal Cost Determines Decision Type
The fastest way to identify decision type is to ask: what would it cost to reverse this in 3-6 months? Cost can be money, time, reputation, or organizational momentum.
Examples of irreversible decisions: building a manufacturing plant (large capital, can't sell quickly), acquiring a company (complex integration), or launching a hardware product (supply chain commitments).
Examples of reversible decisions: testing new pricing for a small segment (can roll back next week), changing website copy (deploy in hours), or adopting a new internal tool (data migration relatively easy).
If reversal cost is low, the decision is reversible. If reversal cost is high or impossible, the decision is irreversible.
2. Information Thresholds Differ
For reversible decisions, wait until you have 60-70% of ideal information, then decide. Waiting for 90% means you're too slow. Bezos wrote: most decisions should probably be made with somewhere around 70% of the information you wish you had. If you wait for 90%, in most cases, you're probably being slow.
For irreversible decisions, gather 90%+ of information. Conduct scenario analysis, consult experts, and do deep financial modeling. The extra time for research is far cheaper than a major decision mistake.
This framework frees teams from the illusion of "perfect data." Reversible decisions don't need perfection. Irreversible decisions require maximum care.
3. Speed as Competitive Advantage
Organizations that move fast on reversible decisions gain an experimentation advantage. They can test 10 hypotheses in the time competitors use to analyze 1 hypothesis.
Amazon launches thousands of experiments per year. Most fail. That's fine, because reversible decisions can be canceled quickly. Successful experiments scale. Failed experiments get killed.
Speed creates a learning loop. The more reversible decisions you execute, the more data you collect, the better your team's judgment becomes.
4. Avoid Heavy Processes for Light Decisions
The biggest problem in large organizations is treating Type 2 decisions like Type 1. Extended meetings, layered approvals, and analysis paralysis for decisions that should take 1 hour.
Bezos wrote: as organizations get larger, there seems to be a tendency to use the heavy-weight Type 1 decision-making process on most decisions, including many Type 2 decisions. The end result: slowness, unthoughtful risk aversion, failure to experiment sufficiently, and consequently diminished invention.
This framework forces organizations to ask: is this meeting really necessary? Does this approval add value or just bureaucracy? Reversible decisions must move fast.
Implementation Steps
- Classify the Decision: For every important decision, start with the question: "What would it cost to reverse this decision in 3-6 months?" Write down costs in terms of money, engineering time, leadership time, brand reputation, or team momentum. If total reversal cost is low (for example, less than $10K or 2 weeks of engineering time), mark as reversible. If high or impossible, mark as irreversible. Create a decision spreadsheet with columns: Decision, Type (R/I), Reversal Cost, Decision-Maker, Timeline.
- Determine Information Threshold: For reversible decisions, ask: "What are the 3 most important data points I need to decide?" Gather that data in 1-3 days, then decide. Don't wait for perfect analysis. For irreversible decisions, create a complete list of needed data: competitor analysis, financial scenarios, legal consultation, customer feedback, and technical feasibility. Allow 2-4 weeks for deep research. Create a 6-page decision document Amazon-style for group review.
- Choose Decision-Maker: Reversible decisions are delegated to the lowest level with sufficient context. Product managers can decide A/B tests, senior engineers can decide which library to use, marketing managers can decide ad copy. Irreversible decisions involve senior leadership. VPs or C-level review decisions that affect organizational structure, platform architecture, or major capital commitments. Document who the decision-maker is for each category of decisions.
- Execute at Appropriate Speed: Reversible decisions go from idea to execution in days or at most 2 weeks. Use standups or Slack for quick sync, not formal meetings. Irreversible decisions get appropriate analysis time. Don't rush, but also don't fall into analysis paralysis. Set explicit deadlines: "We will decide this no later than 4 weeks from now with data X, Y, Z."
- Setup Feedback Loop: For reversible decisions, install metrics that update daily or weekly. If metrics show bad trends for 1-2 weeks, roll back or iterate. Create a simple dashboard with 2-3 key metrics. For irreversible decisions, set up long-term monitoring with monthly or quarterly reviews. Track lagging indicators like revenue, retention, or NPS. Document learnings for similar future decisions.
- Review and Iterate: Every month, review reversible decisions made: what percentage succeeded, what percentage rolled back, average time from idea to execution. If too many rollbacks (>50%), maybe the information threshold needs raising. If too few rollbacks (<10%), maybe the team is still too conservative. For irreversible decisions, conduct post-mortems 6 months after execution. What could have been predicted better? What remained unpredictable? Update the playbook for similar decisions.
Brief Case Studies
Amazon Prime Launch (Irreversible): The decision to launch Amazon Prime in 2005 was Type 1. No spreadsheet supported it. Every financial analysis showed the program would lose money. Bezos relied on intuition: if customers get free shipping, they'll shop more often. The decision was made after long deliberation with the leadership team. The result: Prime became one of the world's largest loyalty programs with 200 million+ members.
SaaS Startup Pricing Test (Reversible): A B2B collaboration platform tested a 20% price increase for new customers in Southeast Asia. Total affected users: 1,000. Timeline: 4 weeks. Metrics tracked: signup rate, conversion rate, churn rate. Result: signup rate dropped 8%, conversion rate held steady, churn increased 5%, revenue per user increased 18%. Net positive. The decision was rolled out to all new regions in 1 month. Total time from idea to global rollout: 8 weeks.
Microservices Migration (Irreversible): A fintech company with 500 engineers decided to migrate from monolith to microservices. This decision was irreversible because it involved rewriting core architecture, retraining the entire engineering organization, and changing the deployment pipeline. Decision-making process: 3 months of analysis involving 20+ senior engineers and architects, 6 months pilot with 2 services, 18 months full migration. Result: deployment frequency increased 10x. The trade-off that emerged was that operational complexity also increased significantly.
When to Use and Avoid
Use this framework for every important strategic or operational decision. Speed up reversible decisions by giving autonomy to small teams, setting up fast feedback loops, and expecting that rollbacks are normal. Slow down irreversible decisions with deep analysis, cross-functional consultation, and complete documentation for future learning.
Avoid treating reversible decisions like irreversible ones. Don't ask for 5 layers of approval to change a button color or ad copy. Avoid treating irreversible decisions like reversible ones. Don't decide organizational restructuring or database migration in 1 meeting without analysis.
Watch out for gray areas. Some decisions look reversible but have second-order effects that are irreversible. Example: hiring someone looks reversible (you can fire them), but the cultural impact of a bad hire can be permanent. For gray areas, treat as irreversible until proven otherwise.
Practical Advice
Create a simple checklist for every important decision: (1) Decision type: reversible or irreversible? (2) Reversal cost: how much in dollars and time? (3) Information needed: what are the 3-5 critical data points? (4) Decision-maker: who has the context and authority? (5) Timeline: when must this be decided? (6) Feedback mechanism: what metrics will be tracked?
Document reversible decisions in lightweight format: Slack message or 1-pager. Document irreversible decisions in complete format: 6-pager with problem statement, data, alternatives, recommendation, and risks. Create a searchable decision repository for future reference.
Train teams to identify decision types. In meetings, ask: "Is this Type 1 or Type 2?" If Type 2, challenge: "Why didn't we decide this last week?" If Type 1, ensure there's enough time for analysis. This practice builds muscle memory.
Set up decision review rituals. Every quarter, review 5-10 biggest decisions: was initial classification correct, did execution speed match type, did outcome match expectations. These learnings improve organizational judgment quality over time.
Finally, remember this framework is a tool, not a rigid rule. Context matters. Decisions that are reversible for a large company can be irreversible for a startup with limited cash runway. Adjust thresholds based on company stage, risk tolerance, and competitive landscape.
With the Reversible vs Irreversible Decisions framework, organizations can move fast on what matters while staying careful with big bets. The result: execution speed increases, innovation improves, and teams feel more empowered to make decisions.
Use Cases
Startup Product Strategy
Determining which features to build quickly versus platform architecture that is irreversible.
→A SaaS startup categorized UI changes as reversible (deploy in 2 weeks, easy rollback) while database migration was considered irreversible (requires 3 months analysis and 6 months execution). Result: feature velocity increased 40% because the team stopped overthinking UI decisions.
E-commerce Geographic Expansion
Differentiating test markets (reversible) from building fulfillment centers (irreversible).
→A regional e-commerce company tested a new country market with local dropship partners for 6 months. After GMV reached the threshold, they invested in a permanent warehouse. This approach saved $2M from premature expansion risk.
Hiring and Team Structure
Short-term contract hiring is reversible; C-level executive hiring is irreversible.
→A tech company hired product managers on 3-month contracts to validate fit before making full-time offers. For VP Engineering, an 8-round interview process with 15 stakeholders took 2 months. PM turnover dropped 60% and VP hires succeeded 90%.
Pricing and Monetization
Price experiments for small segments are reversible; changing the business model is irreversible.
→A B2B SaaS platform tested a 20% price increase for new customers in one region (1,000 users). Churn increased 5% but revenue per user increased 18%, net positive. The decision was rolled out globally in 1 month. Total time from idea to full execution: 6 weeks.
Technology Infrastructure
Choosing a new library or tool is reversible; microservices architecture is irreversible.
→An engineering team replaced a logging library in 2 sprints due to poor performance (reversible). Meanwhile, the decision to migrate from monolith to microservices took 18 months of planning and execution, involving the entire engineering organization (irreversible).