Skip to content
Subscribe
Technical Debt Is Not a Metaphor: It Is a Financial Instrument
Product & Strategy

Technical Debt Is Not a Metaphor: It Is a Financial Instrument

FN
1 min read

The Problem with the Metaphor

Ward Cunningham coined "technical debt" to explain to business stakeholders why shipping fast now creates costs later. The metaphor worked too well — everyone understood it, and then immediately ignored it, the same way most people ignore their credit card statements.

The solution is to stop treating technical debt as a metaphor and start treating it as what it actually is: a financial instrument with measurable costs.

Quantifying the Interest Rate

Every piece of technical debt has an "interest payment" — the recurring cost of working around it:

  • Developer time: How many extra hours per sprint does this debt cost?
  • Incident frequency: How many outages does this area cause per quarter?
  • Onboarding cost: How much longer does it take new engineers to understand this code?
  • Opportunity cost: What features cannot be built because this area is too fragile to touch?

A Concrete Example

Your payment processing module was written hastily during the launch. Every sprint, engineers spend 3 hours working around its limitations. That is 3 hours × 26 sprints × $100/hour = $7,800/year in interest.

If rewriting the module takes 40 hours ($4,000), the payback period is 6 months. After that, it is pure savings. This is a decision any CFO can understand.

The Debt Register

Maintain a living document that tracks every known piece of technical debt with:

  1. Description of the debt
  2. Estimated interest payment (hours/sprint)
  3. Estimated payoff cost (hours to fix)
  4. Payback period (payoff ÷ interest)
  5. Risk assessment (what happens if we never fix it)

Sort by payback period. Fix the shortest payback items first. This is not engineering intuition — it is basic finance.

When Debt Is Good

Not all technical debt is bad. Deliberate, short-term debt with a clear repayment plan is a legitimate strategy. Ship the MVP with shortcuts, validate the market, then pay down the debt with revenue. The key word is "deliberate" — most technical debt is accidental, undocumented, and growing compound interest.

Tagged in: Product & Strategy

FN

Share your thoughts

Start the conversation. Your input matters.

Enjoy this article?

Subscribe