**Most decisions don't deserve the amount of stress you give them.**
Some decisions deserve days or weeks of careful thought.
But most decisions don't.
The mistake is applying roughly the same decision process to decisions with very different consequences. A small operational experiment can receive the same scrutiny as a major strategic commitment, even though their consequences are completely different.
They do not.
A better approach starts with one question:
**How difficult would this decision be to undo?**
Reversible decisions can be changed, tested, or undone at relatively low cost. Irreversible decisions, by contrast, are costly, difficult, or sometimes impossible to undo.
That difference should shape the amount of analysis required, the speed of the decision, and—most importantly—**where the authority to make it should sit.**
That is where decision-making becomes decision architecture.
## Reversible vs. Irreversible Decisions: What's the Difference?
A **reversible decision** gives you the ability to change course at relatively low cost. You can make the decision, observe the outcome, and modify your approach as new information appears.
Examples include:
* Testing a new meeting format
* Testing a different workflow
* Running a small marketing experiment
* Testing a new process with one team
* Delegating a specific responsibility
* Experimenting with a pricing variation
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.**
This principle forms the foundation of the **Decision Reversibility Framework.**
## Why Are Reversible Decisions So Easy to Overthink?
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.
Uncertainty then produces more analysis.
One more meeting.
Another analysis.
One more opinion.
One more 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.
One delayed decision may not matter. Hundreds of them do.
When low-risk decisions repeatedly require senior approval, leadership itself becomes a bottleneck.
Risk hasn't actually disappeared.
It has simply 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 treat reversibility as a yes-or-no question.
Ask what changing direction would require.
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.
Think of reversibility as a spectrum rather than a binary category.
The more expensive the reversal, the more deliberation the original decision deserves.
### 2. What Happens If You're Wrong?
Separate consequences from discomfort.
Failure in a small experiment may mean a few weeks of lost effort.
A failed strategic decision might create significant financial, legal, operational, or reputational damage.
Ask yourself:
**What would being wrong genuinely cost us?**
The answer determines how much uncertainty you should tolerate.
When the downside is small, you can move faster.
When the downside is significant, greater scrutiny is appropriate.
### 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.
A new meeting structure can be tested for a month and evaluated against productivity.
Fast feedback allows you to replace this process:
**Analyze → Analyze → Analyze → Decide**
and replace it with:
**Decide → Test → Learn → Adjust**
In reversible decisions, action serves another purpose beyond execution.
**Action is information.**
### 4. Can the First Bet Be Smaller?
You don't have to implement every decision across the entire organization immediately.
Pilot the change within one team.
Test the product with a limited customer segment.
Run the policy for 30 days.
Delegate authority within defined limits.
Instead of demanding certainty, contain the downside.
**Before responding to uncertainty with more analysis, see whether you can reduce the size of the commitment.**
A smaller blast radius can transform a risky decision into a controlled experiment.
### 5. Who Should Really Own 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?
Often, it doesn't.
The decision should move toward the person with the best information.
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.
## The Decision Architecture Matrix
Match the decision process to both reversibility and the cost of being wrong.
| Decision Type | Reversibility | Cost of website Error | Best Response | | |
| ---------------------- | ------------- | ------------- | -------------------------------- | ----------------------------------------------------- | ------------------------------------------- |
| **Experiment** | High | Low | Move quickly and test |
| **Delegated Decision** | High | Moderate | Set guardrails and delegate |
| **Strategic Bet** | Low | Moderate–High | Increase analysis before committing |
| **Critical Decision** | Very low | High | Slow down and increase scrutiny |
A common mistake is treating almost every choice like a **Critical Decision.**
More analysis doesn't necessarily create better decisions.
Often, it simply delays action.
## 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.
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 deeper principle is this:
**Reversible decisions need guardrails more than they need certainty.**
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 then becomes part of how the decision is made.
## Use Guardrails Instead of More Approvals
This is where the Decision Reversibility Framework becomes particularly valuable for leaders.
Suppose your team repeatedly asks permission before acting.
You may think:
**They need to stop asking for permission.**
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.
Redesign the architecture.
Instead of controlling each decision individually, establish clear boundaries of authority:
"You can resolve customer issues below this financial threshold."
"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.
The team doesn't need approval for every decision. It needs sound judgment inside defined guardrails.
**Approval controls decisions one at a time.**
**Architecture determines how decisions are made repeatedly.**
Only the second approach scales.
## The Two-Minute Decision Test
Before your next significant decision, spend two minutes classifying it.
Ask:
**1. How reversible is it?**
Can we undo the decision without major consequences?
**2. What would failure cost?**
Calculate what being wrong would actually cost.
**3. When will we get feedback?**
Identify how quickly useful feedback will arrive.
**4. Can we make the first version smaller?**
Find a way to test the decision with less exposure.
**5. Where should the authority sit?**
Move decision authority toward the best available information.
Then match the decision to the appropriate response:
**Reversible + low downside → Decide.**
**Reversible + uncertainty → Experiment.**
**Easy to reverse + someone else has better information → Delegate.**
**Irreversible + costly failure → Increase scrutiny.**
Many difficult decisions become simpler once you classify them correctly.
## Why Decision Speed Creates a Power Advantage
Fast decision making isn't always the objective.
Speed without judgment would be reckless.
Better decision making means matching the process to the consequences.
High-consequence decisions may require research, dissent, scenario analysis, and careful deliberation.
Many others simply deserve an experiment.
Beyond decision speed, there is a more important leadership implication.
If every meaningful decision eventually reaches your desk, you may feel powerful because everything requires your approval.
But structurally, that apparent power may actually reveal weakness.
You may have built an organization that cannot move unless you are involved.
Real organizational power isn't measured by the number of decisions that require a leader's approval.
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 at the organizational level, not just the personal one.
It determines where authority should sit.
It shapes the speed at which information is converted into decisions.
And it helps determine whether the organization runs on judgment or permission.
Before trying to identify the right choice, pause before asking:
**"Which option is right?"**
ask:
**"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.
*The Architecture of POWER* examines how decision rights, authority, information, incentives, and invisible structures determine how power actually operates inside organizations.
**Power isn't just who gets to decide. It's how the system decides.**