Decision Debt™
Decision Debt is the accumulated cost of delayed, deferred, or overly concentrated decisions — the operational drag that builds when choices sit with one person or never get made.
Teams can look busy while progress stalls. Work waits on approvals, priorities stay fuzzy, and people invent workarounds. Like technical debt, decision debt compounds: every postponed choice makes the next one harder.
Authored by David Runnels, Stories & Systems. Published October 3, 2026.
When this framework earns its keep.
Owners and leadership teams who feel constant urgency but still cannot get clear throughput — especially where everything routes through the founder.
Use it when
- Projects stall waiting on the same approver
- Priorities change weekly because tradeoffs were never recorded
- Staff escalate routine choices that should be rule-based
- You feel busy but strategic work never ships
Skip it when
- The bottleneck is pure capacity (not enough people) with clear decisions already in place
- You need clinical or regulated decision frameworks outside business operations
- The problem is solely tool failure with no decision ownership ambiguity
How to run it.
- 01
Inventory waiting decisions
List decisions stuck for more than a few days: hires, pricing exceptions, vendor choices, process changes, and scope calls. Note who is waiting and what is blocked.
- 02
Separate types of debt
Tag each item as delayed (known but postponed), deferred (avoided), or concentrated (only one person may decide). Different tags need different fixes.
- 03
Price the drag
Estimate cost in wait time, rework, missed revenue, or morale — even roughly. Decision debt becomes manageable when the cost is visible.
- 04
Write decision rights
For recurring decisions, define who decides, with what inputs, by when, and what gets escalated. Push routine choices out of the owner's head and into a rule.
- 05
Clear the backlog in slices
Burn down the highest-cost items first. Then install a lightweight cadence so new debt does not silently rebuild.
Illustrative example: the pricing exception pile
Imagine a growing firm with fourteen pricing exceptions sitting with the owner. Sales waits, delivery dates slip, and the team stops proposing creative packages. Treating the queue as Decision Debt — not automatically as a CRM problem — could lead to a focused decision clinic, a published exception matrix, and a weekly clear-the-queue ritual.
Want help applying this inside your operation?
Start with the five-minute Friction Assessment, or talk through where the framework fits.
Start the Assessment