Technical debt
In short: What is Technical debt?
Technical debt is the accumulating cost of quick but non-durable solutions: the extra work that has to be paid back in later development.
Explanation
The metaphor comes from financial debt: a shortcut saves time today but accrues “interest” because every future change becomes slower and riskier. Debt also builds up from outdated dependencies, missing tests and undocumented code.
Not all technical debt is bad, as a tight deadline or a market experiment can justify taking it on. Trouble starts when nobody tracks or repays it, until the system eventually becomes almost impossible to modify safely.
Example: if a feature ships without automated tests to meet a deadline, the team logs the debt and adds the tests in the next sprint before building new functionality on top of it.