**We give most decisions more stress than they actually deserve.**
Some decisions genuinely require days or even weeks of careful consideration.
Most do not.
Yet we often approach both categories as though they require the same decision-making process. We often deliberate over minor operational experiments as though they carry the same consequences as major strategic commitments.
They do not.
A more effective decision-making process begins with one question:
**How easily can this decision be reversed?**
Reversible decisions allow you to change direction without paying a major price for being wrong. 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.**
This is where ordinary how to make decisions faster decision making becomes decision architecture.
## What Makes a Decision Reversible or Irreversible?
A decision is **reversible** when changing direction does not create serious consequences. You can act, see what happens, learn from the result, and adjust.
Examples of reversible decisions include:
* Trying a different meeting format
* Testing a different workflow
* Launching a limited marketing experiment
* Testing a new process with one team
* Delegating a responsibility
* Testing a pricing variation
An **irreversible decision** creates consequences that are difficult or costly to undo.
Examples might include selling a company, signing a major long-term agreement, making a substantial capital commitment, or taking an action that could permanently damage trust or reputation.
The underlying principle is straightforward:
**The more difficult a decision is to reverse, the more carefully it should be scrutinized. The easier it is to reverse, the closer decision authority should sit to the best available information.**
This is the foundation of what I call the **Decision Reversibility Framework.**
## Why Do People Overthink Reversible Decisions?
A decision may be reversible in reality while feeling permanent in the moment.
A manager considers changing a process and imagines everything that could go wrong.
A leader considers delegating authority and worries about losing control.
An entrepreneur may postpone a small experiment because the available evidence doesn't yet feel sufficient.
Instead of acting, uncertainty creates a demand for more information.
One more conversation.
One more spreadsheet.
Another perspective.
Another layer of approval.
Eventually, the cost of deciding becomes greater than the cost of being wrong.
This produces **decision latency**—the delay between having sufficient information and taking action.
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.
This does not necessarily make the organization safer.
It may have merely centralized uncertainty and delay.
## How the Decision Reversibility Framework Works
Before asking **"What should we do?"**, classify the decision with five questions.
### 1. How Hard Would This Decision Be to Reverse?
Don't treat reversibility as a yes-or-no question.
Ask what changing direction would require.
A new meeting format can be reversed quickly. A company-wide technology implementation may technically be reversible but financially and operationally painful to undo.
Think of reversibility as a spectrum rather than a binary category.
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.
A failed strategic bet can create serious financial, legal, operational, or reputational consequences.
Ask:
**What is the actual consequence if this fails?**
The actual downside tells you how much uncertainty the decision can tolerate.
A limited downside allows greater speed.
High downside justifies deeper scrutiny.
### 3. When Will Reality Tell You Whether You're Right?
For some decisions, action produces useful information faster than additional 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.
When feedback arrives quickly, the decision-making process can change from:
**Analyze → Analyze → Analyze → Decide**
and toward:
**Decide → Test → Learn → Adjust**
In reversible decisions, action serves another purpose beyond execution.
**Action becomes a source of information.**
### 4. Can we reduce the blast radius?
A decision doesn't have to be implemented everywhere at once.
Start the workflow with a single team.
Offer the product to a small customer segment.
Give the policy a limited 30-day trial.
Create defined boundaries for delegated authority.
Instead of trying to eliminate uncertainty before acting, reduce the consequences of being wrong.
**When uncertainty rises, shrink the bet before expanding the analysis.**
This converts many apparently high-risk decisions into manageable experiments.
### 5. Where Should Decision Authority Sit?
This is the question many decision-making frameworks overlook.
If a decision is reversible, relatively inexpensive, quick to produce feedback, and limited in downside, why does it need senior approval?
In many cases, it shouldn't.
Authority should move closer to the people who understand the situation best.
That reframes the leader's question from:
**"What decision should I make?"**
and replaces it with:
**"Who should really have the authority to make this decision?"**
That is ultimately a question of power.
## How to Match the Decision to the Right Process
Match the decision process to both reversibility and the cost of being wrong.
| Decision Type | Reversibility | Cost of Error | Best Response | | |
| ---------------------- | ------------- | ------------- | -------------------------------- | ----------------------------------------------------- | ------------------------------------------- |
| **Experiment** | High | Low | Decide quickly and test |
| **Delegated Decision** | High | Moderate | Delegate within clear guardrails |
| **Strategic Bet** | Low | Moderate–High | Increase analysis before committing |
| **Critical Decision** | Very low | High | Increase scrutiny and deliberate carefully |
The common mistake is applying **Critical Decision behavior** to almost everything.
Increasing analysis doesn't guarantee higher-quality decisions.
Sometimes it only creates slower decisions.
## How Much Information Do You Need Before Deciding?
When a decision is reversible and the downside is contained, complete information is rarely necessary.
Act when you know enough to make a reasonable decision and the downside of being wrong remains survivable.
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 broader lesson is this:
**Reversible decisions need guardrails more than they need certainty.**
If failure is cheap, feedback arrives quickly, and the decision can be reversed, continued analysis may offer less value than testing.
The experiment itself becomes part of the decision process.
## Why Leaders Should Replace Approvals With Guardrails
This is where the Decision Reversibility Framework becomes particularly valuable for leaders.
Imagine that your team continually asks for permission before making decisions.
The obvious diagnosis might be:
**They need to stop asking for permission.**
But that hesitation may actually be rational.
If people don't know where their authority begins and ends, asking permission protects them.
The answer isn't another speech about empowerment.
Change the architecture.
Replace case-by-case approval with explicit decision rights:
"You have authority to resolve customer issues below this financial limit."
"You can test process changes within your team for 30 days."
"Experiments don't require additional approval unless they affect legal, security, or brand standards."
Now authority has boundaries.
Instead of constantly seeking permission, people can exercise judgment within an established decision territory.
**Approval manages decisions individually.**
**Architecture determines how decisions happen again and again.**
One creates dependency. The other creates scale.
## A Two-Minute Test for Better Decisions
Before making your next important decision, take two minutes to classify it.
Ask these five questions:
**1. How reversible is it?**
Could we change direction without significant damage?
**2. What happens if we're wrong?**
Identify the real consequences.
**3. When will we get feedback?**
Estimate when the decision will begin producing evidence.
**4. Can we shrink the bet?**
Find a way to test the decision with less exposure.
**5. Who should decide?**
Give the decision to the person closest to the relevant information whenever practical.
Then choose the appropriate action:
**Reversible + low downside → Decide.**
**Reversible + uncertainty → Experiment.**
**Reversible + expertise elsewhere → Delegate.**
**Irreversible + costly failure → Increase scrutiny.**
Decision making becomes easier when you stop treating every decision the same.
## Decision Speed and the Architecture of Power
The objective isn't speed at all costs.
Speed without judgment would be reckless.
The objective is to give every decision the level of scrutiny its downside deserves.
High-consequence decisions may require research, dissent, scenario analysis, and careful deliberation.
Many others deserve a test.
The framework also reveals something deeper about leadership.
A leader whose approval is required for everything may appear to hold enormous power.
From a systems perspective, it may indicate the opposite.
You have created a system that cannot move without you.
A leader's power should not be measured by how many decisions they personally control.
Real organizational power appears when the system can produce good decisions **without requiring continuous intervention from the person at the top.**
That is why reversibility matters beyond personal decision-making.
It helps establish the appropriate location of decision authority.
It influences how quickly information can turn into action.
Ultimately, it determines whether people exercise judgment or wait for permission.
So before you ask:
**"What should we decide?"**
start with:
**"How reversible is this choice—and who should actually have the authority to decide?"**
Most decisions don't deserve more stress.
They deserve better architecture.
*The Architecture of POWER* reveals how authority, decision rights, incentives, information, and invisible organizational systems shape where power really sits.
**Power is not simply who has the authority to decide. It is how the system itself produces decisions.**