Banking Technology Breakfast pt3

Pragmatic insights for effective core platform modernisation.

For part 3 of our Banking Technology Breakfast series, we gathered senior leaders at 1 Lombard Street to talk about a pressing issue across the industry: integrating core platforms after an event – be it a merger, acquisition, or partnership with a FinTech.

Our executive panel came from a range of backgrounds, but one thing they could agree on: effective implementation is rarely straightforward, and requires a pragmatic approach to get right.

Migrations are about people, not technology

Core platform modernisation is often framed as a technology challenge. In reality, it is a human one.

Programmes of this scale can test the emotional endurance of an organisation. CEOs can lose patience, individual contributors can lose sight of the vision. The longer the timeline, the greater the risk of fatigue and attrition – for both decisionmakers and individual contributors. In this light, stakeholder management becomes a discipline in its own right. 

One trick suggested by an executive was to define clear ownership of each area of a platform implementation to ensure long-term engagement in the business. Successful implementations prioritise unifying intent over unifying the systems themselves. Programme leaders, be it a CTO or COO, can lead the migration itself, but the outcomes should be sponsored across the C-suite to ensure accountability and shared commitment.

And modernisation doesn’t take place in the boardroom alone. Change often begins one level below the executive tier, where operational leaders feel the pain of legacy systems most acutely. They understand that scalability, multi-region support and speed of change are not abstract goals but daily necessities. Engaging people at this level – whether in building the business case or in the delivery phase – is essential for a successful implementation. 
 

Always act sooner rather than later

A theme that echoed throughout the discussion was the importance of timing. Banks often find themselves at a crossroads: Do you implement early, or hold delivery to perfect the solution? 

One gives you faster time to value and greater momentum; the other, more stability at launch, compliance readiness, and a higher chance of customer delight.

But platform implementation doesn’t happen in a vacuum. It needs to factor in everything from internal politics, capacity, client demands, to external market conditions. 

Regardless of the size of bank, one thing the panellists agreed is that waiting for perfect conditions is a mistake. “You’ll never be ready, so go early rather than late,” advised one executive. Even if internal conditions are aligned, the world does not stand still; geopolitical shocks and market volatility can derail even the best-laid plans, disrupting management sponsorship or hindering compliance efforts.

Given the scale of a platform migration or integration, the only way to guarantee momentum is by committing early. If it took 30 years to refine a platform, it will not be rebuilt in two. The more successful outcomes around the table came from committing early and learning as the project progresses.
 

Implementation is the endgame

The “cardinal sin” of an implementation project, one executive said, is failing to actually implement.

Delayed platform integrations can take a toll on both the customer and internal teams, so it’s important to forward-plan with achievable outcomes in mind.

Banks cannot afford disruption when undergoing transformation. Customers expect continuity. Core features – payments, loans, account access – must remain uninterrupted and responsive. Any break in services will likely risk churn. In this light, operational efficiency becomes paramount.

Prolonging implementation can also take a toll on your organisation as technical debt compounds over time. Some institutions now track a “spend on systems” metric to measure the cost of complexity and prioritise remediation. To limit the internal cost of inefficiency, the mantra is simple: decompose to recompose. Strip away redundant steps, unify intent, and reimagine the processes rather than the systems. Replacing everything is rarely faster than adapting what exists, and without process re-engineering, new architecture simply replicates old inefficiencies.

With these in mind, a once complex implementation project becomes much more actionable, thus more likely to succeed.
 

Conclusion

Platform modernisation is not a sprint, nor is it a pure technology play. It is a test of organisational resilience, operational discipline and strategic clarity. Success depends on people as much as systems, on pragmatism as much as ambition. Act early, steady the ship, and never lose sight of the customer. The banks that master these principles will not just modernise, they will endure.

We’ll be hosting part 4 of our Banking Technology Leaders series in Q1 next year. Get in touch to register your interest. 
 

Get In Touch