Decision debt
The accumulated cost of decisions a company deferred because the information required to make them was expensive to assemble. It compounds quietly, and is usually repaid during a crisis.
The part that costs money
Technical debt is code you chose to write badly because shipping mattered more that week. Decision debt is a decision you chose not to make at all, because assembling the evidence cost more than the decision felt worth that week. The two behave the same way: cheap to take on, invisible on any statement, and repaid at the worst possible moment with interest.
The mechanism is specific and worth naming, because it is not indecisiveness. A question comes up — is this segment actually profitable, is this channel still working, should this contract be renewed. Answering it properly means someone pulls three systems together for a day and a half. The question is not urgent this week. It is deferred, honestly and reasonably. Then it is deferred again.
What makes it compound is that the deferral is never recorded as a cost. The day and a half saved is real and visible. The decision not made is neither. So the ledger only ever shows one side, and the company keeps making the same locally rational trade until a crisis forces every deferred question to be answered at once, badly, under time pressure.
What it looks like
Six months of leadership notes carry the same line: "need to pull the numbers on the mid-market segment". It was correct to defer every single time — the day and a half was always needed elsewhere. The segment turns out to have been unprofitable since the second month.
How you would actually measure this
- Items in leadership notes carried across more than two cycles with an evidence-gathering blocker attached.
- Median age of open "we should look into" items, measured in cycles rather than days.
- Hours to assemble the evidence for a decision the company makes repeatedly — the assembly cost is the interest rate.
- After any expensive surprise: how long the signal was available in a system before anyone acted on it.
What it is not
- It is indecisiveness. — Indecisiveness is a person seeing the evidence and not choosing. Decision debt is the evidence never being assembled, so there is nothing to be decisive about. Replacing the leader does not clear it.
- It is analysis paralysis. — Analysis paralysis is too much deliberation. Decision debt is the absence of deliberation, caused by the input cost. They look similar from outside and have opposite fixes.
- It shows up in the numbers. — It shows up in their absence. The saving is visible and the foregone decision is not, which is precisely why the balance grows.
Related terms
- Organizational attention (https://www.themeetpatel.com/glossary/organizational-attention) — The finite capacity of a company to notice, prioritise and act on what is actually happening inside it. Storage buys none of it, and most tools spend it.
- Management latency (https://www.themeetpatel.com/glossary/management-latency) — The elapsed time between something changing in a business and the person able to act on it knowing about it. Most companies measure system uptime to the second and leave management latency unmeasured.
- Autonomous decision intelligence (https://www.themeetpatel.com/glossary/autonomous-decision-intelligence) — Autonomous decision intelligence is a system that connects a company’s systems, reconciles where they disagree, monitors what matters, investigates what changed, and puts an evidence-backed decision in front of a human — then keeps watching whether the call worked.
Frequently asked questions
What is decision debt?
The accumulated cost of decisions a company deferred because the information required to make them was expensive to assemble. It compounds quietly, and is usually repaid during a crisis.
How is decision debt different from technical debt?
Technical debt is work done badly on purpose; the artefact exists and can be inspected. Decision debt is work not done at all, because the evidence was expensive to assemble, so there is no artefact and nothing to inspect. Technical debt slows the next build. Decision debt shows up as a surprise.
How do you pay down decision debt?
By attacking the assembly cost rather than the decision. The deferral is rational as long as answering the question takes a day and a half; it stops being rational when the evidence arrives without anyone assembling it. That is the argument for decision infrastructure over another dashboard.