# Technical Debt

A way to describe design or implementation choices that provide near-term benefit while increasing the cost or risk of future software change.

- Type: practice
- Domain: Engineering & architecture
- Level: Intermediate
- Last reviewed: 2026-09-22
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/technical-debt/>)

## What it means

Technical debt is a metaphor for the future consequences of expedient or suboptimal technical choices. Like financial debt, a shortcut may be deliberate and useful when its immediate benefit exceeds its later cost; the continuing friction is the interest. Debt can also arise unintentionally through learning, changing requirements, aging dependencies, weak boundaries, or neglected maintenance. Not every imperfection is debt: the term is most useful when tied to a concrete impact on future work.

## Why it matters

Unmanaged debt can slow delivery, increase defects, constrain product options, and make routine changes hazardous. Naming it helps teams discuss trade-offs between current value and future adaptability. A visible, evidence-based approach also prevents maintenance work from becoming an abstract request to make the code cleaner.

## When to use it

Use the concept when a technical condition imposes a recurring cost, blocks an important objective, or creates material operational risk. Record enough context to explain the affected capability, likely consequences, and repayment options. Address debt according to impact and timing rather than placing every concern in an undifferentiated backlog.

## How it works

1. Describe the specific condition, why it exists, and the decisions or system boundaries involved.
2. Connect it to observable effects such as delays, incidents, support burden, security exposure, or limited options.
3. Estimate urgency, uncertainty, likely interest, and the cost of reducing or containing it.
4. Choose deliberately among repayment, incremental refactoring, isolation, monitoring, acceptance, or retirement.
5. Include reduction work in relevant feature or reliability plans instead of relying only on separate cleanup projects.
6. Review the item as architecture, evidence, and business priorities change.

## A practical example

A retailer copied tax logic into six services to meet a deadline. Every regulatory change now requires coordinated edits and produces inconsistent rounding defects. The team measures incident and change effort, introduces one versioned calculation service, migrates consumers incrementally, and retires each duplicate rather than attempting a risky all-at-once rewrite.

## Where it breaks

The debt metaphor can oversimplify architecture and imply that every compromise must be repaid. Estimates of principal and interest are uncertain, and teams may label disliked code as debt without evidence. The term can also conceal chronic underinvestment or reckless decisions behind neutral language. Some systems will be retired before repayment becomes worthwhile.

## Common mistakes

- Calling every defect, missing feature, or untidy file technical debt.
- Maintaining a large debt register without linking items to outcomes or decisions.
- Demanding complete repayment instead of reducing the highest-cost constraint incrementally.
- Using delivery pressure to justify shortcuts without recording ownership or review conditions.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/technical-debt/#visualization-technical-debt>)

## Sources

1. [A Field Study of Technical Debt](<https://www.sei.cmu.edu/blog/a-field-study-of-technical-debt/>) — Carnegie Mellon University Software Engineering Institute · Institutional research summary
2. [Technical Debt Quadrant](<https://martinfowler.com/bliki/TechnicalDebtQuadrant.html>) — Martin Fowler · Professional technical article

## Related topics

- [Refactoring](<https://wiki.soroush.uk/topic/refactoring/>)
- [Code Review](<https://wiki.soroush.uk/topic/code-review/>)
- [Trunk-Based Development](<https://wiki.soroush.uk/topic/trunk-based-development/>)
