Technical debt is one of the most misused terms in software. Teams use it to justify rewriting working code. Managers hear it as "engineers want to play with new tools." Neither interpretation is helpful.
Technical debt is a deliberate trade-off: you accept a known shortcut today to ship faster, with the understanding that you will pay the cost later. The problem is not the debt itself. It is losing track of what you owe.
## Good debt vs bad debt
Good technical debt is intentional and documented. You hardcode a configuration value because the admin panel is not built yet. You skip input validation on an internal tool that only three people use. You deploy a monolith because microservices would add six weeks to the timeline.
Bad technical debt is accidental and invisible. Copy-pasted code with subtle variations. Undocumented API contracts that only the original developer understands. Test suites that pass but do not actually test the important paths.
## When to pay it down
Pay down technical debt when it actively slows feature development. If adding a new payment method takes three weeks because the payment module is tangled, that is a signal. If onboarding a new developer takes a month because the codebase has no clear structure, that is a signal.
Do not pay down debt just because the code is old or because someone read a blog post about clean architecture.
## How we track it
Every intentional shortcut gets a comment in the code with a TODO tag and a ticket in the backlog. During sprint planning, we review the debt backlog and pull in items when they block or slow current work.
This approach prevents both extremes: ignoring debt until it buries you, and spending all your time refactoring instead of shipping features.
## The business case
Technical debt compounds like financial debt. A shortcut that saves a week today might cost a month six months from now. But a product that ships three months late because the team was perfecting the architecture might not have users at all. The skill is knowing which debts are worth taking and which ones will bankrupt your velocity.