One thing I’ve noticed over the years is that NHS organisations rarely struggle because they lack ambition.
Whether it’s a new Electronic Patient Record programme, improved interoperability between services, better use of data, cloud adoption, or modernising ageing infrastructure, there is no shortage of ideas. Most Trusts, Commissioning Support Units and national bodies have well-developed strategies and a clear understanding of where they want to go.
The challenge is usually something far less exciting.
It’s finding the time, capacity and operational headroom to deliver tomorrow’s projects while keeping today’s services running.
That tension sits at the heart of almost every transformation programme. The same technical teams responsible for implementing new platforms, migrating services and supporting innovation are often the people dealing with incidents, patching systems, responding to security alerts and maintaining critical infrastructure. When operational demands increase, transformation work is often the first thing to slow down.
The Transformation Paradox
Digital transformation is often presented as something separate from day-to-day operations. In reality, the two are inseparable.
A Trust may have funding approved for a major digital programme. A CSU may be investing in new population health management capabilities. A national NHS body may be modernising a large-scale cloud platform. On paper, these initiatives are projects. In practice, they rely heavily on operational teams who already have full workloads.
The challenge isn’t usually a lack of commitment. It’s that the people with the skills needed to deliver transformation are often the same people keeping existing services alive.
I’ve spoken to many IT leaders who find themselves in this position. Their most experienced engineers are capable of delivering significant change, but instead spend much of their time managing technical debt, maintaining legacy systems, troubleshooting issues and dealing with operational interruptions. The organisation wants to move forward, but the people who could help make it happen are busy ensuring nothing falls over today.
When Keeping the Lights On Becomes the Full-Time Job
None of this should be interpreted as a criticism of operational work. Keeping systems secure, available and performing well is fundamental, particularly in healthcare where service interruptions can have far-reaching consequences.
The problem arises when operational demands consume so much capacity that improvement work continually gets postponed.
Perhaps a cloud migration is delayed because key engineers are tied up supporting ageing infrastructure. Maybe an interoperability project slips because the team is focused on patching and security remediation. Sometimes a new digital service reaches the planning stage only to discover that the people needed to implement it simply don’t have enough time available.
Most NHS leaders will recognise these scenarios. The issue isn’t usually the project itself. It’s the competition for finite technical resources.
What often gets overlooked is the role infrastructure stability plays in creating that pressure. The more fragile or labour-intensive an environment becomes, the more attention it demands. Over time, technical specialists can find themselves spending the majority of their week maintaining systems rather than improving them.
Why Infrastructure Matters More Than Most Transformation Plans Acknowledge
Successful transformation programmes tend to focus on visible outcomes. Better patient experiences. Faster access to information. Improved data quality. More efficient services.
What receives less attention is the operational foundation that makes those outcomes possible.
Many critical NHS systems depend on Linux somewhere within the stack. It may sit beneath integration platforms, databases, analytics environments, cloud services or clinical applications. Most users never see it, and that’s exactly how it should be. Infrastructure is doing its job when nobody notices it’s there.
The difficulty comes when that foundation becomes unstable, under-resourced or overly dependent on a small number of individuals. Suddenly, projects that should be focused on delivering new capabilities become distracted by maintenance, firefighting and risk management.
In many organisations, transformation doesn’t stall because the vision is wrong. It stalls because the foundations beneath it require more attention than anticipated.
Creating Capacity For Change
The NHS organisations that make the most progress with transformation are often the ones that recognise operational resilience as an enabler of change rather than a competing priority.
They understand that creating capacity is just as important as creating capability.
That might involve investing in automation to reduce repetitive tasks. It may mean improving documentation so knowledge isn’t concentrated in a handful of individuals. It could involve standardising environments, strengthening monitoring, or adopting more proactive approaches to maintenance and support.
There is no single model that suits every organisation. Some will expand internal teams. Others will use specialist partners to supplement in-house expertise. Many will adopt a combination of both.
The important point is that operational work is managed in a way that allows valuable technical staff to spend more time contributing to strategic objectives and less time dealing with avoidable distractions.
Transformation Depends On Stability
The NHS will continue to pursue ambitious digital programmes over the coming years. That is both necessary and welcome.
But transformation doesn’t happen in isolation. It relies on secure, reliable and well-managed infrastructure. It depends on technical teams having the capacity to focus on improvement rather than spending all their energy maintaining the status quo.
Linux itself is rarely the headline. Few transformation programmes begin with a discussion about operating systems. Yet many depend on Linux-based platforms somewhere beneath the surface, quietly supporting the services and applications that make modern healthcare possible.
That’s why Linux stability is more than a technical concern.
It’s a transformation concern.
Because when infrastructure becomes easier to manage, technical teams gain something increasingly valuable: the time and space to focus on what comes next.
Want to Give Your Team More Time for Transformation?
If your internal specialists are spending more time maintaining Linux systems than helping deliver strategic projects, it may be worth taking a fresh look at how that work is managed.
Tiger Computing helps NHS organisations strengthen Linux stability, reduce operational pressure and free technical teams to focus on higher-value work.
If you’d like to talk through where your team’s time is going today, and where specialist support might help, we’d be happy to have a short conversation.
