Routine, reversible decision
What matters
Lightweight justification: a clear owner, brief rationale, agreed action, and a review trigger if needed.
What to avoid
Unnecessary analysis, lengthy documentation, and committee delays.
Most organizations can point to projects that have accumulated technical debt: shortcuts were taken to get something working, temporary fixes survived longer than intended, and each compromise made the next change just that little bit harder.
What isn’t as widely realized is that something very similar happens with decisions. A decision gets postponed because the meeting runs out of time. Another is made, but nobody records why. A temporary compromise is agreed with the intention of revisiting it in six months, then quietly just becomes the way things are done. Elsewhere, two teams make sensible decisions independently but only discover much later that they conflict.
None of these incidents looks particularly serious on its own; people work around them, another meeting gets scheduled, someone digs through old emails, and life moves on.
Over time, though, the organization starts paying for them. That accumulated burden is Decision Debt: the future cost created when decisions are repeatedly delayed, made without enough clarity, poorly documented, left without ownership, or allowed to survive after the assumptions behind them have changed.
The analogy with technical debt is useful because Decision Debt also compounds. A shortcut today may save an hour, but make something harder next month. The important question therefore isn’t whether every decision followed a perfect process, but whether the organization still knows what it decided, why it decided it, what had to be true for the decision to work, and when that decision should be reconsidered.
What Decision Debt actually looks like
Just like its better-known cousin, technical debt, Decision Debt rarely appears on a dashboard with a helpful label attached. It tends to surface indirectly, usually when somebody tries to move something forward.
The examples will sound familiar to anyone who’s ever worked in a company, big or small; a team wants approval for a new investment but discovers that nobody can explain why a related initiative was approved last year. A project can’t proceed until another department makes a decision that’s already been discussed in three meetings. A new leader challenges an existing policy, and the conversation is forced to start from scratch because the original reasoning disappeared with the people who made it.
Some common forms are easy to recognize once you know to look for them:
⏳ Unresolved decisions that block downstream work. People continue researching, discussing, or designing around an issue because nobody has actually made the call.
🔁 Decisions that are repeatedly reopened. The conclusion may have been perfectly reasonable, but the evidence and rationale were never preserved well enough to stop the same argument from returning.
📌 Temporary compromises that become permanent. An exception agreed for three months is still operating three years later because nobody created a trigger to revisit it.
🧩 Conflicting decisions across teams. Different departments optimize for their own objectives without seeing commitments already made elsewhere.
🔍 Assumptions with no owner. A forecast depends on customer adoption, hiring capacity, or supplier pricing, but nobody’s responsible for checking whether that assumption remains credible.
🗂️ Approvals that can’t be reconstructed. The organization knows something was approved, but struggles to establish who approved it, what evidence they saw, or what conditions were attached.
📅 Initiatives that continue without a review point. Circumstances change, yet the decision effectively renews itself through inertia.
The common thread isn’t poor documentation for its own sake; it’s lost decision context. Once that context disappears, future teams have to reconstruct it, challenge it again, or simply guess, and that’s when an apparently small shortcut begins charging you interest.
Decision Debt is created by delay as well as poor records
Some Decision Debt begins before a decision has even been made. In many organizations, keeping an issue open is treated as the cautious option. If more information might arrive next week, more stakeholders could be consulted, or another analysis might reduce uncertainty, postponing the decision can feel safer than committing.
And sometimes it is, as many decisions genuinely benefit from more evidence.
The trouble starts when delay just becomes the default response to uncertainty. Work continues around the unresolved question, people develop competing interpretations, assumptions harden unofficially, and downstream teams begin making their own provisional choices because they can’t wait forever.
Eventually, the organization hasn’t avoided making a decision at all; it’s made several fragmented decisions without acknowledging them.
Consider a company debating whether to replace an aging internal system. Leadership delays the investment decision while further options are examined. Meanwhile, to keep the lights on, one team is forced to renew a supplier contract that was coming to an end, another builds an integration around the existing platform, and a third recruits people with skills specific to it. Six months later, the original decision is harder because postponement has created new dependencies.
HOW A DELAYED DECISION CREATES NEW COMMITMENTS
Decision delayed
Further evidence requested
Leadership postpones the investment while seeking more evidence.
Teams work around it
Keep things moving
Contracts are renewed, integrations built, and people recruited.
Dependencies grow
Temporary becomes lasting
Workarounds become commitments that are harder to reverse.
Decision becomes harder
Options narrow
New costs and dependencies constrain the original choice.
The official decision may still be open, but the organization is already accumulating commitments around it.
The same thing happens on a smaller scale when meetings repeatedly end with the all-too-familiar “we need a bit more information” without specifying what information would actually change the decision.
Useful delay has a purpose: there’s a gap in the evidence that can realistically be closed, someone responsible for closing it, and some sense of when the decision will be made.
Without those things, waiting isn’t analysis; it is accumulating commitments while pretending the decision is still open.
More governance isn’t automatically the cure
There’s an obvious response to Decision Debt: document everything, create more approval stages, and make sure every decision passes through a formal governance process.
However, taken too far and too literally, that can create another form of the same problem.
If a £5,000 operational choice is forced to have the same process put around it as a £5 million investment, decisions slow down for reasons that have nothing to do with their risk or importance. People wait for committees, prepare documents nobody needs, and find informal workarounds because the official route takes too long.
The resulting backlog is still Decision Debt.
Good decision governance therefore needs some proportionality. A minor, reversible decision may need little more than a clear owner and a short record of what was agreed. A strategic investment with significant financial exposure likely deserves stronger evidence, explicit assumptions, alternatives, risk analysis, approval authority, and post-approval tracking.
MATCH GOVERNANCE TO THE DECISION
Strategic, high-impact investment
What matters
Deeper scrutiny: alternatives, supporting evidence, financial assumptions, risk analysis, and approval authority.
What to preserve
Expected outcomes, accountability, approval conditions, and review triggers.
Good governance preserves the context that matters without making every decision follow the same process.
Speed itself isn’t the enemy. In fact, a clear decision made quickly can prevent debt from forming. The distinction is between moving quickly and deferring clarity.
A team that says, “We have enough evidence, Person X owns the decision, we’re choosing option B, and we’ll review it if adoption falls below 60%” has moved quickly while preserving the information that matters.
A team that says, “Let’s go with B for now and see how it goes” may reach the same immediate outcome, but leaves several problems for somebody (or indeed, possibly nobody) else to solve later.
That difference can look trivial in the meeting, but months later, it may determine whether the organization can adapt intelligently or has to reopen the entire argument.
The cost compounds across the organization
The most visible cost of Decision Debt is usually wasted time. People repeat analysis, search for old presentations, reconstruct approval histories, and attend meetings that wouldn’t be necessary if the original decision had been clearly recorded.
The less visible effects can be more damaging. Poorly preserved decisions can lead to political disputes because people remember the past differently. One person may recall an initiative as a strategic commitment, while another may remember it as an experiment. Somebody may believe a benefit target was promised, while somebody else may think it was merely illustrative. With no reliable decision record, memory becomes evidence.
Decision Debt can also encourage sunk-cost behavior. Initiatives continue because stopping them would require consciously making a new decision (which again, can have a political dimension, if that’s viewed as rocking the boat), while just continuing down the same path requires no such moment of questioning. Unless someone defined what should trigger a review, yesterday’s decision quietly becomes today’s default.
At portfolio level, the problem grows again. Leaders may see a collection of projects and investments without being able to see the commitments linking them: which initiatives rely on the same assumptions, where different teams have approved overlapping work, which expected outcomes are already at risk, or where several apparently separate decisions compete for the same resources.
That’s when Decision Debt can start to resemble corporate amnesia. The organization continues making decisions, but loses enough of its memory that each new one is made with an incomplete view of what’s already been learned or promised.
Individual decisions may still look sensible, but collectively the organization becomes slower, less consistent, and surprisingly good at paying twice for the same thinking.
How to reduce Decision Debt without adding process for the sake of it
Managing Decision Debt doesn’t require recording every conversation or building bureaucracy around routine judgment. The aim is to preserve the parts of a decision that someone is likely to need later. For decisions with meaningful consequences, that usually means being able to answer a handful of practical questions:
🧭 What was actually decided? Avoid records that describe the discussion but never quite state the conclusion.
👤 Who owns it? Someone should be accountable for the decision or the commitment that follows from it.
🔍 What evidence and assumptions mattered? Capture the factors that could later change whether the decision still makes sense.
⚖️ What alternatives were considered? You rarely need the full history, but knowing why the chosen option beat credible alternatives prevents needless reopening.
✅ Who approved it, and under what conditions? This matters particularly where authority, spending, or risk is involved.
📊 What outcome was expected? Without an expected result, reviewing the decision later becomes little more than hindsight.
🔄 What should cause us to revisit it? A date can work, but a change in price, demand, regulation, adoption, or another key assumption is often more useful.
None of this needs to become a twenty-page business case; the amount of structure should reflect the importance, reversibility, and uncertainty of the decision.
The bigger opportunity comes when those records are connected rather than disappearing into individual documents and folders. Structured decision information can show leaders where approvals are waiting, which assumptions recur across several investments, where expected outcomes are slipping, and which decisions may now deserve another look.
This is one reason KangaROI treats the decision itself as the primary object. Evidence, assumptions, risks, financials, approvals, and subsequent tracking remain connected to the commitment they supported, while outputs such as business cases or approval packages can be produced when they are useful.
The objective isn’t perfect institutional memory; it’s enough memory to stop the organization paying repeatedly for forgetting.
Decisions are a portfolio of commitments
Most organizations already manage portfolios of projects, investments, products and risks. Their decisions deserve similar attention.
Every important decision creates some form of commitment. Money may be allocated, people reassigned, suppliers selected, systems built, targets accepted or opportunities deliberately declined. Those commitments have histories, assumptions, owners and consequences even when the original meeting has long since disappeared from everyone’s calendar.
Treating decisions as isolated moments makes those connections difficult to see. Treating them as a portfolio creates a different kind of organizational memory: leaders can understand what has been decided, what remains unresolved, what those choices depend on, and where changing circumstances may require another decision.
Decision Debt will never disappear completely, so attempting to remove every trace of it shouldn’t become another governance exercise. Sometimes the sensible choice really is to move quickly, accept an imperfect record, and get on with the work.
The danger is allowing temporary ambiguity to become permanent organizational memory. A decision that saves ten minutes today but costs three teams several meetings next year was never quite as cheap as it looked.
