**Most decisions don't deserve nearly as much stress as you give them.**
Some decisions genuinely require days or even weeks of careful consideration.
Most do not.
The problem is that we often use the same decision-making process for both. A small operational experiment can receive the same scrutiny as a major strategic commitment, even though their consequences are completely different.
The consequences aren't the same.
A better approach starts with 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 are difficult, expensive, or impossible to reverse.
Reversibility should influence how long you deliberate, how quickly you act, and—critically—**who has the authority to decide.**
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** is one you can change without creating significant damage. You can decide, observe what happens, learn, and adjust.
Common examples include:
* Testing a new meeting format
* Changing a workflow
* Running a small marketing experiment
* Testing a new process with one team
* Delegating a specific responsibility
* Running a limited pricing test
An **irreversible decision** carries consequences that make reversal difficult or costly.
Selling a company, signing a major long-term contract, making a large capital commitment, or risking permanent reputational damage are examples of decisions that may be difficult to reverse.
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.**
I call this approach the **Decision Reversibility Framework.**
## Why Do We Overthink Reversible Decisions?
A decision may be reversible in reality while feeling permanent in the moment.
A manager thinks about changing a process and immediately imagines the possible problems.
A leader may hesitate to delegate because of concerns about control.
An entrepreneur delays an experiment while waiting for additional evidence.
So uncertainty triggers more analysis.
Another meeting.
Another analysis.
Another opinion.
Another approval.
At some point, the cost of continued deliberation exceeds the likely cost of a mistake.
The result is **decision latency**: the unnecessary gap between knowing enough to act and actually making the decision.
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.
It has centralized hesitation.
## 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?
Don't stop at asking whether the decision can technically be reversed.
Ask what reversal would 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.
Reversibility exists on a spectrum.
As reversal becomes more costly, the case for deeper deliberation becomes stronger.
### 2. What Would Failure Actually Cost?
Separate consequences from discomfort.
Failure in a small experiment may mean a few weeks of lost effort.
A failed strategic bet can create serious financial, legal, operational, or reputational consequences.
So ask:
**If this fails, what do we actually lose?**
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?
Certain decisions teach you more through action than through continued deliberation.
A new sales script can generate customer feedback within days.
You can change a meeting format for a month and measure whether it improves productivity.
When reality provides fast feedback, the decision process can shift from:
**Analyze → Analyze → Analyze → Decide**
and toward:
**Decide → Test → Learn → Adjust**
With reversible decisions, action is more than execution.
**Action itself produces evidence.**
### 4. Can we reduce the blast radius?
A decision doesn't have to be implemented everywhere at once.
Test the workflow with one team.
Test the product with a limited customer segment.
Give the policy a limited 30-day trial.
Delegate authority within defined limits.
Rather than trying to remove uncertainty, make being wrong less expensive.
**High uncertainty doesn't always require more analysis. Sometimes it requires a smaller bet.**
Limiting exposure turns many uncertain decisions into manageable tests.
### 5. Who Should Really Own This Decision?
This is the question website most decision-making frameworks miss.
If the downside is contained and the decision is easy to reverse, why should it travel to the top of the organization?
Frequently, there is no reason for it to.
The person closest to the relevant information should usually have greater authority to act.
The leadership question then shifts from:
**"What decision should I make?"**
into:
**"Why does this decision require me?"**
That is ultimately a question of power.
## A Decision Architecture Matrix
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 | Decide quickly and test |
| **Delegated Decision** | High | Moderate | Create boundaries and delegate |
| **Strategic Bet** | Low | Moderate–High | Analyze carefully, challenge assumptions, then commit |
| **Critical Decision** | Very low | High | Increase scrutiny and deliberate carefully |
A common mistake is treating almost every choice like a **Critical Decision.**
Additional analysis is not always the same as better decision making.
Sometimes it simply produces slower ones.
## When Should You Make the Decision?
Reversible, low-downside decisions generally don't require complete information.
Act when you know enough to make a reasonable decision and the downside of being wrong remains survivable.
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 broader lesson is this:
**The goal with reversible decisions isn't certainty. It's controlled downside.**
When the cost of testing is low and the decision can easily be reversed, acting may teach you more than another round of analysis.
Experimentation becomes part of the decision-making process.
## Why Leaders Should Replace Approvals With Guardrails
The leadership implications become clear at this point.
Consider a team that repeatedly waits for approval before acting.
You may think:
**They need to become more decisive.**
But the behavior may make perfect sense within the existing system.
When employees don't know the boundaries of their authority, seeking permission is a rational form of protection.
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."
"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."
Now authority has boundaries.
Instead of constantly seeking permission, people can exercise judgment within an established decision territory.
**An approval system controls individual decisions.**
**Architecture shapes the system that produces decisions repeatedly.**
Only one of those scales.
## A Two-Minute Test for Better Decisions
Before you start debating your next decision, give yourself two minutes to classify it.
Start with five questions:
**1. How reversible is it?**
Can we undo the decision without major consequences?
**2. What is the downside?**
Calculate what being wrong would actually cost.
**3. How quickly will we know?**
Identify how quickly useful feedback will arrive.
**4. Can we limit the first commitment?**
Find a way to test the decision with less exposure.
**5. Who should decide?**
Put authority as close as practical to the best information.
Then match the decision to the appropriate response:
**Reversible + low downside → Decide.**
**Reversible + uncertain outcome → Experiment.**
**Reversible + better information elsewhere → Delegate.**
**Irreversible + significant downside → Deliberate.**
Decision making becomes easier when you stop treating every decision the same.
## Why Decision Speed Creates a Power Advantage
The objective isn't speed at all costs.
That would confuse speed with judgment.
The goal is to give each decision the amount of attention its consequences justify.
High-consequence decisions may require research, dissent, scenario analysis, and careful deliberation.
Other decisions need little more than a controlled test.
The framework also reveals something deeper about leadership.
If every meaningful decision eventually reaches your desk, you may feel powerful because everything requires your approval.
Structurally, the opposite may be true.
You have created organizational dependency on your presence.
Real organizational power isn't demonstrated by how many decisions a leader controls.
It is demonstrated by whether the organization can repeatedly make good decisions **without requiring that leader's constant intervention.**
That is why reversibility matters at the organizational level, not just the personal one.
It shapes where decision-making authority should be located.
It determines how quickly information becomes action.
And it helps determine whether the organization runs on judgment or permission.
Before trying to identify the right choice, pause before asking:
**"What should we decide?"**
start with:
**"How difficult would this be to reverse—and where should the decision authority sit?"**
Most decisions don't deserve more stress.
They deserve better architecture.
*The Architecture of POWER* explores how decision rights, authority, incentives, information, and invisible systems determine how power actually works inside organizations.
**Power isn't just who gets to decide. It's how the system decides.**