How Building Societies can get Transformation Right

Let’s be honest: a number of building societies, in common with a number many industries, have likely underinvested in technology transformation for years.

It could be argued that they haven’t had to — protected by loyal customers and a conservative market. But with challenger banks rewriting the rules and traditional banks doubling down on digital services, the days of standing still are arguably over. Building societies are now in a tightening vice, squeezed by agile newcomers and powerful incumbents. Transformation is no longer a nice-to-have – it’s a matter of survival.

But here’s where things often go wrong.

Transformation is not much more than a technical install

Too many building societies view transformation as little more than a “technical upgrade” – buy a shiny new platform, plug it in, job done, but we know from experience that that mindset is flawed. Real transformation isn’t about replacing a system; it’s about changing how your business operates. It touches your people, processes, culture, governance, and customer experience. You have to adopt the mindset that it’s a change programme first, and a technical upgrade second. Ignore that, and you risk delivering an expensive, disruptive IT project that doesn’t deliver value.

The Problem with (Some) Technical Vendors

Technology vendors are great at technology. They’ll sell you the latest cloud-based, API-rich, open-architecture, regulatory-compliant platform. But ask them to lead a structured business transformation programme, govern risk across stakeholders and drive behaviour change across you organisation (whatever its size)? Well, as we know that’s significantly more of a challenge.

If you’re relying on your software provider to also lead your business through a once-in-a-generation change, you’re probably asking too much.

Legacy Culture, Legacy Systems

Let’s not ignore the elephant in the room: most building societies are 150+ years old. That heritage is a strength — but can also be a burden. Institutional memory is deep, but so is inertia. Some of the core systems still in use are most likely older than the people reading this article. Codebases written in COBOL or other legacy languages are hard to maintain, and harder still to replace.

Meanwhile, technical talent — the kind needed to navigate a transformation — is being pulled elsewhere. Young developers don’t dream of working on 1980s architecture in a heritage brand. Your in-house knowledge might be walking out the door due to retirement, redundancy, or just sheer frustration.

Change isn’t in the DNA (Yet)

It gets worse. Like many organisations, most building societies lack the in-house change capability required to deliver complex transformations. That’s entirely understandable — and nothing to be ashamed of. After all, your core expertise lies in lending and savings, not in navigating large-scale change programmes that may only occur once every 15 or 20 years. The likelihood that your current team has previously led a similar transformation is, realistically, quite low. That’s why it makes sense to bring in experienced partners. Without that support, even the most well-intentioned programmes can quickly run into issues — governance gaps, decision paralysis, resourcing shortfalls, and cultural resistance.

And while you’re figuring that out, customers have already changed. They expect slick digital experiences, 24/7 support, self-service options, and instant resolution. If you’re not there yet, they’ll take their savings elsewhere.

Ok, so what can we do about it?
Transformation is hard — especially when it involves unpicking 40 years of architecture, legacy processes, and outdated assumptions. But it can be done, and it can be done well. Here are four proven ways to de-risk the journey:

1. Use a Partner with Real Experience
Not a software house. Not a PowerPoint consultancy. A delivery partner who has actually transformed legacy financial systems in real-world, high-risk environments. Someone who understands governance, risk management, business change and delivery — and won’t just smile and nod when things get tough.

2. Don’t Go Big Bang
The temptation to “rip off the plaster” and do everything at once is understandable — but dangerous. Big bang transformations introduce high levels of risk, especially when dealing with aged infrastructure and mission-critical services. Instead, move in manageable increments and prove success along the way.

3. Run a Proper Proof of Concept (PoC)
Before you commit to a full-scale rollout, validate your approach with a PoC that focuses on the most difficult and business-critical integrations. If your core system can’t talk to your CRM or payments platform, you need to know that early — not six months in. Prove the thorniest elements first, build the team’s confidence, start that successful delivery cadence, then scale with confidence.

4. Phase based on Business Need and Capability
Don’t let your system architecture dictate your rollout plan. Structure your transformation around business needs and internal capability. Group your integrations and changes into sensible, value-driven phases. Align them to your people, your culture, and your ability to absorb change. Build your “doable plan” from there — and update it often.

Final Thought
Building societies are at a crossroads. You can cling to the comfort of legacy systems and hope your customers stay loyal — or you can face into the challenge, transform your operation, and secure your relevance for the next generation.

Transformation is uncomfortable. It’s disruptive. But it’s also where the opportunity lies. With the right plan, the right partners, and the right mindset, building societies can evolve without losing what makes them special.

So don’t wait for a perfect time. It’s already here. And standing still is the riskiest move you can make.

Are you ready to embrace the right kind of failure on your change journey?

Let’s talk.