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

What it is not

Related terms

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.