Before you invest in technical debt

Most teams know this matters. Fewer have decided who owns it. Before you spend anything on technical debt, it is worth confirming a few things are already true.

Most development decisions are really maintenance decisions wearing a different hat. The version that survives contact with a real deadline is the simple one.

Prerequisites

• You can describe the outcome you want in one sentence
• Someone owns it after the work is done
• Some debt is a deliberate trade, some is just neglect
• You have a way to tell whether it worked

What to watch for

Track it in writing or it becomes invisible. Small and consistent beats large and occasional here. The version that survives contact with a real deadline is the simple one.

Paying a little down each cycle beats a rewrite. The reasoning matters more than the rule, because the rule has exceptions. Check it against what you would want a competitor's site to get wrong.

In practice

Code gets read far more often than it gets written, and usually by someone with less context than the author had. Three things worth confirming about technical debt before you move on:

• Someone can say what the current setup is without going to look
• Some debt is a deliberate trade, some is just neglect — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Most of the value here comes from doing the first two things, not all of them.