Every decision embeds an assumption. The pricing model assumed a certain cost structure. The team split assumed a certain product scope. The market-entry sequence assumed a competitive landscape that has since shifted.
At the time, these were reasonable calls. The problem is that decisions persist long after the context that produced them has changed. The pricing model stays. The team split stays. The market-entry sequence stays. Nobody revisits them, because they no longer feel like decisions. They feel like facts.
This is decision debt: the accumulated weight of assumptions embedded in past decisions that continue to shape execution, often without anyone realizing a choice was ever made.
How decision debt accumulates
It starts innocuously. A founder chooses to build for SMB first because that was the fastest path to revenue in 2021. By 2024, the product has grown into mid-market, but the infrastructure, the sales motion, the support model, and the pricing tiers still assume an SMB buyer. Nobody made a decision to stay SMB-focused. The original decision just never got un-made.
Or a leadership team sets quarterly OKRs around a three-product portfolio. A year later the third product is mothballed, but the goal structure still allocates a third of the KPI targets to it. The quarterly planning deck carries the ghost of a product that no longer ships.
Decision debt compounds in exactly the same way strategy debt does, but it operates one layer deeper. Strategy debt is visible in the gap between the stated plan and the work underway. Decision debt is invisible, because the decisions it carries no longer look like decisions at all.
Why it resists detection
Three reasons make decision debt hard to spot:
The decision predates the team. Nobody in the room was there when the call was made. The constraint feels structural, like a property of the business rather than a choice someone made three years ago.
The constraint is load-bearing. Other decisions have been built on top of it. Revisiting it feels like pulling a thread that could unravel a quarter's worth of planning. So people work around it rather than through it.
It masquerades as alignment. A team that executes against inherited constraints looks aligned. The goals are met, the KPIs are tracked, the reviews go well. The problem is that the goals themselves were set against assumptions nobody has tested. The green dashboard hides the fact that the entire plan rests on a foundation that may no longer hold.
What to do about it
The first step is to separate constraints from assumptions. In any planning cycle, list the things the team is treating as fixed: the budget, the headcount, the target segment, the timeline, the tech stack, the partnership terms. Then ask: which of these are genuinely fixed, and which are decisions from a previous cycle that nobody has revisited?
The answer is usually surprising. Half the constraints are real. The other half are assumed, and several of them would be changed immediately if someone put them on the table.
The second step is to make the assumptions under each goal explicit. What has to be true for this KPI target to make sense? What market condition, cost structure, or competitive position does it assume? When those assumptions are written down, they become testable. When they stay implicit, they become debt.
The Vindaris view
The Work Graph traces every goal and KPI back to the projects, tasks, and people supporting it. When a constraint changes - a headcount shift, a product sunset, a market exit - the graph exposes which goals were built on that assumption and which initiatives are still executing against it. Execution risk isn't just misaligned effort. Sometimes it's perfectly aligned effort pointed at a target that no longer makes sense.