What is Technical Debt?
Technical debt is the accumulated cost of past shortcuts in how software was built — quick fixes, outdated dependencies, skipped refactoring — that makes future change slower and riskier. Like financial debt, it can be a sensible trade-off, but it accrues interest and has to be deliberately managed and repaid.
Reviewed by Gensudo Team · 23 July 2026
In more depth
The debt metaphor, coined by Ward Cunningham, is precise: borrowing (shipping a shortcut) can be rational when speed matters more than polish, but the interest is paid on every subsequent change that touches the compromised area — longer estimates, more regressions, more careful testing. Debt is taken on knowingly or accumulates silently as the codebase ages and the product outgrows early design decisions. The failure mode is not having debt; it is having invisible, unmanaged debt, where nobody can say where it is, what it costs, or which parts are worth repaying. Mature teams track significant debt items alongside features and pay them down where change is most frequent.
Why it matters
For product decisions, technical debt is a velocity tax that compounds: features that once took days start taking weeks, and estimates stop being believable. Left unmanaged, it eventually forces a brutal choice between a risky rewrite and a slow decline. Managed openly — named, sized and prioritised against feature work — it becomes a normal cost of doing business, and 'slow down to speed up' becomes a defensible line in a prioritisation discussion rather than special pleading.
A product example
A team notices that every change to their notification system takes three times its estimate, because a years-old shortcut hard-wired notifications into the ordering code. They log the debt explicitly, quantify the drag it adds to a roadmap full of notification-dependent features, and win a fortnight to separate the two systems — after which the next three planned features each ship in half the projected time.
Documents where this shows up
Product Requirements Document (PRD) for Product Managers · Prioritisation Framework for Heads of Product
Related terms
Product Backlog · Feature Creep · Minimum Viable Product (MVP)