Author: GHA Marketing
25 March 2026
Healthcare organizations feel stretched every day. Demand keeps rising, budgets stay tight, and staff feel the strain. Many teams work hard from morning to night, yet progress still feels slow. Leaders plan for the future, but daily pressure keeps pulling focus back.
As a result, people end up firefighting instead of improving care. This creates a shared frustration. Everyone wants clearer direction, but the system often feels heavy and slow. That tension raises an important question.
How should work, decisions, and leadership fit together so care improves, not just survives? This question sits behind every discussion about how organizations actually run.
Three experienced voices shape the ideas in this article. Alastair Mitchell-Baker, an experienced consultant and ex NHS CEO, interviewed:
John Deverill brings a wide background from the Army, engineering, and medical technology. He shows why many NHS structures feel too rigid and how data and digital twins can test new designs before change begins.
Andrew Liles draws on ten years as an NHS Chief Executive and now advises organizations on leadership and accountability. He talks openly about firefighting cultures and why staff must help design any new system.
In this article, we explain what an Operating Model really means in daily work. We show why many NHS structures feel rigid under pressure. We explore signs that design no longer supports delivery.
Moreover, we examine how co-design, data, and digital tools can help teams rethink their structure. Finally, we share practical lessons that leaders can use to bring clarity, confidence, and steadier progress back into everyday care.
An operating model explains how an organization gets its work done. It links purpose, strategy, people, processes, culture, and tools into one working system.
When this system fits well, people know what they’re aiming for and how they’ll get there. The work feels clearer, and decisions move faster.

Image Credits: Photo by Thirdman on Pexels
The model acts as the “how” behind the plan. Strategy sets the goal, but the operating model shows how the organization delivers that goal each day and over time. It brings together a few core pieces.
These parts must work from top to bottom, or things start to slip.
Many organizations spend a lot of time shaping the board and executive level, but the real test sits in the layers that run clinical services. That’s where daily issues show up and where a weak model becomes hard to ignore.
Some sectors are built for change, so they adjust with less pain. Their models expect shifts in tasks, tools, and environments. This mindset helps people reorganize quickly and carry on with confidence. It’s a clear advantage.
Healthcare doesn’t always have that ease. Many pathways and habits have grown over long periods. Training shapes people in fixed ways. Rules add even more weight. So change often feels slow, even when everyone wants things to improve.
When an organization hits its goals and people feel they can do their jobs, the model fits. When results slip, or confusion grows, it’s usually a sign that the model no longer supports the work. At that point, something needs to shift so the organization can move forward again.
Many organizations feel pressure to move from short-term recovery to steady, reliable delivery. That shift puts the operating model at the center because it shapes daily work, decision-making, and team confidence. When pressure rises, people don’t need to put in more effort. They need a clearer structure.

Image Credits: Photo by Vlada Karpovich on Pexels
Several forces now collide, which makes a review timely and necessary.
Together, these forces create tension. People want clarity, but they often get noise. They want to know their role, their manager, and how support works.
They want systems that help them do the job, not slow them down. When those basics feel unclear, frustration builds fast.
A familiar pattern keeps showing up. Teams plan for medium and long-term goals, but daily pressure eats all their time. Firefighting becomes normal. Improvement work keeps slipping. That’s not a people problem. It’s a design problem.
This pressure grows after mergers or restructures. Old ways of working stick around. Temporary fixes turn permanent. Different parts of the organization follow different rules. Over time, alignment fades, and confusion grows.
Some signals appear quickly and repeat often.
These signs matter. Effort stays high, but progress slows. People feel stretched, and trust in the system drops.
New financial rules and tighter plans demand a clear link between strategy and daily work. A refreshed operating model restores focus, reduces friction, and gives teams a structure that supports both today’s pressure and tomorrow’s change.
A review of the operating model works best when people understand why it matters and feel part of the process. The aim is to shape a model that supports real work, not one that adds confusion. Clear intent and steady involvement make that possible.

