Technical Debt
The accumulated cost of shortcuts, deferred improvements, and suboptimal decisions made during development — paid back through slower delivery and higher bug rates.
What is Technical Debt?
Technical debt is a metaphor coined by Ward Cunningham. Like financial debt, technical shortcuts taken today create interest payments tomorrow — in the form of slower development, more bugs, and harder onboarding for new engineers.
Types of technical debt
| Type | Description | Example |
|---|---|---|
| Intentional | Conscious shortcut with a plan to fix later | Hardcoded config to meet launch deadline |
| Unintentional | Mistakes or lack of knowledge | Poor abstraction that made sense at the time |
| Architectural | Foundational design choices that limit scale | Monolith that should have been modular |
| Dependency | Outdated libraries and frameworks | Running Node 12 when Node 22 is current |
How debt affects product teams
- Feature estimates increase 20–50% on heavily indebted codebases
- Onboarding new engineers takes longer
- Bug rates increase in areas with accumulated debt
- Engineers lose motivation working in poor code
PM's role in managing debt
- Maintain a visible debt inventory with engineering
- Allocate 15–20% of sprint capacity to debt reduction
- Frame debt in business terms: "This delays every feature in checkout by 1 week"
- Prioritise debt that sits in the critical path of upcoming features
Free templates for Technical
Frequently asked questions
How do you convince leadership to prioritise tech debt?
Frame it as risk and delivery speed. 'Our checkout module has high debt — every new feature there takes 3x longer than equivalent features elsewhere. Paying it down is a multiplier on Q3 roadmap velocity.' Avoid technical jargon.
Is all technical debt bad?
No. Intentional, documented debt taken to hit a deadline is a rational business decision. Undocumented, accumulating debt with no plan to repay it is the problem. The analogy holds: a mortgage is fine; maxed credit cards with no payment plan are not.
Apply Technical Debt to your real product data
PMRead ingests customer feedback, interviews, and Slack threads — and generates PRDs grounded in real evidence.
Related terms
Agile
An iterative approach to software development that delivers working software in short cycles, embraces changing requirements, and prioritises collaboration over documentation.
Scrum
An Agile framework that organises work into fixed-length sprints (1–4 weeks) with defined roles, ceremonies, and artifacts to deliver working software iteratively.