Technical debt register

What it means

A technical debt register makes debt visible as specific work rather than a vague complaint. A useful entry describes the affected area, the tradeoff that created it, the current interest or risk, an owner, and a review condition. The register should be pruned when items are resolved or no longer relevant.

Example

A register entry records that a synchronous adapter limits throughput, names the owning team, links evidence, and states that it should be revisited before the next volume increase.

Limitations

A register becomes ceremonial when it contains unbounded wish lists with no prioritization. Not every imperfect design deserves an item. Tie entries to observed cost, risk, or a credible future trigger.

How to use the signal

Prune resolved or irrelevant entries regularly, otherwise the register becomes a wish list that cannot guide capacity.

Weave can help connect register items to change frequency, blocked time, and rework. Keep prioritization with the owning team and use Weave evidence to support a measured decision.