Execution is a real problem in healthcare.
Most strategic initiatives that fail do so during the execution phase. But execution is an incomplete diagnosis. When we dig into why execution failed, the root causes often live somewhere upstream—in two disciplines that organizations rarely name, rarely staff, and rarely treat as deliberate work.
Those two disciplines are strategy deployment and creating leadership capacity. Both sit between the strategic plan and the work that delivers it. Both are prerequisites for execution to succeed. And in most health systems, both are absorbed silently into either planning or execution, treated as residual administrative tasks rather than distinct disciplines.
What is strategy deployment in healthcare?
Strategy deployment is the structural work that bridges the strategic plan to the people who execute it. It’s the discipline of breaking a strategy down into ownable bodies of work, mapping the interdependencies between them, aligning support functions to the operational outcomes they are meant to serve, and putting in place the leadership and change management infrastructure that will carry the work forward.
Done well, deployment sets execution up to succeed. Done poorly, it can undermine execution no matter how disciplined the execution team is.
Why strategy deployment matters more at scale
At the unit or department level, deployment is usually straightforward. Scope is small, ownership is clear, operational outcomes are well understood, and execution is most of the battle. When engaging teams across multiple departments, deployment becomes more important because coordination across functions becomes a concern.
At the enterprise level—across multiple facilities, multiple disciplines, multiple markets, and a much wider population of stakeholders—deployment becomes the dominant phase of the work. The volume of handoffs, the depth of coordination required, the number of leaders who must be aligned, and the amount of context that has to travel across the organization all grow with scale. It’s important to increase the effort allocated to deployment accordingly.
In practice, deployment efforts don’t scale.
In many health systems, organizations typically spend roughly 75% of their strategic planning effort on producing the plan, 5% on deploying it, and 20% on trying to execute. In large health systems, the allocation that produces results is closer to 10% on development, 40% on deployment, and 50% on execution.
That allocation gives deployment four times the emphasis allocated to development. It’s nearly as substantial as execution. And at enterprise scale, where deployment should be a substantial phase of the work, it gets a fraction of the time, attention, and structure that planning and execution receive.
How to improve the pace and clarity of deployment
Another critical activity is identifying the workstreams and deploying them into the hands of the people who will do the work—quickly. Downstream teams need time to digest the work, ask clarifying questions, break the streams down into activities, understand the resources and barriers they will face, get approvals, and source what they need to start. None of that happens overnight.
At enterprise scale, this digestion process happens at multiple levels of the organization simultaneously and is iterative at the beginning. The lead time required for downstream teams to be ready to work is significant, and it’s consistently underappreciated by the planning teams who set the timeline.
The result is that planning teams hold the work too long before deploying it, and the downstream teams who finally receive it don’t have the runway to start cleanly. Pace of deployment is critical and shouldn’t be underestimated.
How workstreams and dependencies should be sequenced
Also important is sequencing. Critical pathways—the dependencies between workstreams that determine which work must be ready before other work can start—must be mapped clearly. All parties have to be engaged in the dependencies that affect them, and target dates should be set against the operational dates the work is ultimately serving. Without that mapping, initiative oversight often misses the importance of the connected work until a missed dependency leads to delays and missed deadlines.
How support functions affect healthcare strategy execution
Healthcare has spent the last 20 years building extraordinary operational performance management infrastructure. Daily huddles. Throughput dashboards. Quality scorecards. Labor productivity tracking. Patient experience metrics. Operational units—nursing units, ORs, EDs, ambulatory clinics—carry real-time accountability for outcomes, with the cadence and structure to meet that accountability.
We have built almost nothing equivalent for support and administrative functions. HR, recruiting, finance, supply chain, quality, IT—each has its own internal scorecards, but those scorecards aren’t anchored to the operational outcomes the support functions are meant to serve. Support functions are assumed to be aligned rather than deliberately aligned. The asymmetry shows up in two ways that operational leaders absorb in real time.
The first is that much of the operational work depends on support functions delivering critical elements of the plan on time, and when they don’t, the operational work stalls. In the health systems we’ve worked with, missed commitments often trace back not to a failure inside the accountable operational team, but to a dependency that another function didn’t deliver. The consequence falls disproportionately on the operational areas that depend on those functions.
Why support function goals must reflect operational needs
The second problem is that support functions may set targets based on their own capacity rather than operational needs. The result is a successful program inside the function alongside a continuing operational gap outside of it.
Case study
A health system’s chief nursing officer was running a certified nursing assistant development program producing 12-15 newly certified CNAs annually. The CNO was proud of the program. It was a real workforce investment, well run and hitting its internal targets. But across four hospitals, there were roughly 60 open CNA positions, and the system was losing 25-30 CNAs a year to attrition. Even at the program’s stated targets, there was a net loss of 10-15 CNAs every year. The vacancies never closed.
The program’s goal had been set without being anchored to operational requirements. Once the disconnect was surfaced and the program was given a new deployed goal anchored to the operational gap, the design recalibrated and the output roughly tripled within the year.
The fix wasn’t more meetings. It was extending the same rigor of goal setting, accountability, and cadence to a support function that we apply as a matter of course to operational areas.
How to choose the right structure for enterprise initiatives
Selecting the right leadership and team to drive a complex strategic initiative is one of the most consequential deployment decisions an organization makes.
Enterprise-scale work requires leadership with the right authority, scope, and proximity to the geographies where the work lands. The deployment leader needs an organizational mandate that lets them demand the attention of other executives, hold them to delivery dates, and escalate cleanly when commitments slip.
The leader also has a day job. No senior leader running a full portfolio can carry an enterprise initiative on top of it without dedicated support. The team around the leader matters as much as the leader.
That team must have bandwidth, capability, and standing to do the work the leader can’t personally do.
Why change management is essential to strategy deployment
A core responsibility of that team is change management. Sprawling, complex initiatives require sustained communication about why the change matters, repeated reinforcement at every level of the organization, awareness of what is being asked of different stakeholder groups, cultivation of ownership at the receiving end, and a clear understanding of what will be impacted as the change rolls out.
The methodology for this work has existed for decades. Because time is always under pressure, formal change management is consistently the first thing to be shortchanged. It’s also one of the deployment failures with the most direct line to execution failure downstream.
What is organizational capacity for strategic execution?
The second prerequisite is the deliberate creation of leadership capacity to drive the work.
Even when deployment is done well—priorities translated into ownable work, dependencies mapped, support functions aligned, leadership and change management set up properly—execution still fails if the leaders responsible for driving the work don’t have the hours, the energy, and the protected attention to drive it.
Capacity isn’t a soft constraint. It’s the supply-and-demand math of leadership attention applied to the change portfolio, and in most healthcare organizations, the math doesn’t work.
How change saturation slows execution
Many healthcare organizations are already operating at or beyond their practical capacity for change. Leaders and employees are absorbing multiple enterprise initiatives at once, often alongside local improvement work, regulatory demands, technology implementations, and ongoing operating pressure.
As the portfolio expands, the willingness and capacity to support each additional change decline. The portfolio of change being asked of healthcare organizations has grown faster than the absorptive capacity of the people responsible for absorbing it.
Why portfolio prioritization is a capacity decision
Saturation isn’t a side effect of doing too much work. It’s a structural deployment choice. Leadership commits to more change than the organization can absorb, almost always in good faith—each initiative looks important, each has a sponsor, each has a reason. The discipline of portfolio triage—deciding what not to deploy, what to sequence later, what to deprioritize entirely—is rarely exercised with the rigor required.
The result is a change portfolio whose total demand for leadership attention dramatically exceeds the supply, and a leadership team that experiences the consequence as constant under-delivery on initiatives they had every intention of driving.
Why execution speed depends on organizational capacity
The reason capacity matters now in a way it didn’t a decade ago is velocity. The runway for the pressures bearing down on healthcare—demographic shift, Medicaid cuts in the One Big Beautiful Bill Act (OBBBA), margin compression, the next wave of payment reform—is shorter than in any prior cycle. Across our work with health system leaders, strategic imperatives are turning over faster, and decision-making windows are compressing. The organizations that come out ahead in the next decade will be the ones that move large transformations faster than their peers.
What happens when workstreams fall out of sync
Velocity is a direct function of capacity. When leadership capacity is constrained, workstreams fall out of sync with each other—one stream waits on another that has stalled, dependencies miss their windows, and the cadence of the portfolio diverges from the cadence of the market. Lack of pace is rarely caused by a single dramatic failure. It’s caused by hundreds of small delays compounding across a portfolio whose leaders ran out of hours.
How healthcare organizations can connect strategy to execution
Most healthcare strategies don’t fail because the plan was wrong. They fail because no one built the bridge between the strategy and the work. Deployment and capacity are that bridge. Name them. Staff them. Resource them.
Strategy is the easy part. The work is what comes after.