A Rezilien whitepaper
Why the operating model now sets the limit on value creation in PE-backed healthcare.
By Lily Kyriacou · Founder, Rezilien · 2026
Healthcare transformation is most often framed as a strategy, technology, or leadership problem. In PE-backed healthcare businesses, the more consequential constraint sits one layer beneath, in the nature of execution itself, and in the operating model that quietly governs what the business can actually absorb.
Chapter I
The constraint on value creation has moved one layer beneath strategy.
Healthcare transformation is most often framed as a strategy, technology, or leadership problem. In PE-backed healthcare businesses, the more consequential constraint sits one layer beneath. The nature of execution itself is changing.
For much of the past decade, the prevailing model in healthcare has been product-led execution: a posture suited to regulated environments, controlled releases, and the protection of product and data integrity. For most organisations, it was the right model for the stage they were in. It produced trust, stability, and the credibility that made the business investable.
That model is now under strain. Customer expectations are sharper, AI is compressing reinvention cycles, and private equity investors are asking businesses to scale, integrate, recover margin, and innovate at the same time. The pressure is surfacing a different kind of execution: customer-led, where value is judged less by what is shipped internally and more by how the business adapts to constantly shifting customer demands, accelerates adoption, and coordinates delivery as a whole system.
This is not a clean replacement. PE-backed healthcare businesses still need the control and discipline that product-led execution provides. They also need the responsiveness and coordination that customer-led execution demands.
The nature of healthcare makes this shift even harder. Compliance, privacy, cyber security, and patient-safety obligations all push the operating model toward containment, local protection, and reactive crisis management. Those defaults are rational, and often necessary. But they tend to crowd out the cross-functional adaptation that customer-led execution requires, particularly at the points where strategic direction has to become operational reality.
This trade-off has become one of the defining execution tensions in the market: how a business optimises for perpetual change and customer needs without losing the coherence that built its credibility in the first place.
Chapter II
Two operating postures, two patterns of decisions, two sets of outcomes.
For senior leadership teams, the difference between product-led and customer-led execution is behavioural. Each model encourages a distinct pattern of decisions, incentives, and coordination, and those patterns shape the outcomes the business is able to produce.
Product-led execution rewards precision, control, and internal coherence. Roadmaps are protected, dependencies are managed carefully, and variability is treated as risk. Functions can remain relatively self-contained because work moves through clear handoffs. Success is measured by what has been built, released, stabilised, or shielded from disruption.
The strength of this model is quality and continuity. Its hidden cost is a tendency to optimise inward rather than outward, and a slowness in sensing what the market is actually asking for in real time.
Customer-led execution rewards responsiveness, cross-functional collaboration, and adjustment in flight. In practice, this means that critical functions can no longer operate as downstream handoffs because value is no longer created by any one of them alone. It is created by how the system responds together.
The model’s strength is the speed at which the business converts intent into delivered outcomes. Its hidden cost is exposure: it surfaces alignment, accountability, and decision-making gaps that a more contained operating model can mask for years.
The commercial implications are straightforward. A business built for product-led execution that is then asked to pursue an aggressive growth agenda, without first adapting its execution model, breaks in recognisable ways: uneven adoption of change, inconsistent customer outcomes, and a widening gap between what the client needs and what the business can deliver. It is left with an execution model that has not yet caught up with market direction.
At board level, this is not a discussion about ways of working. It is a discussion about what the operating model is currently set up to produce, and whether that still matches the value case the business is being asked to deliver.
Many businesses are running perpetual transformation through a model originally built to preserve business-as-usual. The mismatch is felt as constant motion without real progress: a sense that the business is always changing, but that change is rarely landing.
The problem is not the volume of change. It is the gap between what the operating model was built to do and what the market now asks it to metabolise.
Chapter III
Three observable patterns where the operating model is beginning to give way.
The shift from product-led to customer-led execution is already producing observable patterns across PE-backed healthcare. Three of the most pronounced are set out below.
Execution risk is increasingly concentrated in the chain between Sales, Product, Technology, and Delivery. This is the part of the business where the gap between strategic intent and operational reality is now most visible.
Sales optimises for conversion and momentum. Product protects roadmap integrity and prioritisation discipline. Technology manages complexity, resilience, and technical risk. Delivery protects continuity for customers already in the system. None of those positions is wrong in isolation. The problem begins when each function is optimising for its own local success.
In practice, this means deals are sold on one assumption, products are prioritised on another, technical teams optimise for somewhere in the middle, and Delivery absorbs the consequences downstream. What looks from the top like a single growth motion is, in fact, a series of loosely connected decisions being made against different definitions of value.
Perpetual change and uncertainty are pulling these functions further apart at precisely the moment they most need to collaborate. In a more customer-led market, value is no longer created by any one of these functions alone. It is created by how the system responds together, in real time, under pressure.
Impact. Misalignment across the growth chain rarely stays internal. It tends to bleed through to the client quickly. Clients begin navigating between functions to get what they need, managing coordination that should have been resolved internally. Over time, this pattern shows up as declining NPS scores, weakening retention, reputational strain, and pressure on market share.
Leadership layers are being pulled to optimise for different realities inside the same operating model, while driving the same strategy.
The senior leadership team is typically aligned on growth, change and the value case. It sees the business through a broad portfolio mix of risk and opportunity: growth targets, customer impact, integration progress, margin optimisation, and the pace of overall innovation.
The leadership team experiences the business through the operational burden of fragmentation. Its reality is shaped by friction driven by siloed handoffs, late escalations, and repeated replanning. As a result, it is often forced to optimise for local stability and issue containment, even when the stated priority from above is growth and change.
What this means in practice is that even a well-articulated strategy can land as optional. For the senior team, it marks the new state of the business. For the layer beneath, it arrives on top of an already full operating load. Leaders look at the direction and think, in effect: “This makes sense, but I still need to keep the business running.” Their attention is dominated by operational responsiveness, so the new strategic direction is treated as a good-to-have.
This misalignment deepens as it reaches middle managers. They witness the gap between language and actions across the business, and ambiguity hardens into uncertainty. Faced with uncertainty, they adopt a mindset that delivery must continue even when priorities have not been fully resolved above them. This pushes them toward the safest option, the behaviour that was rewarded before the change, and the organisation quietly reverts to the old ways.
Impact. Over time, this is why strategic intent fails to translate to the lower layers of the business and why C-suite intent and frontline reality diverge. At an organisational behavioural level, it reinforces local bias, promotes internal politics, and breeds disengagement.
Even a well-articulated strategy can land as optional.
Ambition for change at the board level is often not accompanied by a corresponding redesign of how accountability is distributed below it. In that gap, leaders are held accountable for outcomes without equivalent influence over the conditions that produce them.
When something goes wrong, a regular occurrence in a high-change environment, the most common response is to manage the immediate problem. Contain the impact, patch it, and move on. In a fast-paced environment, this can feel entirely rational, as speed is required. The problem is that those fixes rarely get revisited. They compound quietly over time, layered on top of each other until the same problems resurface in bigger forms. Each cycle adds a little more weight to the system.
What turns this from a short-term coping mechanism into a structural pattern is the way the system reads and rewards it. The organisation tends to recognise and value those who respond to crises, not those who step back and invest time in fixing the conditions that keep producing them. That distinction matters because it actively discourages the kind of bottom-up problem solving that creates lasting change. Where teams closest to the work could identify a structural issue and address it properly, the default instead is to show forward motion, often with no escalation at all.
Over time, this dynamic becomes self-reinforcing. Teams become skilled at firefighting. The organisation develops a quiet tolerance for reactive ways of working that would once have been recognised as a warning sign. Leaders begin to mistake it for speed of response, when what they are actually observing is an organisation that has become far better at managing crises than preventing them.
Impact. When this becomes the norm, the organisation loses its ability to distinguish between urgent and important. Strategic priorities compete with immediate operational demands, and immediacy wins almost every time. Over time, this is why transformation initiatives stall, why capable people become exhausted managing symptoms, and why the gap to the growth target quietly widens even when the business appears to be moving fast.
Chapter IV
The condition underneath the patterns, and the discipline that resolves them.
The three patterns mentioned share a common condition that allows them to persist. In each case, the organisation is making decisions without a shared logic for how competing demands between market demand, business continuity, modernisation, and integration should be resolved. This absence of shared trade-off logic reinforces all three as ongoing challenges, even for the most mature organisations.
Most PE-backed businesses enter periods of intensive growth with clear priorities. What is far less often examined is whether the logic behind those priorities has been translated into the way the organisation makes decisions day to day, at every level, under real operating pressure.
The divergence of the two is one of the most consistent and costly sources of execution failure in the market.
The most execution-mature businesses have learned that shared trade-off logic cannot live in a list of values in a shiny deck or in the outputs of a leadership offsite. It has to form the foundation of the operating fabric and be reinforced through the culture. In practice, that means working at two distinct layers simultaneously.
Trade-off logic is woven into how performance is defined, measured, and rewarded. Where growth acceleration is the primary goal and Product and Sales have historically operated at arm’s length, leading organisations are beginning to hard-code that trade-off into the system in the form of engineered interdependence. In those settings, Product is rewarded for using Sales as its market radar and delivery partner by being accountable for customer success. Where this structural expression of trade-off logic is absent, even the most well-intentioned people tend to revert to what is easiest: their own lane.
It is not enough for people to know, in theory, what the trade-offs are. Trade-off thinking is a muscle. It develops through the operating conditions the business creates, but it is strengthened in the day-to-day drills: the questions leaders ask in reviews, the way conflicts are surfaced early rather than buried, and the way people narrate the logic behind a ‘no’ as clearly as a ‘yes’. In the most execution-mature organisations, leaders and teams talk explicitly about what they are trading off when they commit to a deal, change a roadmap, or reassign capacity in the growth chain, and they do it before the decision is locked in. A Product squad, for example, may choose to pause a release that would improve general quality in order to unlock a multi-million-pound client commitment, because that is the trade-off the organisation has said matters most at this stage.
When trade-off logic is genuinely embedded at both levels, the first signal is in how people respond to taking accountability for outcomes and the processes that drive them.
Clarity on the trade-offs, and confidence in dealing with perpetually competing priorities, produce a certain ease in taking accountability for key outcomes and show up in people and teams volunteering for ownership and discretionary effort.
Chapter V
From reading execution by its outputs to reading execution by its conditions.
The measurement infrastructure most healthcare businesses rely on was not built for the execution environment they now operate in. It was built for a more stable era, one in which transformation was episodic, operating models were relatively fixed, and success could be read reliably through financial outputs, delivery milestones, and compliance reporting. That infrastructure still has value, but it was designed to confirm performance, not to surface the conditions that determine whether performance will hold.
The result is a fundamental mismatch between what leadership teams can see and what they most need to understand. Because those conditions are not captured, they are not managed, and because they are not managed, they show up in outcomes: missed revenue targets, slower adoption curves, margin pressure, and delivery failures. By the time the data confirms the problem, the execution gap it reflects has typically been accumulating for months.
What is beginning to emerge, in the most successful organisations, is a different category of data altogether. Not more reporting layered on top of existing infrastructure, but a fundamentally different layer of intelligence: one oriented towards reading the conditions that drive healthy execution, rather than execution outputs.
The new layer surfaces patterns that traditional reporting cannot: where coordination across the business is coherent and where it is beginning to fray; where frontline behaviour is consistent with strategic intent and where it is being reshaped in transit; where the organisation is successfully enacting change and where earlier habits are quietly reasserting themselves. In doing so, it finally achieves what businesses have been trying to unlock for decades: make sense of the interaction between people and operating conditions and how that interaction shapes the business.
This shift, from managing execution by its outcomes to reading execution by its conditions, represents a meaningful change in what it means to run a high-performing healthcare business.
For most leadership teams, execution conditions have sat in the category of things that are felt but not formally read. In PE-backed healthcare, where the value case depends on pace, integration, and consistent delivery through change, that is becoming an increasingly costly position to hold.
Businesses that can read their execution conditions clearly and act on what they see while there is still time to influence the outcome will have a materially different relationship with risk, with their investors, and with the growth targets they are being asked to hit. That capability is moving from a competitive advantage to a baseline requirement.
Chapter VI
Closing reflection.
The blind spot sits in the operating model. It is most evident in the gap between the conditions people are working in and the conditions the value case requires.
Closing that gap is gradual work. It means building shared trade-off logic into how decisions are made, and treating execution conditions as a category of data that is read as carefully as financial performance.
For PE-backed healthcare leaders, the outcome is a business that can keep its promises under integration, under growth, and under pressure to change.
How the organisation behaves under pressure is no longer a soft consideration. It is the value case.