**Most decisions receive far more stress than their consequences justify.**
Certain decisions deserve extended analysis and deliberate thought.
But most decisions don't.
The problem is that we often use the same decision-making process for both. We deliberate over a major strategic commitment and a small operational experiment as though both carry the same consequences.
They don't.
A stronger approach starts by classifying the decision with one question:
**How easily can this decision be reversed?**
A decision is reversible when it can be changed or undone at relatively low cost. Irreversible decisions are difficult, expensive, or impossible to reverse.
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.**
And that is the point where a decision-making problem becomes a question of decision architecture.
## What Makes a Decision Reversible or Irreversible?
A **reversible decision** gives you the ability to change course at relatively low cost. It allows you to make a choice, gather feedback, and change direction if necessary.
Examples of reversible decisions include:
* Experimenting with a new meeting structure
* Adjusting an internal workflow
* Testing a small marketing initiative
* Testing a new process with one team
* Delegating a responsibility
* Testing a pricing variation
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.**
I call this approach the **Decision Reversibility Framework.**
## Why Do We Overthink Reversible Decisions?
Even reversible decisions can feel permanent while we're deciding.
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.
So uncertainty triggers more analysis.
One more conversation.
Another analysis.
One more opinion.
One more 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.
When low-risk decisions repeatedly require senior approval, leadership itself becomes a bottleneck.
The organization hasn't necessarily reduced risk.
It has simply centralized hesitation.
## The Decision Reversibility Framework
Before asking **"What should we do?"**, classify the decision with five questions.
### 1. What Would It Take to Reverse the Decision?
Don't simply ask whether reversal is possible.
Ask what reversal would cost.
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.
Reversibility is a spectrum.
The greater the cost of reversing course, the more scrutiny the original decision deserves.
### 2. What is the actual cost of being wrong?
Don't confuse discomfort with meaningful consequences.
A small experiment that fails might simply create some additional work.
A failed strategic decision might create significant financial, legal, operational, or reputational damage.
So ask:
**What would being wrong genuinely cost us?**
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 sales-script experiment can start producing feedback in a matter of days.
A new meeting structure can be tested for a month and evaluated against productivity.
When feedback is available quickly, you can move away from:
**Analyze → Analyze → Analyze → Decide**
and replace it with:
**Decide → Test → Learn → Adjust**
For reversible decisions, action isn't merely execution.
**Action generates information.**
### 4. Can the First Bet Be Smaller?
A decision doesn't have to be implemented everywhere at once.
Test the workflow with one team.
Launch first to a small group of customers.
Run 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 rises, shrink the bet before expanding the analysis.**
A smaller blast radius can transform a risky decision into a controlled experiment.
### 5. Who actually needs to make this decision?
This is the question 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?
Often, it doesn't.
Decision authority should move toward whoever has the best relevant information.
This changes the question leaders should ask from:
**"What should I choose?"**
toward:
**"Why does this decision require me?"**
That is ultimately a question of power.
## The Decision Architecture Matrix
Use reversibility and cost of error to determine the appropriate decision process.
| 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 | Slow down and increase scrutiny |
Organizations often apply **Critical Decision behavior** to decisions that don't deserve it.
Increasing analysis doesn't guarantee higher-quality decisions.
Sometimes the only result is a slower organization.
## When Should You Stop Analyzing and Decide?
Reversible, low-downside decisions generally don't require complete information.
A practical rule is to move once you have sufficient information to make an informed choice and enough protection to absorb a mistake.
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 more important principle is:
**You don't need certainty for a reversible decision. You need boundaries that make failure survivable.**
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.
## Use Guardrails Instead of More Approvals
The leadership implications become clear at this point.
Consider a team that repeatedly waits for approval before acting.
You might conclude:
**They need to make decisions faster.**
But their hesitation may 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.
Redesign the architecture.
Rather than approving decisions one by one, define clear decision rights:
"Customer issues below this financial threshold are yours to resolve."
"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.**
**Decision architecture governs how choices are made repeatedly.**
One creates dependency. The other creates scale.
## The Two-Minute Decision Test
Before your next significant decision, spend two minutes classifying it.
Start with five questions:
**1. Can it be reversed?**
Could we change direction without significant damage?
**2. What is the downside?**
Calculate what being wrong would actually cost.
**3. How quickly will reality tell us?**
Identify how quickly useful feedback will arrive.
**4. Can we shrink the bet?**
Find a way to test the decision with less exposure.
**5. Where should the authority sit?**
Put authority as close as practical to the best information.
Your answers should determine what happens next:
**Reversible + low downside → Decide.**
**Reversible + uncertainty → Experiment.**
**Reversible + better information elsewhere → Delegate.**
**Hard to reverse + high downside → Deliberate.**
Many difficult decisions become simpler once you classify them correctly.
## Better Decision Architecture Creates Speed
The goal isn't to make every decision quickly.
That would be reckless.
The goal is to match the amount of deliberation to the consequences of the decision.
Some decisions deserve research, dissent, scenario planning, and careful scrutiny.
Many others deserve a test.
There is, however, a larger implication for leadership.
If every meaningful decision eventually reaches your desk, you may feel powerful because everything requires your approval.
Structurally, however, the opposite may be happening.
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.**
This is what makes decision reversibility an organizational issue rather than merely a personal productivity technique.
It shapes where decision-making authority should be located.
It shapes the speed at which information is converted into decisions.
It influences whether an organization is built around distributed judgment or centralized permission.
The next time you're facing more info a decision, don't begin with:
**"What's the correct decision?"**
begin with a better question:
**"How difficult would this be to reverse—and where should the decision authority sit?"**
Most decisions don't deserve more stress.
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.**