Technical debt is the extra work you will have to do later because of shortcuts or poor design chosen now. Like financial debt, borrowing can be a good decision (to hit a deadline), but you pay interest: every feature becomes slower to build, bugs increase and new developers struggle.
An analogy for non-technical people: a restaurant kitchen where staff skip cleaning during the busy season. At first they serve more orders, but soon things get slower, food safety becomes a risk and eventually the kitchen must close for a deep clean.
How to present it:
Use business impact, not code details: "Every change to checkout now takes three days instead of one, and it caused two outages last quarter."
Make it visible: keep a list of known debt with an estimated cost and risk.
Propose a plan: reserve a fixed share of each sprint (for example 10 to 20 percent), or fix the debt near the code you are already changing.
Prioritise the debt that slows the team most.
Some debt is acceptable if it is deliberate and recorded.
Markdown for AI
A clean, structured version of this page for AI assistants and LLMs.
We use cookies to ensure you have the best browsing experience on our website. By using our site, you
acknowledge that you have read and understood our
Cookie Policy &
Privacy Policy.
Technical debt is the extra work you will have to do later because of shortcuts or poor design chosen now. Like financial debt, borrowing can be a good decision (to hit a deadline), but you pay interest: every feature becomes slower to build, bugs increase and new developers struggle.
An analogy for non-technical people: a restaurant kitchen where staff skip cleaning during the busy season. At first they serve more orders, but soon things get slower, food safety becomes a risk and eventually the kitchen must close for a deep clean.
How to present it:
Some debt is acceptable if it is deliberate and recorded.