**We give most decisions more stress than they actually deserve.**
Some decisions genuinely require days or even weeks of careful consideration.
But most decisions don't.
Yet we often approach both categories as though they require the same decision-making process. 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 easily can this decision be reversed?**
A reversible decision can usually be changed, tested, adjusted, or undone without significant cost. Irreversible decisions, by contrast, are costly, difficult, or sometimes impossible to undo.
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 Is the Difference Between Reversible and Irreversible Decisions?
A **reversible decision** gives you the ability to change course at relatively low cost. You can decide, observe what happens, learn, and adjust.
Reversible decisions might include:
* Testing a new meeting format
* Adjusting an internal workflow
* Launching a limited marketing experiment
* Running a process pilot with a single team
* Delegating a specific responsibility
* Running a limited pricing test
A decision becomes **irreversible** when changing course would be difficult, expensive, or impossible.
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 principle forms the foundation of the **Decision Reversibility Framework.**
## Why Do People Overthink Reversible Decisions?
Reversible decisions rarely feel reversible while we're making them.
A simple process change can lead a manager to imagine every possible failure.
A leader may hesitate to delegate because of concerns about control.
An entrepreneur may postpone a small experiment because the available evidence doesn't yet feel sufficient.
So uncertainty triggers more analysis.
Another meeting.
One more spreadsheet.
Another opinion.
Another layer of approval.
Eventually, delaying the decision becomes more expensive than making an imperfect one.
This creates **decision latency**: the gap between having enough information to act and actually acting.
A single delayed decision may have little effect. Hundreds create a system problem.
And when reversible decisions repeatedly travel upward for approval, senior leadership becomes a bottleneck.
Risk hasn't actually disappeared.
Instead, it has concentrated hesitation at the top.
## The Five Questions for Classifying a Decision
Before asking **"What should we do?"**, classify the decision with five questions.
### 1. How difficult is the decision to reverse?
The question isn't simply whether reversal is possible.
Instead, determine the real cost of reversing course.
Changing a meeting structure is easy to undo. Replacing an enterprise-wide technology system might technically be reversible, but the cost of reversal could be enormous.
Decisions aren't simply reversible or irreversible; reversibility exists on a continuum.
As reversal becomes more costly, the case for deeper deliberation becomes stronger.
### 2. What Would Failure Actually Cost?
Separate real downside from emotional discomfort.
A failed experiment might create two weeks of additional work.
The downside of a strategic decision can include significant financial loss, legal exposure, operational disruption, or reputational damage.
The question is:
**If this fails, what do we actually lose?**
Your answer should determine how much uncertainty is acceptable.
Low downside allows faster action.
When the downside is significant, greater scrutiny is appropriate.
### 3. How Fast Will You Get Feedback?
Sometimes acting generates better information than analyzing further.
Test a sales script and you may begin receiving useful reactions almost immediately.
A new meeting structure can be tested for a month and evaluated against productivity.
When feedback arrives quickly, the decision-making process can change from:
**Analyze → Analyze → Analyze → Decide**
to:
**Decide → Test → Learn → Adjust**
For reversible decisions, action isn't merely execution.
**Action becomes a source of information.**
### 4. Can You Make the Decision Smaller?
You don't have to implement every decision across the entire organization immediately.
Test the workflow with one team.
Launch first to a small group of customers.
Give the policy a limited 30-day trial.
Give someone decision authority within predetermined limits.
Instead of demanding certainty, contain the downside.
**High uncertainty doesn't always require more analysis. Sometimes it requires a smaller bet.**
This can turn seemingly high-risk decisions into manageable experiments.
### 5. Who Should Really Own This Decision?
Many decision frameworks fail to ask this question.
If the downside is contained and the decision is easy to reverse, why should it travel to the top of the organization?
In many cases, it shouldn't.
The decision should move toward the person with the best information.
That changes the leadership question from:
**"What should I decide?"**
toward:
**"Why am I the person deciding this?"**
That is ultimately a question of power.
## The Reversibility Decision Matrix
Use two variables—reversibility and cost of error—to choose the appropriate decision process.
| Decision Type | Reversibility | Cost of Error | Best Response | | |
| ---------------------- | ------------- | ------------- | -------------------------------- | ----------------------------------------------------- | ------------------------------------------- |
| **Experiment** | High | Low | Decide quickly and test |
| **Delegated Decision** | High | Moderate | Set guardrails and delegate |
| **Strategic Bet** | Low | Moderate–High | Analyze carefully, challenge assumptions, then commit |
| **Critical Decision** | Very low | High | Increase scrutiny and deliberate carefully |
The mistake is using the highest level of scrutiny for almost every decision.
Additional analysis is not always the same as better decision making.
Sometimes it simply produces slower ones.
## How Much Information Do You Need Before Deciding?
Reversible, low-downside decisions generally don't require complete information.
A useful principle is to act once you have enough information to make a reasonably informed choice and enough protection to survive being wrong.
The distinction echoes Jeff Bezos's description of reversible "two-way door" decisions and his argument that waiting for nearly complete information often makes organizations too slow.
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.
The experiment itself becomes part of the decision process.
## Replace Approvals With Guardrails
For leaders, this is where the framework becomes especially consequential.
Suppose your team repeatedly asks permission before acting.
You may think:
**They need more confidence.**
But the behavior may make perfect sense within the existing system.
When people aren't sure what they are authorized to decide, escalation protects them from making the wrong call.
Encouraging decisiveness alone won't solve the problem.
Change the architecture.
Instead of approving individual decisions, establish decision rights:
"You have authority to resolve customer issues below this financial limit."
"You can test process changes within your team for 30 days."
"You can run experiments provided they don't 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 decision making framework within an established territory.
**Approval controls decisions one at a time.**
**Architecture determines how decisions are made repeatedly.**
Architecture is the one that scales.
## Classify a Decision in Two Minutes
Spend two minutes classifying your next significant decision before trying to solve it.
Run through these questions:
**1. How reversible is it?**
Could we change direction without significant damage?
**2. What is the downside?**
Define the actual downside.
**3. When will we get feedback?**
Estimate when the decision will begin producing evidence.
**4. Can we shrink the bet?**
Reduce, pilot, stage, or limit the initial 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 + limited downside → Decide.**
**Reversible + uncertain outcome → Experiment.**
**Reversible + better information elsewhere → Delegate.**
**Hard to reverse + high downside → Deliberate.**
Most decisions become easier once you stop treating them equally.
## Better Decision Architecture Creates Speed
The goal isn't to make every decision quickly.
That would create recklessness.
Better decision making means matching the process to the consequences.
Certain decisions genuinely deserve research, debate, scenario planning, and deep scrutiny.
Many others simply deserve an experiment.
There is, however, a larger implication for leadership.
If every important decision comes to you for approval, it may feel like evidence of your authority.
Structurally, the opposite may be true.
You have created organizational dependency on your presence.
Real organizational power isn't measured by the number of decisions that require a leader's approval.
A stronger measure is whether the organization can repeatedly make sound decisions **without depending on constant senior approval.**
This is what makes decision reversibility an organizational issue rather than merely a personal productivity technique.
It helps determine where authority belongs.
It determines how quickly information becomes action.
And it determines whether an organization operates through judgment or permission.
The next time you're facing a decision, don't begin with:
**"What is the right decision?"**
ask:
**"How reversible is the decision, and who is best positioned to make it?"**
Most decisions don't need more anxiety or deliberation.
They deserve better 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.
**Power isn't only about who makes the decision. It's about how the system makes decisions.**