Engineering organisations have built an entire culture around tech debt. It's named, tracked, discussed in retros, occasionally allocated dedicated time to pay down. The vocabulary is mature enough that any engineer can articulate why some debt is healthy and some is dangerous, and any engineering leader can defend a quarter spent reducing it. Strategy organisations have no equivalent vocabulary, and yet the equivalent phenomenon is staring back at every executive team in the country. Every postponed strategic decision is a debt. It accrues interest. The interest is paid in capacity allocated against ambiguity, focus diluted across half-decisions that should have been one whole decision, and credibility eroded each time the leadership team has to hold the same conversation it held last quarter.
What strategy debt actually looks like
The catalogue is depressingly consistent across companies. Every executive team can identify their own version of it within five minutes if asked directly.
A market the company says it serves in its positioning materials, but has never actually decided whether to invest in. The marketing copy mentions it. The sales team gets asked about it. No headcount has been allocated to it. No product capability has been built for it. Whether the company is in this market is technically unresolved, and every quarter the question gets raised and deferred.
A product line that the executive team privately agrees should be sunset, but keeps quietly funding because nobody wants to be the person who proposes killing it. The engineering team servicing it is bored and underused. The revenue is flat and shrinking. The decision to sunset has been on the agenda for three quarterly reviews and has been deferred each time with some version of "let's look at it again next quarter."
A geographic expansion that gets discussed every quarter and never gets a yes or a no. The CRO keeps adding it to the planning conversation. The CFO keeps asking for more analysis. The CEO keeps saying it's "important but not now." Eighteen months go by. The opportunity, whatever it was, is now smaller, and the question is no closer to resolution.
A pricing model that everyone in the leadership room knows is wrong — too cheap for what it delivers, too complex to explain to customers, too punitive to expansion — but nobody owns the decision to change it because changing pricing is high-stakes and politically expensive.
Each of these costs nothing in isolation. Together they form the actual operating drag on the company.
Why strategy debt stays invisible
Because the cost never shows up on a strategy slide. It shows up everywhere else, attributed to other causes.
It shows up as the engineering roadmap looking incoherent, because the team is trying to serve three half-decisions instead of one whole one. The PM who built the roadmap gets blamed for poor prioritisation, when the real problem is that the strategy never resolved which of the three competing directions was the actual priority.
It shows up as marketing spend that can't be defended on its return, because the segment was never explicitly chosen, so the campaigns are spread thin across three plausible segments instead of concentrated on the one that was supposed to be the bet. The CMO gets pushed on inefficient spend. The real problem is that the choice was deferred upstream of marketing.
It shows up as a sales pipeline full of confused customers, because the positioning was never resolved, so the field is selling four different versions of the company depending on which rep is in the room. The CRO gets pressured on win rates. The real problem is that the company has not yet decided which company it is.
Each local cost is attributed locally. Nobody adds them up. The aggregate — the actual operating drag of unresolved strategic ambiguity — is the largest number in the company and the only one that never gets reported.
How to start paying it down
There's a small, uncomfortable, effective protocol for this, and it doesn't require a strategy consultant.
First, list the open strategic decisions. Every executive can name three to ten of them under mild pressure. Write them down on a shared page. The act of listing them is half the work, because the moment they're visible together it becomes impossible to pretend they aren't accumulating.
Second, assign each one a decision date. Not a discussion date. A decision date, by which the leadership team will say yes, say no, or say "explicitly defer for the following named reason." A decision date with a name on it is a commitment. A discussion date with a name on it is more debt.
Third, make non-decision a decision. "We are choosing not to enter market X this year, and we will revisit only if Y changes" is an answer. It frees the marketing team, the sales team, and the product team to operate against a clear constraint. "We'll revisit next quarter" is not an answer. It's debt with a calendar reminder attached.
Why this protocol is harder than it looks
Because every postponed decision is postponed for a reason — usually political, usually involving some executive whose perceived authority would be diminished by resolution one way or the other. The pricing decision is deferred because the CFO and the CRO disagree and neither wants to lose. The market entry is deferred because the founder is emotionally attached to the idea and the CEO doesn't want to override them. Paying down strategy debt requires the leadership team to absorb the political cost of resolution, which is uncomfortable, which is why it keeps not happening.
The Vindaris view
You cannot operate a company efficiently against unresolved strategic questions. The work fragments around the ambiguity. The substrate cannot connect goals to work, because the goals themselves are contingent on decisions that haven't been made. The teams sense the ambiguity and lose belief in the planning artefact, which compounds the problem at the cultural layer. Pay the debt. The list is shorter than you think, the decisions are less terrifying than the deferral, and the operating system gets dramatically simpler the moment the open questions get closed.