Ward Cunningham's original 1992 debt metaphor wasn't a warning that code could be flawed — every codebase is. It was the observation that imperfect code charges interest: the longer you carry it, the more it costs to pay off. This visualizer shows what that interest actually looks like over five years, under five different response strategies.
Enter your current annual cost of technical debt below (use the Cost Calculator if you don't have this number yet), and see how it compounds over 5 years under each strategy.
| Scenario | Annual growth | 5-year total cost | Savings vs. Do Nothing |
|---|
Debt doesn't sit still — it accelerates through five reinforcing mechanisms. Each adds its own annual growth pressure on top of the base cost.
Every function or service that stays un-refactored tends to pick up more callers over time. What was once an isolated shortcut becomes a load-bearing wall — and touching it now means touching everything downstream of it.
New engineers take longer to onboard into a debt-heavy system, and without tribal knowledge to fall back on, they're more likely to unknowingly add to the very debt they're still learning to navigate.
Deferred library and framework upgrades don't stay the same size — they compound. Jumping four major versions at once is exponentially harder than four incremental upgrades, and the security exposure grows the whole time you wait.
Code written without tests tends to get extended without tests too. Coverage doesn't erode linearly — it collapses in the areas people are most afraid to touch, which are usually the areas that need the most work.
Every patch-on-a-patch adds a layer of indirection. Eventually engineers spend more time reconstructing why a workaround exists than they spend on the business logic it was built around.
Compounding is gradual for years — until the annual cost crosses a threshold your team can no longer absorb inside its existing headcount. That inflection point is the "debt cliff." Here's a worked example for a 25-person engineering org carrying $350,000/year in debt cost at an 18% annual growth rate, measured against the cost of two dedicated senior engineers ($250,000 fully-loaded each, $500,000 combined) as the affordability ceiling.
| Year | Annual debt cost | FTE-equivalents consumed | Status |
|---|---|---|---|
| Year 1 | $350,000 | 2.3 | Manageable drag |
| Year 2 | $413,000 | 2.8 | Velocity decline becomes visible |
| Year 3 | $487,340 | 3.2 | Sprint commitments start slipping |
| Year 4 | $575,061 | 3.8 | Debt cliff — exceeds 2 senior hires |
| Year 5 | $678,572 | 4.5 | Rewrite conversation begins |
By Year 4, the annual cost of doing nothing ($575K) exceeds what it would cost to simply hire two more senior engineers outright — except this spend buys no new capacity, just standing still.
The 20% Rule — a standing allocation of sprint capacity to debt paydown — is sufficient. No special initiative required.
Time to dedicate a focused initiative — a quarterly debt sprint or a named owner — rather than relying on ad hoc attention.
Urgent. You're approaching or past the cliff — a major refactor or phased rewrite needs to be on the roadmap now, not next planning cycle.
Measure first. Use the Assessment Scorecard and the Metrics Guide to get an honest baseline before choosing a strategy.
This visualizer shows the cost of waiting. Here's how to turn it into a plan.