A team's technical debt backlog contains hundreds of items and never shrinks. How should debt be managed?

Why the backlog never shrinks

Items are added when noticed and prioritised never, because each is small, none has a business case, and all compete against features. A list of hundreds is not a plan; it is a record of dissatisfaction.

It also conflates several different things under one label: genuine deliberate trade-offs, accidental mess, outdated technology, missing tests, and things one engineer dislikes.

How to manage it

1. Separate the categories. Deliberate debt taken for a reason has a repayment trigger. Accidental mess is fixed by the ratchet. Preference is not debt.

2. Attach a cost of inaction to each item, per quarter. Incident time, change lead time in that area, features refused, engineering time consumed by workarounds. An item with no stated cost of inaction will always lose to an item with a stated benefit, which is why the backlog does not move.

3. Rank by cost of inaction times change frequency. Debt in code nobody touches costs nothing. Debt in the area changed weekly costs continuously. This ranking usually reduces the actionable list dramatically, which is the point.

4. Fix by ratchet, not by project. New code meets the standard; existing code improves when touched, with automated checks enforcing the boundary. Most items are then fixed as a side effect of ordinary work in the areas that matter.

5. Delete aggressively. Items proposed three times and never prioritised are not going to happen, and a list containing them misleads about capacity.

6. Track the leading indicators rather than the item count: change lead time, change failure rate, incident frequency by area. These are what debt actually costs, and they make the argument in the language the business decides in.

The framing that gets it funded

Not "we have technical debt" but "changes in this area take six weeks instead of one, across forty changes a year, and here is what fixing it costs". That competes; a backlog does not.

The prevention

Deliberate debt is recorded with a trigger and an owner at the moment it is taken. Undocumented shortcuts become the architecture by default, because nobody remembers they were meant to be temporary.