top of page

The Diagnosis Debt: Naming the Pattern That Keeps Costing the Enterprise Twice

Updated: Apr 24

Yellow background with bold black and pink text: "A NEW TERM The Diagnosis Debt." Describes untested strategic decisions' costs.


Every category eventually gets the vocabulary it needs. Software engineering got technical debt in the 1990s and the conversation about how teams build, ship and maintain code has never been the same. The term didn't introduce a new problem. It named one that engineers had been living with for decades, and naming it changed how the work got commissioned, scoped and resourced.


Enterprise commercial strategy is overdue for the same move.


There is a pattern that every senior leader in the space recognises but the category has no language for.


It deserves one.


I'm going to call it The Diagnosis Debt, and I want to be precise about what it is, how it accrues, and what it costs because once a pattern is named, the conversation about how to address it can finally begin.



What the Diagnosis Debt is

The Diagnosis Debt is the accumulated cost of every strategic decision an enterprise has made on inputs it never properly tested.


It is what builds up when a reset is commissioned under time pressure and the scope is set before the problem has been honestly diagnosed. It is what builds up when a kick-off workshop accepts the leadership team's view of the issue as the issue, rather than as one hypothesis among several. It is what builds up when a strategy is signed off based on consensus in the room rather than evidence from the market.


It is what builds up every time the answer to "how do we know this is true?" is "we've talked to enough people."


None of these moments feel expensive at the time. That is the nature of debt. The cost is deferred, not avoided.


Text on a light background reads: The strategy gets reset. The same problems keep returning. Every engagement is to fix the last one's issues.

How the debt compounds

The Diagnosis Debt has the same compounding property as technical debt. Each unaddressed assumption makes the next decision harder, because the next decision is built on top of it.


A segmentation that was never validated becomes the basis for a campaign plan, which becomes the basis for a content investment, which becomes the basis for a sales enablement track, which becomes the basis for a regional rollout. By the time the regional team flags that the original segmentation never matched their market, the cost of unwinding is no longer the cost of redoing the segmentation. It is the cost of rebuilding everything that was stacked on top of it.


This is why enterprises so often experience strategic work as fragile. It isn't fragile because the work was bad. It is fragile because too much of it is sitting on undiagnosed foundations.


Text on pink background: “Campaigns miss. Creative gets the blame. Diagnosis never does. The organisation learns to repair the symptom and protect the assumption underneath.”

How the debt becomes visible

The Diagnosis Debt is rarely visible in the form of a single failed initiative. It is visible in the patterns that surround the work.


Campaigns miss the buying group, and the response is to commission better creative rather than to ask whether the buying group was ever properly mapped. Regions quietly stop using the global framework, and the response is to commission another enablement programme rather than to ask whether the framework was ever designed for the operator who has to use it. Content is rewritten by every team that touches it, and the response is to commission stricter brand guidelines rather than to ask whether the original positioning ever earned the regional team's trust.


Each of these moments is the debt presenting an interest payment. The organisation pays it, usually without recognising it as a payment, and moves on. The principal remains untouched.


Text on blue background reads: "The framework rolls out. Regions quietly opt out. Nobody calls it failure." Emphasizes unread signals by leaders.

How the debt gets paid down and why the industry resists doing so

Paying down diagnosis debt is conceptually simple and operationally uncomfortable. It means stopping, before the next big strategic move, and asking the four questions the kick-off deck is designed to skip.


  1. What is actually broken, as opposed to what is uncomfortable.

  2. Where are we operating on belief rather than evidence.

  3. Who owns the decisions that keep getting re-opened.

  4. What would have to be true for the next phase of work to hold.


These are not difficult questions in principle. They are difficult questions because the answers often reveal that the problem leadership wants to solve is not the problem the organisation has. That recognition is expensive in the short term, it slows the project down, it changes the scope, it sometimes implicates decisions that were made by the people commissioning the work and cheap in the long term, because it prevents the next round of debt from being taken on.


The reason the industry resists this move is structural. Strategy partners are commissioned to produce decisiveness in the first four weeks. Enterprise leadership is rewarded for visible motion. Both sides collude, quietly, in skipping the step that would have made the work durable. The Diagnosis Debt is the predictable consequence.


Text on a purple background reads, "The deck gets approved. The real decisions happen in the corridor." It suggests decisions happen informally.

Why naming it matters

A pattern without a name is hard to argue against. It is also hard to argue for addressing. When the only available framing is "we should probably do more discovery this time," the conversation routes around it. When the available framing is "we are about to take on more diagnosis debt than we can carry," the conversation has somewhere harder, and more useful, to go.


That is what naming the debt does. It gives the senior commercial leader a vocabulary for an instinct they have had for years but couldn't articulate to a board, an executive team, or a strategy partner. It gives the procurement function a basis for asking different questions before signing the next statement of work. It gives the operator inside the organisation a way to flag the cost they are absorbing every time another initiative arrives without the foundations being checked.


It also, eventually, changes how the category builds. When technical debt was named, the engineering function reorganised around the assumption that maintenance, refactoring and architectural integrity were first-class work, not a tax on real work. The category built tools, methods and roles to address it. The same shift is overdue in enterprise commercial strategy.



The question worth carrying into the next reset

If the organisation is about to commission another strategic reset, there is one question worth asking before the kick-off deck lands.


How much diagnosis debt are we carrying into this decision, and what is our plan to pay it down before we add to it?


The honest answer is usually the most expensive conversation of the year. It is also, without exception, the cheapest decision made in it.


Text on pink background: "How much of it are you carrying into your next decision?" The mood is reflective and thought-provoking.

 
 
bottom of page