When The System Outlives The Generation That Built It

There’s a liability sitting quietly at the heart of many financial services organisations. It doesn’t appear on the balance sheet. It rarely features in risk committee papers. But it compounds steadily, year by year.

Decades ago, the pattern made perfect sense: implement a best-of-suite core system and platform, take the modules appropriate to your business, and invest in customisation to fine-tune it to your precise requirements. The result was often a remarkably capable platform — shaped by talented people who understood the business deeply, and built to last.

The problem is what “built to last” actually means in practice.

Research on technology adoption and the workforce makes a compelling observation: it is not the technical lifespan of a system that determines how long it endures in an organisation — it is the working tenure of the generation that introduced it. The professionals who implement an enterprise system in the early or middle years of their careers tend to remain its stewards until they approach retirement. Their institutional knowledge, the context for why certain customisations were made, the workarounds that became workflows — none of this is documented anywhere. It lives with them.

As that generation moves on, the knowledge base shrinks. Knowledge transfer requires time, willing participants, and motivated learners — and there are not many ambitious professionals eager to invest years mastering a platform that was configured before they were in secondary school.

The result is an organisation increasingly dependent on systems it understands less and less well.

The “big bang” era — and why it left so many organisations stranded

For years, the assumed solution was total replacement: tear out the monolithic core and everything built around it, and install something new. In practice, this approach failed more often than it succeeded. Programmes ran years over schedule, consumed hundreds of millions beyond budget, and in some cases were abandoned entirely. By the time a new system finally arrived, the business requirements and regulatory landscape had moved on. You had answered a question that had changed.

A better model is now well-established

More than half of mid-market financial institutions now favour progressive transformation — a gradual, modular approach that replaces specific components based on the reason and urgency for change, rather than attempting wholesale replacement all at once.

The landscape shifts incrementally: modern specialist applications are onboarded for specific requirements — payments, digital onboarding, risk, customer experience — each integrated via APIs, each delivering value, each reducing dependence on the legacy core without requiring the entire architecture to be dismantled. What was once a single, mammoth, customised system gradually becomes a modular ecosystem of fit-for-purpose applications, more maintainable, more legible to a new generation, and far better positioned to support growth.

The question isn’t whether. It’s when — and in what sequence.

The generation that understands the current systems most deeply is moving, year by year, toward the end of their working lives. The window for structured transition is narrowing. And the distance between what legacy architectures can deliver and what customers, regulators, and competitors demand grows wider.

At Quantum Six, we bring depth and practical experience to exactly this challenge — helping financial services organisations understand where they are, design a realistic path forward, and begin moving with confidence rather than waiting for conditions that may never feel quite right.

If your organisation is navigating this transition, we’d welcome the conversation.

Get in touch with Quantum Six to discuss.