Quantifying technical debt so an executive committee listens

Technical teams ask for time to repay debt. Executive committees do not fund a concept they can neither measure nor tie to an outcome. Both are right, and the deadlock is one of vocabulary.

Why technical arguments fail

"The code is badly structured", "test coverage is insufficient", "this library is unmaintained" are accurate observations. None is a budget argument, because none states the cost of doing nothing.

An executive committee arbitrates between competing requests. The one that states its cost of inaction wins.

The conversion into three indicators

Extra cost per delivery. Measure the real time spent on three recent changes of comparable size, one in an indebted area and one in a healthy area. The gap, multiplied by the number of annual changes in that area, gives days per year. It is a debatable number and it is a number.

Post-release defect rate. Count incidents occurring within thirty days of a release, by code area. An area that systematically produces regressions costs operations time, fix time and user trust.

Onboarding time for a new joiner. How long before a newly hired developer is autonomous in that area? That delay is directly proportional to the code's illegibility, and it converts immediately into salary cost.

The phrasing that gets a decision

Not: "we need to refactor the billing module".

But: "the billing module consumes 40 extra development days per year compared with a healthy codebase, and generates 60% of our production incidents. Thirty days of structural work would bring that extra cost below 10 days a year. Payback is nine months."

The second statement is an investment case. The first is an engineer's preference.

The debt report in a maintenance contract

If you outsource maintenance, debt has an unpleasant property: a provider paid per fix has no interest in reducing it. They have an interest in fixing quickly and moving to the next ticket.

Write into the contract a monthly debt report stating, on one page: debt deliberately taken on during the month with its justification, debt repaid, and the three most expensive areas with their estimated extra cost.

That document makes the subject visible without an extra meeting, and it protects you from the silent drift that makes an application unmaintainable within three years.

Deliberate debt is not a defect

Consciously taking a shortcut to meet a commercial deadline is a legitimate decision. What causes problems is taking it on without recording it.

The rule that works: every deliberate debt is documented at the moment it is incurred, with the reason, the estimated repayment cost and a review date. It takes five minutes and it completely changes the conversation three years later.