**Most decisions don't deserve nearly as much stress as you give them.**
A small number of decisions justify days or weeks of serious deliberation.
But most decisions don't.
The problem is that we often use the same decision-making process for both. We often deliberate over minor operational experiments as though they carry the same consequences as major strategic commitments.
They do not.
A stronger approach starts by classifying the decision with one question:
**How easily can this decision be reversed?**
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.
The degree of reversibility should determine the level of scrutiny, the speed of action, and **who should hold the decision-making authority.**
At that point, the issue is no longer just decision making. It becomes decision architecture.
## What Makes a Decision Reversible or Irreversible?
A **reversible decision** gives you the ability to change course at relatively low cost. You can decide, observe what happens, learn, and adjust.
Examples of reversible decisions include:
* Experimenting with a new meeting structure
* Testing a different workflow
* Launching a limited marketing experiment
* Running a process pilot with a single team
* Delegating a responsibility
* Running a limited pricing test
An **irreversible decision** creates consequences that cannot easily or cheaply be reversed.
Examples include selling a business, entering a major long-term agreement, committing substantial capital, or taking an action that could permanently harm trust or reputation.
The logic is straightforward:
**The harder a decision is to reverse, the more scrutiny it deserves. The easier it is to reverse, the closer the authority should move to the person with the best information.**
I call this approach the **Decision Reversibility Framework.**
## Why We Spend Too Much Time on Reversible Decisions
Even reversible decisions can feel permanent while we're deciding.
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 may postpone a small experiment because the available evidence doesn't yet feel sufficient.
Uncertainty then produces more analysis.
Another discussion.
One more spreadsheet.
One more opinion.
One more approval.
Eventually, delaying the decision becomes more expensive than making an imperfect one.
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.
When reversible decisions continually move upward for approval, leaders eventually become organizational bottlenecks.
This does not necessarily make the organization safer.
It may have merely centralized uncertainty and delay.
## The Five Questions for Classifying a Decision
Before solving the decision itself, classify it using five questions.
### 1. How difficult is the decision to reverse?
Don't treat reversibility as a yes-or-no question.
Instead, determine the real cost of reversing course.
A new meeting format can be reversed quickly. A company-wide technology implementation may technically be reversible but financially and operationally painful to undo.
Reversibility is a spectrum.
The greater the cost of reversing course, the more scrutiny the original decision deserves.
### 2. What Happens If You're Wrong?
Distinguish actual consequences from temporary discomfort.
A failed experiment may cost the team two weeks of extra work.
A failed strategic bet can create serious financial, legal, operational, or reputational consequences.
The question is:
**What is the actual consequence if this fails?**
Your answer should determine how much uncertainty is acceptable.
When the downside is small, you can move faster.
When the downside is significant, greater scrutiny is appropriate.
### 3. How Quickly Will the Decision Produce Information?
Some decisions generate information faster through action than through analysis.
You can test a sales script and begin seeing reactions within days.
You can test a meeting format for several weeks and see whether productivity improves.
Fast feedback allows you to replace this process:
**Analyze → Analyze → Analyze → Decide**
with:
**Decide → Test → Learn → Adjust**
In reversible decisions, action serves another purpose beyond execution.
**Action is information.**
### 4. Can You Make the Decision Smaller?
A new decision doesn't need to be rolled out everywhere at the same time.
Pilot the workflow with one team.
Limit the initial product test to a small customer group.
Run the policy for 30 days.
Delegate authority within defined limits.
Rather than eliminating every uncertainty before acting, reduce the potential cost of failure.
**When uncertainty is high, reduce the size of the bet before increasing the amount of analysis.**
Limiting exposure turns many uncertain decisions into manageable tests.
### 5. Who actually needs to make this decision?
This is the question many decision-making frameworks overlook.
When a decision is reversible, low-cost, fast to test, and limited in downside, does it really require senior approval?
Usually, it doesn't.
The decision should move toward the person with the get more info best information.
This changes the question leaders should ask from:
**"What should I do?"**
toward:
**"Why am I the person deciding this?"**
At that point, decision making becomes an issue of power architecture.
## How to Match the Decision to the Right Process
The right decision process depends largely on reversibility and the potential cost of error.
| Decision Type | Reversibility | Cost of Error | Best Response | | |
| ---------------------- | ------------- | ------------- | -------------------------------- | ----------------------------------------------------- | ------------------------------------------- |
| **Experiment** | High | Low | Act quickly, then test |
| **Delegated Decision** | High | Moderate | Delegate within clear guardrails |
| **Strategic Bet** | Low | Moderate–High | Analyze, challenge, then commit |
| **Critical Decision** | Very low | High | Slow down and increase scrutiny |
The common mistake is applying **Critical Decision behavior** to almost everything.
More analysis doesn't necessarily create better decisions.
Sometimes the only result is a slower organization.
## When Should You Stop Analyzing and Decide?
For reversible decisions with contained downside, waiting for complete information is usually unnecessary.
A useful principle is to act once you have enough information to make a reasonably informed choice and enough protection to survive being wrong.
Jeff Bezos popularized the idea of reversible "two-way door" decisions and has argued that many decisions can be made with around 70% of the information you would ideally want.
The underlying idea is straightforward:
**The goal with reversible decisions isn't certainty. It's controlled downside.**
When testing is inexpensive, feedback is fast, and reversal is manageable, action may produce more value than additional analysis.
Testing becomes part of decision making rather than something that happens afterward.
## Use Guardrails Instead of More Approvals
The leadership implications become clear at this point.
Suppose employees routinely bring decisions to you before taking action.
The obvious diagnosis might be:
**They need to make decisions faster.**
But the behavior may make perfect sense within the existing system.
If decision rights are unclear, asking for approval becomes the safest behavior.
Encouraging decisiveness alone won't solve the problem.
Redesign the architecture.
Rather than approving decisions one by one, define clear decision rights:
"You can resolve customer issues below this financial threshold."
"Process changes can be tested within your team for a 30-day period."
"You can run experiments provided they don't affect legal, security, or brand standards."
People now know where their authority begins and ends.
Instead of constantly seeking permission, people can exercise judgment within an established decision territory.
**Approval manages decisions individually.**
**Decision architecture governs how choices are made repeatedly.**
Only one of those scales.
## The Two-Minute Decision Test
Spend two minutes classifying your next significant decision before trying to solve it.
Run through these questions:
**1. Can it be reversed?**
Can we change course without serious damage?
**2. What would failure cost?**
Define the actual downside.
**3. How quickly will we know?**
Determine when reality will provide useful feedback.
**4. Can we shrink the bet?**
Reduce, pilot, stage, or limit the initial commitment.
**5. Who should decide?**
Give the decision to the person closest to the relevant information whenever practical.
Then act accordingly:
**Easy to reverse + low cost of error → Decide.**
**Easy to reverse + uncertain result → Test.**
**Reversible + better information elsewhere → Delegate.**
**Irreversible + costly failure → Increase scrutiny.**
Decision making becomes easier when you stop treating every decision the same.
## Better Decision Architecture Creates Speed
Fast decision making isn't always the objective.
That would be reckless.
The goal is to give each decision the amount of attention its consequences justify.
Some decisions deserve research, dissent, scenario planning, and careful scrutiny.
Many others deserve a test.
The framework also reveals something deeper about leadership.
When every meaningful choice eventually reaches the leader, that centrality can feel like power.
Structurally, however, the opposite may be happening.
You have created a system that cannot move without you.
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.**
This is what makes decision reversibility an organizational issue rather than merely a personal productivity technique.
It helps establish the appropriate location of decision authority.
It shapes the speed at which information is converted into decisions.
Ultimately, it determines whether people exercise judgment or wait for permission.
The next time you're facing a decision, don't begin with:
**"What should we decide?"**
begin with a better question:
**"How difficult would this be to reverse—and where should the decision authority sit?"**
Most decisions don't need more anxiety or deliberation.
What they need is better decision architecture.
In *The Architecture of POWER*, I explore how decision rights, authority, incentives, information, and invisible systems shape the way power actually works inside organizations.
**Real power isn't just about who decides. It's built into the architecture through which decisions get made.**