Technical Debt

Technical explanation

Debt can arise in code, architecture, data, tests, infrastructure, security, documentation, or operations. Like financial debt, it can be a deliberate trade-off, but it accumulates interest through slower change, defects, workarounds, and rising cognitive load.

Business relevance

Visible technical debt helps leadership balance delivery speed with reliability and adaptability. Unmanaged debt reduces development capacity, increases incident risk, and delays strategic change.

Implementation example

A team launches with a temporary point-to-point integration, records its limitations and retirement trigger, and budgets replacement before transaction volume makes migration expensive.

Limitations and common misconceptions

Technical debt is a metaphor, not a precise accounting measure. Not every old system or imperfection is debt, and rewriting systems can create more risk than maintaining them.

Topics

Sources