Decision debt: definition
Decision debt is the accumulated cost of decisions made without a usable trace: no written context, no reasoning, no link to the evidence that motivated them. Like technical debt, it is not paid at the moment it is incurred but later, in recurring interest: debates that reopen, alternatives that get re-proposed, mistakes that get repeated. The metaphor is deliberate: deciding fast without documenting is sometimes the right call, but the debt compounds silently if it is never repaid.
Why the concept matters
An early-stage team decides constantly, and every untraced decision adds to the debt. The mechanism is described in Why startups forget their decisions: decisions live in conversations, the "why" never gets written, and memory rests on people. The interest payments take concrete forms:
- The re-debate: a settled question comes back, with the same arguments, because nobody remembers the conclusion or its reasons.
- The re-test: a channel or approach already tried and abandoned returns as a "new idea," and the experiment gets run again at full price.
- The orphaned conclusion: the rule survives ("we never discount"), but its reasoning is gone, which makes it impossible to re-evaluate honestly.
- People dependency: every departure takes a slice of the decision history with it.
What decision debt is not
It differs from neighboring notions:
- It is not technical debt, even though the metaphor comes from it: technical debt lives in the code, decision debt lives in the lost knowledge around choices.
- It is not indecisiveness. A team can decide fast and well while still piling up debt: the problem is not the quality of the decision, it is the absence of a trace.
- It is not merely under-documentation. A team can document heavily and stay in debt if the documents never resurface at the useful moment.
How to pay down decision debt
You do not repay this debt by reconstructing the entire past: the effort would be disproportionate. The realistic approach:
- Stop incurring it: record new structural decisions as they are made, with a decision record capturing the conclusion, the reasoning, the alternatives and the evidence.
- Repay opportunistically: when an old topic resurfaces, reconstruct its original decision once and for all, and add it to the log.
- Learn from failures: a post-mortem after every significant episode turns a loss into a reusable lesson.
- Tool the retrieval side: the debt re-forms if traces never resurface at the right moment. That is the role of a living organizational memory, the approach Verbasil takes, where past decisions come back on their own when the topic reappears.
FAQ
How do I know if my team is accumulating decision debt?
Three reliable symptoms: debates restarting on topics already settled, "new" ideas that were actually tried before, and rules everyone follows without anyone being able to justify them. If any of the three happens regularly, the debt is already there.
Should we document every decision to avoid decision debt?
No. Documenting everything creates a different debt: a volume nobody consults. The target is the structural decision, the one that commits the team beyond a few weeks or is likely to be re-debated. For everything else, staying lightweight remains the right strategy.