Stop calling it technical debt. Your legacy system is an asset with a known risk profile.

'Technical debt' is a metaphor borrowed from finance. The idea: shortcuts taken now accrue interest over time.

It's a useful frame for code quality. It's a poor frame for legacy systems.

'Debt' implies you owe something. That you made a mistake. It breeds shame, paralysis, the feeling that you're already behind.

And it leads to bad decisions - panic migrations, rushed rewrites, expensive consultants arriving with a clean-slate proposal.

Here's a different frame: your legacy system is an asset with a known risk profile.

It has value: the business logic it encodes, the data it holds, the processes it enables.

It has risks: dependence on specific people, hardware age, vendor support status, integration gaps.

That's a risk management problem. Which means it's solvable. Measurable. Prioritisable.

You don't panic about a risk profile. You assess it. You address the highest risks first. You plan the rest.

This is how we approach it at Legacymigrations when we walk into an IT function. Not 'what a mess' - 'what's the actual risk, and where does it sit?'

It's a calmer conversation. It leads to better decisions. And it starts with an honest assessment - not a sales pitch.