Part Two of the Guiding Lights series, by CTO Chelsea Chamberlin
The systems that don’t quite talk to each other. The processes everyone works around. The decisions that were right once — but no longer are.
It’s easy to tell yourself that this is just how things are. That the old systems are “too embedded” or the data “too messy” to fix. But denial (or deliberate ignorance) is a strategic risk — and the longer you leave it, the harder it gets to do anything about it.
The truth is, legacy isn’t the problem. It’s the neglect around it that does the damage.
Facing up to “legacy gaps” is an act of leadership. It means admitting that what got you here might not get you there — but also recognizing the value in what you’ve already built. These systems, relationships, and processes were designed for a reason. The challenge now is to look at them with fresh eyes and ask: *Are they still serving that purpose?*
Too often, legacy is treated like clutter — something to clear out rather than care for. But inside those systems are years of refinement, expertise, and embedded knowledge. They’ve kept the lights on, processed millions of transactions, and carried institutional memory through change after change.
Legacy doesn’t make you slow. What makes you slow is refusing to evolve.
This is where the best leaders make a conscious pivot: from blame to ownership. They don’t apologise for their history — they use it. They treat legacy as a live asset, not a relic.
Progress starts with honest reflection. Not the kind that fills a slide deck, but the kind that looks under the surface and asks awkward questions:
This kind of self-examination can be uncomfortable — but it’s far cheaper than a failed transformation. The organizations that make real progress are the ones brave enough to confront their blind spots early, before those inefficiencies become vulnerabilities.
Every legacy platform, every manual process, every “temporary fix” tells you something about your culture. Where you compromise. Where you excel. Where you stop listening. If you can see those patterns clearly, you can change them.
Turning legacy into leverage takes more than good intentions. It needs structure, clarity, and a bit of grit.
You can’t change what you can’t see. A transparent view of your systems, integrations, and dependencies stops problems hiding in plain sight. It turns risk into information — and information into power.
No more working in silos. The technical, operational, and financial teams need to see themselves as co-owners of the same challenge. When the people who understand the tech are invited into the room early, the conversation changes, and once impossible risks to resolve suddenly make room for new solutions.
The people closest to the systems often know what’s possible — but they need permission to say it. Trust your experts. Let your technical teams and analysts advise, not just deliver.
Don’t wait for the perfect moment or the perfect plan. Transformation happens in layers. The point isn’t to get it all right on day one — it’s to build momentum, reduce risk, and keep learning.
The organizations that handle legacy best are the ones that treat improvement as a continuous cycle, not a crisis response.
What this really comes down to is mindset. If the first two pieces in this series were about constraint and focus, this one is about confidence. The quiet belief that you will make the right choice. Perhaps you already have what you need, whether it’s people, process, or data — you just need to use it better. Or perhaps it is time for a radical reinvention – either way, being sure that you decision is rooted in data, outcomes and intent is the only confidence you need.
No panic. No shame. Just the discipline to look at what’s in front of you and ask, “How can this work better for us?”
That might mean upgrading selectively instead of wholesale replacement. It might mean using new tech to fill the gaps rather than rebuild from scratch. It might simply mean identifying that part of your ‘outdated’ system still works beautifully — and protecting it.
Change doesn’t always come from revolution. More often, it comes from alignment and integration — of people, systems, and priorities.
When you stop treating legacy as a liability, you start seeing it for what it really is: proof. Proof of resilience, experience, and the ability to evolve.
CIO’s know perhaps more than any other executive that the combination of budgetary and talent constraints mean the work ahead isn’t about starting over. It’s about building on the strength you already have. About making choices that are smart, sustainable, and true to your organization’s identity and achieving this through collaboration between functional areas, early risk analysis, and adopting continual improvement as a cultural pillar.
Because in the end, legacy isn’t the thing holding you back. It’s the platform that got you this far — and, at least some elements of it, will provide the foundations on which you’ll stand to transform further.
Tap into Chelsea’s expertise for insights on the trends, tools and AI helping to shape the future of technology.
Spark the conversation with Chelsea