Over the past few years, I’ve spent a lot of time with Clinical Engineering teams across NHS Trusts.
Not in boardrooms.
Not in glossy innovation sessions.
But in workshops, equipment rooms, service corridors, and conversations where people are trying to solve very real problems with very limited time.
These conversations come from working alongside Clinical Engineering teams across acute hospitals and community services — where asset visibility, compliance pressure, and time lost searching are daily realities.
What strikes me is not a lack of effort, ambition, or professionalism. Quite the opposite.
What strikes me is how consistent the challenges are, regardless of Trust size, geography, or estate complexity.
Different places.
Same pressures.
What Clinical Engineering Teams Keep Telling Us
When Clinical Engineering leads talk openly, the themes are remarkably familiar — and we hear them repeatedly, not as one-off complaints but as systemic constraints that surface across almost every Trust we engage with:
- Responsibility for thousands of assets, many of which are mobile and shared
- Increasing compliance and regulatory pressure, with little margin for error
- Time lost searching for equipment instead of maintaining it
- Assets disappearing into community settings with limited visibility
- Buying or hiring more equipment because it’s faster than finding what already exists
- Innovation feeling risky, because failure feels personal and visible
None of this is about a lack of capability.
It’s about operating in a system where the cost of not knowing is rising, while the tools to reduce that uncertainty haven’t kept pace.
Clinical Engineering teams are expected to manage risk, availability, safety, and cost — often without the data or visibility that would make those decisions easier.
That tension is not sustainable.
Reframing Innovation for Clinical Engineering
“Innovation” is one of the most overused words in the NHS.
For many teams, it has come to mean:
- Big programmes
- Long timelines
- Heavy procurement
- High scrutiny
- And very little that helps next week’s problem
But that version of innovation has very little to do with what Clinical Engineering actually needs.
From a CE perspective, innovation isn’t about transformation.
It’s about reducing unknowns.
It’s about:
- Knowing where assets are
- Knowing which ones are compliant
- Knowing what’s actually being used
- And making decisions with evidence rather than assumption
In other words, innovation in Clinical Engineering is operational, pragmatic, and risk-reducing — when it’s done properly.
What Manufacturing Taught Me About Flow, Visibility, and Empowerment
Earlier in my career, I spent many years working in manufacturing environments. Healthcare and manufacturing are obviously very different industries — but some of the lessons are surprisingly transferable.
The environment is different, but the pressure of managing flow under constraint — with limited time, limited resources, and real consequences when things stall — is surprisingly familiar.
In manufacturing, organisations live or die by flow. Inventory, work in progress, and orders move through multiple work centres, and the challenge is always the same: how do you convert effort into output efficiently and predictably?
What I learned very quickly is that flow only works when three things are true.
First, you need up-to-date information. Decisions about resources, priorities, and bottlenecks can’t be made on yesterday’s data. In fast-moving environments, even small delays in visibility create outsized disruption.
Second, you need a clear cadence. In manufacturing, that cadence might be daily or weekly. Problems are surfaced early, adjustments are made quickly, and teams closest to the work are trusted to act within clear boundaries.
Third — and most importantly — you need to empower the people closest to the problem. Bottlenecks don’t get resolved in boardrooms. They get resolved where work actually happens.
When I later spent time inside NHS organisations, much of this felt familiar.
Patient flow places demand across multiple services at once. Pressure builds at bottlenecks. Small delays ripple into bigger ones. And when visibility breaks down — particularly around equipment availability — the whole system feels it.
The principle is simple: having the right people, in the right place, at the right time, with the right equipment creates capacity. Without visibility, that capacity can’t be monitored, protected, or improved.
Healthcare is not an assembly line, and it never should be. The NHS runs on professionalism, goodwill, and an extraordinary commitment to patient care. But in such a dynamic, stretched environment, live information becomes essential — not to control people, but to support them.
What manufacturing taught me is that simplification beats perfection. Small, staged improvements. Real-time data. Clear ownership. And leadership that creates space for teams to solve problems rather than pushing solutions down from above.
Those principles don’t diminish healthcare. They respect it.
What This Looks Like in Practice for CE Teams
When innovation works for Clinical Engineering, it tends to share a few characteristics:
- Start with one clearly defined problem, not the whole estate
- Focus on one asset type or pathway, not everything at once
- Work in short, deliberate cycles
- Learn quickly what does and doesn’t add value
- Prove benefit before committing to scale
This isn’t about bypassing governance or ignoring risk.
It’s about recognising that the risk of doing nothing — continuing to operate with partial visibility while pressures increase — is rarely neutral.
Small, contained experimentation can actually lower long-term risk, not increase it.
Giving Teams the Space to Solve Their Own Problems
One of the most important shifts is cultural.
Clinical Engineering teams are full of people who understand their problems better than anyone else. What they often lack is time, space, and autonomy to address them properly.
Innovation doesn’t require heroic programmes.
It requires:
- Protected time
- Clear boundaries
- Leadership support
- And permission to start small
When that space exists, solutions tend to emerge naturally — and they’re far more likely to stick.
A Practical Starting Point
As budget windows tighten and 2026/27 planning accelerates, we’re seeing more Clinical Engineering teams choose to begin with a small, contained Proof of Value.
Typically:
- Around £5k
- Focused on a specific, known challenge
- Designed to fit around existing pressures
- Run at the Trust’s pace, not ours
The aim isn’t to “roll out a system”.
It’s simply to answer a question:
Does this help us see what we can’t currently see — across acute and community settings — and does that make our job easier?
If it does, teams decide what happens next.
If it doesn’t, they’ve learned something valuable without committing further.
That choice — and that control — matters.
A Final Thought
Clinical Engineering teams already carry enormous responsibility for patient safety, compliance, and operational resilience.
Innovation, when it’s done well, should make that responsibility lighter, not heavier.
If any of the challenges above resonate, the first step isn’t a project or a platform.
It’s just a conversation — about what you’re seeing, what’s getting in the way, and whether a small, practical step could help.
That’s where meaningful change usually starts.
– Fen