**Most decisions don't deserve nearly as much stress as you give them.**
Certain decisions deserve extended analysis and deliberate thought.
Most don't.
The mistake is applying roughly the same decision process to decisions with very different consequences. We deliberate over a major strategic commitment and a small operational experiment as though both carry the same consequences.
They shouldn't.
Better decision making begins by asking one question:
**How difficult would this decision be to undo?**
A decision is reversible when it can be changed or undone at relatively low cost. An irreversible decision creates consequences that may be expensive or impossible to reverse.
That distinction should determine how much analysis a decision receives, how quickly it is made, and—critically—**who should have the power to make it.**
This is where ordinary decision making becomes decision architecture.
## Reversible vs. Irreversible Decisions: What's the Difference?
A **reversible decision** allows you to change course without significant damage. You can act, see what happens, learn from the result, and adjust.
Reversible decisions might include:
* Testing a new meeting format
* Adjusting an internal workflow
* Testing a small marketing initiative
* Piloting a process with one team
* Testing the delegation of a responsibility
* Testing a pricing variation
An **irreversible decision** carries consequences that make reversal difficult or costly.
These decisions might include selling a company, making a substantial long-term financial commitment, entering a binding agreement, or taking an action with lasting reputational consequences.
The underlying principle is straightforward:
**Hard-to-reverse decisions deserve greater scrutiny. Easy-to-reverse decisions should move closer to the people who have the best information.**
This is the core principle behind the **Decision Reversibility Framework.**
## Why Are Reversible Decisions So Easy to Overthink?
Reversible decisions rarely get more info feel reversible while we're making them.
A simple process change can lead a manager to imagine every possible failure.
A leader thinks about delegating authority and begins worrying about losing control.
An entrepreneur considers launching an experiment and wants more evidence before committing.
The natural response to uncertainty becomes additional analysis.
One more conversation.
Another spreadsheet.
Another opinion.
Another layer of approval.
At some point, the cost of continued deliberation exceeds the likely cost of a mistake.
This produces **decision latency**—the delay between having sufficient information and taking action.
One delay may not matter much. Repeated across an organization, those delays become consequential.
If every reversible decision must travel up the hierarchy, senior leadership becomes the constraint.
This does not necessarily make the organization safer.
It has centralized hesitation.
## How the Decision Reversibility Framework Works
Before asking **"What should we do?"**, classify the decision with five questions.
### 1. How Reversible Is the Decision?
Don't simply ask whether reversal is possible.
Ask how much reversing it would actually cost.
A new meeting format can be reversed quickly. A company-wide technology implementation may technically be reversible but financially and operationally painful to undo.
Decisions aren't simply reversible or irreversible; reversibility exists on a continuum.
The greater the cost of reversing course, the more scrutiny the original decision deserves.
### 2. What Would Failure Actually Cost?
Don't confuse discomfort with meaningful consequences.
A failed experiment might create two weeks of additional work.
A failed strategic bet can create serious financial, legal, operational, or reputational consequences.
Ask yourself:
**What is the actual consequence if this fails?**
The actual downside tells you how much uncertainty the decision can tolerate.
When the downside is small, you can move faster.
When the downside is significant, greater scrutiny is appropriate.
### 3. When Will Reality Tell You Whether You're Right?
Some decisions generate information faster through action than through analysis.
Test a sales script and you may begin receiving useful reactions almost immediately.
You can test a meeting format for several weeks and see whether productivity improves.
When reality provides fast feedback, the decision process can shift from:
**Analyze → Analyze → Analyze → Decide**
and toward:
**Decide → Test → Learn → Adjust**
For decisions you can reverse, taking action does more than implement the choice.
**Action itself produces evidence.**
### 4. Can You Make the Decision Smaller?
You don't have to implement every decision across the entire organization immediately.
Start the workflow with a single team.
Launch first to a small group of customers.
Pilot the policy for one month.
Delegate authority within defined limits.
Instead of demanding certainty, contain the downside.
**Before responding to uncertainty with more analysis, see whether you can reduce the size of the commitment.**
This can turn seemingly high-risk decisions into manageable experiments.
### 5. Who Should Really Own This Decision?
This is the question most decision-making frameworks miss.
If the decision can be reversed cheaply, produces fast feedback, and has limited downside, why should senior leadership need to approve it?
Usually, it doesn't.
Decision authority should move toward whoever has the best relevant information.
The leadership question then shifts from:
**"What should I decide?"**
and replaces it with:
**"Why does this decision require me?"**
That is a question about power.
## How to Match the Decision to the Right Process
Use reversibility and cost of error to determine the appropriate decision process.
| Decision Type | Reversibility | Cost of Error | Best Response | | |
| ---------------------- | ------------- | ------------- | -------------------------------- | ----------------------------------------------------- | ------------------------------------------- |
| **Experiment** | High | Low | Decide quickly and test |
| **Delegated Decision** | High | Moderate | Create boundaries and delegate |
| **Strategic Bet** | Low | Moderate–High | Analyze, challenge, then commit |
| **Critical Decision** | Very low | High | Slow the process and apply deeper scrutiny |
Organizations often apply **Critical Decision behavior** to decisions that don't deserve it.
More analysis doesn't necessarily create better decisions.
Sometimes it only creates slower decisions.
## How Much Information Do You Need Before Deciding?
If a decision can be reversed and failure is manageable, waiting for perfect information is usually unnecessary.
You can move once the information is sufficient for an informed decision and the guardrails make failure manageable.
Jeff Bezos has famously described many decisions as reversible "two-way doors" and argued that decisions can often be made with roughly 70% of the information you wish you had.
The deeper principle is this:
**The goal with reversible decisions isn't certainty. It's controlled downside.**
If failure is cheap, feedback arrives quickly, and the decision can be reversed, continued analysis may offer less value than testing.
Testing becomes part of decision making rather than something that happens afterward.
## Why Leaders Should Replace Approvals With Guardrails
For leaders, this is where the framework becomes especially consequential.
Suppose your team repeatedly asks permission before acting.
Your first conclusion might be:
**They need to make decisions faster.**
Yet asking for permission may be the rational response.
If decision rights are unclear, asking for approval becomes the safest behavior.
The solution isn't telling people to be more confident.
Fix the structure.
Replace case-by-case approval with explicit decision rights:
"You can resolve customer issues below this financial threshold."
"You can pilot process changes within your team for up to 30 days."
"Experiments don't require additional approval unless they affect legal, security, or brand standards."
People now know where their authority begins and ends.
People don't need permission for every action. They need judgment within an established territory.
**Approval handles one decision at a time.**
**Architecture shapes the system that produces decisions repeatedly.**
Architecture is the one that scales.
## The Two-Minute Reversibility Test
Spend two minutes classifying your next significant decision before trying to solve it.
Run through these questions:
**1. Can it be reversed?**
Could we change direction without significant damage?
**2. What happens if we're wrong?**
Define the actual downside.
**3. How quickly will we know?**
Identify how quickly useful feedback will arrive.
**4. Can we make the first version smaller?**
Pilot, limit, stage, or test the commitment.
**5. Who should own the decision?**
Give the decision to the person closest to the relevant information whenever practical.
Then choose the appropriate action:
**Reversible + low downside → Decide.**
**Easy to reverse + uncertain result → Test.**
**Reversible + better information elsewhere → Delegate.**
**Irreversible + significant downside → Deliberate.**
Many difficult decisions become simpler once you classify them correctly.
## Decision Speed and the Architecture of Power
The objective isn't speed at all costs.
That would create recklessness.
Better decision making means matching the process to the consequences.
Some decisions justify extensive analysis, opposing viewpoints, scenario planning, and scrutiny.
But many decisions are better handled through experimentation.
But there is a larger leadership implication.
When every meaningful choice eventually reaches the leader, that centrality can feel like power.
Structurally, the opposite may be true.
You may have built an organization that cannot move unless you are involved.
Real organizational power isn't demonstrated by how many decisions a leader controls.
It is demonstrated by whether the system can consistently produce good decisions **without the leader constantly intervening.**
That is why reversibility matters beyond personal decision-making.
It helps establish the appropriate location of decision authority.
It determines how quickly information becomes action.
And it determines whether an organization operates through judgment or permission.
Before trying to identify the right choice, pause before asking:
**"What's the correct decision?"**
start with:
**"How difficult would this be to reverse—and where should the decision authority sit?"**
Most decisions don't require more stress.
They deserve a decision system designed for their actual consequences.
*The Architecture of POWER* examines how decision rights, authority, information, incentives, and invisible structures determine how power actually operates inside organizations.
**Power is not simply who has the authority to decide. It is how the system itself produces decisions.**