This article is based on reporting originally published by InformationWeek, drawing on commentary from Richard James, Ways of Working Enablement Leader at Nationwide Building Society.
A 100-Year-Old Institution Facing a Digital Threat
Longevity in financial services is no longer a sufficient competitive moat. Britain-based Nationwide Building Society — a cooperative financial institution with more than a century of history — recognised that its experience alone would not protect it from the wave of digital-first challengers reshaping retail banking.
According to Richard James, Nationwide’s Ways of Working Enablement Leader, the pressures are structural as much as technological. “Within the industry, retail banking is an increasingly hard place to be sustainable,” he said, pointing to a prolonged low-interest-rate environment that compresses margins across the sector.
The Scale and Complexity of Nationwide’s IT Landscape
Nationwide serves approximately 16 million members with mortgage, savings, personal banking, and credit card products. Members interact through branches, digital channels, and contact centres — all underpinned by a broad technology stack that includes CRM systems, data warehouses, and a growing multi-cloud footprint spanning both on-premises and off-premises infrastructure.
That complexity is compounded by history. Nationwide has completed more than 100 mergers over its lifetime, inheriting a wide range of legacy systems with each acquisition. As James put it: “The technical landscape is relatively broad because of the history of what we’ve inherited and merged with.”
Managing this inherited estate while simultaneously modernising for digital delivery is a challenge familiar to many large financial institutions — and it is precisely the kind of problem DevOps practices are designed to address.
Adopting DevOps and Continuous Delivery
Nationwide’s response was to embrace DevOps methodology, with a particular focus on continuous integration and continuous delivery (CI/CD). The organisation worked with CloudBees to introduce automation into its software delivery pipeline, reducing the manual overhead associated with integrating and releasing code changes.
The strategic intent went beyond tooling. James described a goal of shifting effort away from maintaining the existing IT environment and toward active software development and innovation. “With the advance of the age of digital,” he said, “members need us to be more adaptive, experimental, and more able to engage and rapidly meet their needs.”
Inspiration came partly from observing how younger software companies organise their engineering work. Nationwide aimed to embed what James called “the three ways of DevOps” — flow, feedback, and continuous improvement — into its operating model. These principles, popularised by Gene Kim and colleagues in works such as The Phoenix Project and The DevOps Handbook, provide a framework for aligning development speed, system reliability, and organisational learning.
Expanding the Scope: From Dev and Ops to BizDevSecOps
As Nationwide matured in its DevOps journey, the scope of the initiative broadened considerably. James highlighted exploration of disciplines such as cyber liability, software engineering practices, and deeper collaboration on digital channels. Concepts like toil reduction — eliminating repetitive manual operational work — and error budgets — a reliability engineering technique for balancing feature velocity against system stability — entered the conversation.
Perhaps most significantly, the initiative evolved from a technology programme into an organisational alignment effort. “What could have been a technology-focused initiative around dev and ops has become much more about how we bring together biz, dev, sec, ops in service to our customers,” James said.
This shift — sometimes described as BizDevSecOps — reflects a growing recognition that sustainable digital delivery requires breaking down silos not just between development and operations teams, but between IT and the business units that depend on it.
Bridging Business KPIs and IT Metrics
One concrete outcome of this broader framing is the way Nationwide began thinking about measurement. Rather than maintaining separate scorecards — IT operational metrics on one side and business KPIs on the other — the organisation started working toward a unified view that ties system performance directly to customer and commercial outcomes.
This approach has a practical benefit beyond dashboards: it gives technology teams a credible voice in leadership discussions. When engineers can speak in terms of customer impact and business value — not just system uptime and deployment frequency — they earn a seat at the table alongside product and commercial leaders.
Key Takeaways for DevOps Practitioners in Financial Services
- Legacy complexity is manageable. A sprawling, merger-acquired technology estate does not prevent DevOps adoption — but it does require deliberate prioritisation and phased automation.
- Tooling is an enabler, not the goal. Nationwide’s use of CloudBees for CI/CD automation supported a broader cultural and organisational shift, not just a pipeline upgrade.
- Reliability engineering concepts translate to regulated industries. Toil reduction and error budgets are not exclusive to cloud-native startups; they apply wherever operational sustainability matters.
- Alignment beats division. Separating IT metrics from business KPIs creates misaligned incentives. Linking them drives shared accountability and better outcomes.
- Security must be part of the model from the start. In a regulated financial environment, DevSecOps is not optional — it is a prerequisite for sustainable delivery.
Nationwide’s experience illustrates that DevOps transformation in a large, regulated institution is neither quick nor simple — but it is achievable, and the competitive case for it is clear. Digital challengers do not carry the burden of legacy infrastructure, but they also do not carry 16 million member relationships built over a century. DevOps gives established institutions a way to modernise without abandoning the trust they have earned.