Image Credits: Photo by RDNE Stock project on Pexels
Leaders need to explain why the review is happening now. Without that context, people often assume cuts or major restructuring. A simple message helps.
It should link the review to what the organization must deliver over time. When people hear a clear reason, they feel less anxious and more open to the work.
A redesign lands better when people help build it. Creating a design group with staff from different levels and backgrounds brings in practical insight. It also shows that the work isn’t happening behind closed doors.
Co-design sessions help teams talk through issues that affect daily work, such as:
These conversations let people connect the design to their own roles. Moreover, they build a sense of shared ownership, which makes later change easier to absorb.
Good design needs evidence. Data helps people test ideas and see possible outcomes. Digital twins can show what happens when processes shift, when capacity changes, or when new roles are added. This makes the work feel grounded rather than theoretical.
As AI grows, teams can also model how AI-supported roles might fit into future structures. That keeps the design flexible and ready for change.
Looking at how similar or international organizations organize their work helps people think more widely. These examples give practical ideas and offer a sense of what’s possible. They can also challenge habits that no longer serve the organization well.
A mix of purpose, co-design, data, and external insight creates a redesign process that feels fair, clear, and genuinely useful.
Operating model redesign changes how an organization works in real life. It affects how decisions move, how teams work together, and how confident people feel doing their jobs. When the design fits the work, daily pressure eases, and progress feels possible.

Image Credits: Photo by Anna Shvets on Pexels
Well-designed work usually improves a few core areas.
When people help shape the model, commitment rises. They feel included and heard, not managed from a distance. That shared effort builds trust and gives teams more energy to try new ways of working.
Digital tools strengthen this process. Digital twins let teams test ideas before acting. They can see what happens when capacity shifts, pathways change, or teams adjust roles.
This removes guesswork and replaces it with evidence. Moreover, people trust change more when they can see its likely effect.
Some redesign efforts struggle for reasons beyond the organization. If partners don’t align, momentum drops. Weak links across budgets or information systems also slow progress.
Even strong local efforts can’t overcome those gaps on their own. That said, this shows why wider agreement matters so much in large-scale change.
Sharing leadership can unlock real energy. When responsibility spreads across clear areas, people step up with purpose. Teams solve problems quickly and rely less on escalation. The culture shifts toward ownership and action, and the organization feels more responsive.
Strong systems often use one shared operating model. They focus on joint outcomes and work together rather than in silos. This alignment lifts performance across the whole system, even when some parts struggle. It shows that shared design can raise results for everyone.
These examples show redesign isn’t a theory. It shapes behavior, builds confidence, and improves how work gets done when the model fits the purpose.
Strong delivery starts with how work actually runs each day. Strategy sets direction, but structure decides what really happens. When roles stay clear, decisions move faster, and teams feel less strain. That clarity does not appear by chance. It stems from design choices that align with real work.
When pressure rises, effort alone does not help. People need systems that support judgment, not constant escalation. However, many teams stay stuck because old setups linger too long. Temporary fixes turn permanent, and confusion grows.
Reviewing an Operating Model brings focus back. It reconnects purpose with daily action. It also gives leaders and teams a shared language to fix problems early. Moreover, co-design builds trust because people help shape what they must use.
No model stays perfect forever. Work changes, tools change, and expectations shift. That said, regular review keeps drift in check. If leaders treat design as ongoing work, delivery feels steadier. And progress stops feeling like a daily fight.
Most models remain useful for 3 to 5 years. However, big policy or technology shifts can shorten that time. If complaints rise and decisions slow, the model has aged. Regular small updates keep it fresh.
The chief executive owns it at the top. But daily ownership sits with operational leaders and managers. If only one office controls it, the model turns into paperwork. Shared ownership keeps it alive.
No, it can’t work well. Middle managers translate strategy into daily actions. They solve local problems and protect standards. Without them, decisions climb upward, and delays grow.
Yes, size changes how detailed the model must be. Small organizations need simple lines and few layers. Large systems need clearer rules and stronger coordination. One style does not fit all.
Culture decides whether people follow the design. A model can look perfect on paper and still fail. Trust, openness, and respect make the design real. Fear and blame break it fast.