The decisions your company is not making are the expensive ones

By Meet Patel · 2026-09-06 · updated 2026-09-11

Summary

Decision debt is the accumulated cost of decisions a company deferred because the information required to make them was expensive to assemble. It comes in three forms: deferred decisions waiting on information, defaulted decisions made by the calendar, and orphaned decisions with no owner. It is invisible in reporting and is typically repaid all at once during a crisis. It can be audited by listing every decision explicitly postponed in ninety days and grouping the stated reasons.

Key Metrics & Takeaways

3 forms
deferred, defaulted, orphaned
90 days
the audit window
6 months
one segment question I deferred, while it was unprofitable throughout

Technical debt got a name and, once it had one, it became something a company could discuss without anyone being accused of anything. That naming did more work than any tool.

There is an equivalent on the management side and it does not have a name in common use, so nobody discusses it. I call it decision debt: the accumulated cost of decisions a company deferred because the information required to make them was expensive to assemble.

It behaves like technical debt in the ways that matter. It is invisible on every report. It compounds. And it is repaid in a lump, at the worst possible moment, rather than in instalments.

Three kinds, and they need different fixes

Deferred debt is an information cost problem. Defaulted debt is a calendar and ownership problem. Orphaned debt is purely an ownership problem. Treating all three as a prioritisation failure — which is the usual instinct — fixes none of them.

Why every individual deferral is correct

This is the part that makes it hard to see.

Nobody is being lazy. On any given Tuesday, with three days of work required to assemble the picture and a launch on Friday, deferring is the right call. It is right again the following week. It is right eleven weeks in a row.

I spent six months not answering one question about a mid-market segment, and every single time I deferred it, it was the correct local decision. The segment had been unprofitable since roughly the second month. Six months of correct weekly decisions produced one badly wrong six-month outcome, which is not a paradox — it is just what happens when the cost of finding out is paid per attempt and the cost of not knowing is paid once, later, in full.

That is the whole mechanism. Nothing about it requires anyone to behave badly.

The audit

This is worth doing once, and it is unglamorous.

Go back ninety days through leadership meeting notes, message threads and your own calendar. Write down every decision that was explicitly postponed. For each one, record the date it was first raised and the stated reason for postponing it.

Then group the reasons. In every version of this I have run, they collapse into three or four clusters, and the shape of the clusters is the diagnosis.

If most of them say some version of we need to look at the numbers first, your decision debt is being generated by the cost of assembling information. That is fixable, and it is the one people assume is unfixable.

If most say we should discuss this with the team, it is a cadence problem — the decision is waiting for a forum, and the forum is the constraint.

If most say nothing coherent at all, you are looking at orphaned debt, and no system will help until a person is named.

The number that stops the room is not the count. It is the oldest item, and the fact that somebody can usually still remember when it was first raised.

What I got wrong about it

I assumed decision debt was a discipline problem — that better-run companies had less of it because they were more decisive.

The better-run companies I have seen do not defer fewer decisions. They defer roughly as many. What they do differently is keep the list visible, so a deferral is a recorded state rather than a disappearance. The decision still is not made, but everyone can see it is not made, and it has a date on it.

That is a much smaller intervention than being more decisive, and it is the only one I have seen actually hold.

The reason it stays invisible

Every reporting system in a company measures things that happened. Revenue that came in, tickets that closed, features that shipped.

Decision debt is a stock of things that did not happen, and no instrument in the building points at absence. You cannot dashboard a decision nobody made, which is why the first time most companies see the whole of it is during a crisis, when someone finally assembles the picture in an afternoon under pressure and discovers it could have been assembled at any point in the previous eight months.

That afternoon is not the failure. The eight months are.

Frequently asked questions

What is decision debt?

Decision debt is the accumulated cost of decisions a company deferred because the information required to make them was expensive to assemble. Like technical debt it is invisible on any report, it compounds quietly, and it is repaid in a lump during a crisis rather than in instalments.

How do you measure decision debt?

List every decision explicitly postponed in the last ninety days, with the stated reason for postponing it and the date it was first raised. Then group the reasons. If most say some version of we need to look into the numbers first, the debt is being caused by the cost of assembling information rather than by a lack of will.

What is the difference between decision debt and decision latency?

Decision latency measures how long a single decision takes from a change occurring to a response shipping. Decision debt measures the stock of decisions that were never made at all. Latency is a speed problem and debt is an accumulation problem, and a company can have low latency on the decisions it makes while carrying heavy debt on the ones it keeps avoiding.

Written by Meet Patel — founder of Company 8, building Dan (usedan.com). Dubai, UAE.

Read on themeetpatel.com