Definition
Technical debt is the future cost created when a technical choice solves a current need while leaving known structural weakness behind.
What this term depends on
- Current shortcut
- A choice solves an immediate need while postponing structural work.
- Future cost
- Later change becomes slower, riskier, or more expensive because of the shortcut.
- Structural weakness
- The debt sits in architecture, code, data, tests, knowledge, or operating routines.
Why it matters
Technical debt matters when it changes the economics and risk of future modernization work.
Watch out for
- Calling every disliked system technical debt
- Fixing code while the operating or funding debt remains
- Debt registers with no decision about repayment or tolerance
Use technical debt when a technical compromise is actively increasing the cost of change.
The term is useful only when it leads to a decision: repay, tolerate, isolate, or redesign the conditions that keep creating it.