**Most decisions don't deserve the amount of stress you give them.**
Some decisions genuinely require days or even weeks of careful consideration.
But most decisions don't.
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 more effective decision-making process begins with one question:
**If we're wrong, how easily can we reverse this decision?**
Reversible decisions can be changed, tested, or undone at relatively low cost. Irreversible decisions are those where changing course is difficult, costly, or impossible.
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.**
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 act, see what happens, learn from the result, and adjust.
Examples include:
* Trying a different meeting format
* Adjusting an internal workflow
* Launching a limited marketing experiment
* Testing a new process with one team
* Delegating a responsibility
* Experimenting with a pricing variation
An **irreversible decision** carries consequences that make reversal difficult or costly.
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 rule is simple:
**As reversibility decreases, scrutiny should increase. As reversibility increases, authority should move toward the person closest to the relevant information.**
This principle forms the foundation of the **Decision Reversibility Framework.**
## Why Are Reversible Decisions So Easy to Overthink?
Reversible decisions often don't feel reversible in the moment.
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 considers testing an idea but wants more evidence before acting.
So uncertainty triggers more analysis.
One more conversation.
Another spreadsheet.
Another perspective.
One more approval.
At some point, the cost of continued deliberation exceeds the likely cost of a mistake.
This creates what we can call **decision latency**: the time lost after enough information exists but before action occurs.
One delay may not matter much. Repeated across an organization, those delays become consequential.
When low-risk decisions repeatedly require senior approval, leadership itself becomes a bottleneck.
The organization hasn't necessarily reduced risk.
It may have merely centralized uncertainty and delay.
## The Decision Reversibility Framework
Before asking, **"What should we decide?"**, classify the decision using 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.
Reversibility is a spectrum.
The greater the cost of reversing course, the more scrutiny the original decision deserves.
### 2. What Would Failure Actually Cost?
Separate real downside from emotional discomfort.
A small experiment that fails might simply create some additional work.
The downside of a strategic decision can include significant financial loss, legal exposure, operational disruption, or reputational damage.
Ask:
**What is the actual consequence if this fails?**
The size of the downside should influence how much uncertainty you're willing to accept.
A limited downside allows greater speed.
When the downside is significant, greater scrutiny is appropriate.
### 3. How quickly will reality give us feedback?
Sometimes acting generates better information than analyzing further.
Test a sales script and you more info may begin receiving useful reactions almost immediately.
You can pilot a different meeting format and quickly determine whether it improves the team's work.
When feedback is available quickly, you can move away from:
**Analyze → Analyze → Analyze → Decide**
to:
**Decide → Test → Learn → Adjust**
With reversible decisions, action is more than execution.
**Action generates information.**
### 4. Can we reduce the blast radius?
Many decisions can begin on a much smaller scale.
Test the workflow with one team.
Launch first to a small group of customers.
Test 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 Should Really Own This Decision?
This is where traditional decision-making frameworks often stop short.
If the decision can be reversed cheaply, produces fast feedback, and has limited downside, why should senior leadership need to approve it?
Often, it doesn't.
Authority should move closer to the people who understand the situation best.
The leadership question then shifts from:
**"What decision should I make?"**
toward:
**"Why does this decision require me?"**
At that point, decision making becomes an issue of power architecture.
## A Decision Architecture Matrix
Match the decision process to both reversibility and the cost of being wrong.
| Decision Type | Reversibility | Cost of Error | Best Response | | |
| ---------------------- | ------------- | ------------- | -------------------------------- | ----------------------------------------------------- | ------------------------------------------- |
| **Experiment** | High | Low | Move quickly and test |
| **Delegated Decision** | High | Moderate | Create boundaries and delegate |
| **Strategic Bet** | Low | Moderate–High | Increase analysis before committing |
| **Critical Decision** | Very low | High | Slow down and increase scrutiny |
The mistake is using the highest level of scrutiny for almost every decision.
Additional analysis is not always the same as better decision making.
Often, it simply delays action.
## How Much Information Do You Need Before Deciding?
For reversible decisions with contained downside, waiting for complete 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 underlying idea is straightforward:
**Reversible decisions don't require certainty. They require guardrails.**
If you can test cheaply, receive feedback quickly, and reverse course without serious damage, additional analysis may be less valuable than action.
Testing becomes part of decision making rather than something that happens afterward.
## Why Leaders Should Replace Approvals With Guardrails
This is where the framework becomes especially important for leaders.
Suppose your team repeatedly asks permission before acting.
You may think:
**They need to become more decisive.**
But their hesitation may be rational.
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 decision architecture.
Instead of approving individual decisions, establish decision rights:
"You can resolve customer issues below this financial threshold."
"Process changes can be tested within your team for a 30-day period."
"Experiments don't require additional approval unless they affect legal, security, or brand standards."
Authority now has clear boundaries.
People don't need permission for every action. They need judgment within an established territory.
**Approval manages decisions individually.**
**Architecture determines how decisions happen again and again.**
Only the second approach 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 would failure cost?**
Identify the real consequences.
**3. When will we get feedback?**
Determine when reality will provide useful feedback.
**4. Can we shrink the bet?**
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 choose the appropriate action:
**Easy to reverse + low cost of error → Decide.**
**Reversible + uncertain outcome → Experiment.**
**Reversible + better information elsewhere → Delegate.**
**Irreversible + costly failure → Increase scrutiny.**
Most decisions become easier once you stop treating them equally.
## Why Decision Speed Creates a Power Advantage
Fast decision making isn't always the objective.
That would confuse speed with judgment.
The objective is to give every decision the level of scrutiny its downside deserves.
Certain decisions genuinely deserve research, debate, scenario planning, and deep scrutiny.
Many others simply deserve an experiment.
The framework also reveals something deeper about leadership.
If every important decision comes to you for approval, it may feel like evidence of your authority.
From a systems perspective, it may indicate the opposite.
You have created organizational dependency on your presence.
A leader's power should not be measured by how many decisions they personally control.
A stronger measure is whether the organization can repeatedly make sound decisions **without depending on constant senior approval.**
Reversibility therefore matters far beyond individual decision making.
It determines where authority should sit.
It determines how quickly information becomes action.
And it determines whether an organization operates through judgment or permission.
So before you ask:
**"What should we decide?"**
begin with a better question:
**"How reversible is the decision, and who is best positioned to make it?"**
Most decisions don't deserve more stress.
They need better architecture.
*The Architecture of POWER* explores how decision rights, authority, incentives, information, and invisible systems determine how power actually works inside organizations.
**Real power isn't just about who decides. It's built into the architecture through which decisions get made.**