Operating practices that sustain results.
Durable enterprise transformation in a health system depends on decisions about how the organization operates: who owns each outcome, how implementation risk will be priced, and how the program ties to margin, workforce strategy, and service-line performance. Make those decisions before funding the initiatives. They give operators a basis for choosing which projects to pursue, resolving conflicts during implementation, and maintaining improvements after the launch team moves on.
Launching a transformation and sustaining it place different demands on health system leaders. A steering committee can approve a program before a unit manager has the capacity to run it. Boards may expect quarterly evidence while workflow and staffing changes take much longer to produce results. When vendors, internal champions, and consultants are accountable mainly for launch milestones, the executive sponsor must assign responsibility for what happens during the following year.
An operating practice is vulnerable when the budget, staffing model, and decision rights still support the previous way of working. Local teams then have to reconcile the new requirement with the conditions of a shift. Their workarounds can become routine before the enterprise metrics reveal a problem.
“An operating practice is vulnerable when the budget, staffing model, and decision rights still support the previous way of working.”
Decision rights, management cadence, and accountability across entities give a transformation continuity. Without them, leaders can defer the program when volumes change or a new CFO resets priorities, because no standing responsibility requires them to maintain it.
Make the operating model specific: who owns throughput, who owns workforce productivity, who sets the enterprise standard, and who may authorize local variation. Ask each team to describe those decisions and escalation paths on one page. Resolve unclear responsibilities or escalation routes before approving the initiative.
Tie individual projects to continuing responsibilities for margin and workforce performance. A staffing initiative may end when it reaches its target or its funding closes, while the operator still has to manage labor costs and clinical capacity. That connection gives leaders a reason to maintain the new practice through the next budget cycle. It also makes the trade-offs explicit. What does a common standard mean across four hospitals with different payer mixes? Where does local variation protect clinical capacity, and where does it erode consistency? Which roles are being redesigned, and which are being refilled under a new title?
The management cadence should resolve routine barriers without relying on repeated executive intervention. A monthly steering committee may leave operating teams waiting too long for decisions. Consider a weekly value council lasting 30 to 45 minutes, organized around three questions: Which decisions are needed? What is blocking implementation? What will be completed next week? Circulate status updates beforehand so the meeting can address issues that require action.
Consider a centralization effort involving supply chain, scheduling templates, revenue cycle work queues, or IT intake. Leadership declares a new standard and early metrics improve. As local teams encounter situations the design did not anticipate, exceptions accumulate and temporary workarounds appear. If those exceptions remain unresolved, the organization can end up with two processes: the approved standard and the one people use to complete a shift.
Before diagnosing change fatigue, examine how exceptions are handled. Staff may lack a defined approver, a service-level agreement, or a threshold for escalating recurring exceptions with their volume and cost attached. In those conditions, workarounds provide a practical response to an unresolved design problem. Governance should distinguish a justified local variation from a recurring defect that requires a change to the enterprise standard.
Implementation risk also needs an owner. A capital proposal can present an attractive return on investment while omitting workflow redesign, training time, reduced productivity during the transition, and managers' capacity to operate the new process. Require each proposal to estimate those costs, including hours per role and the expected productivity ramp. Finance and the operating leader can then assess whether the projected return still justifies the investment.
Funding does not establish that a project has changed how people work. Value tracking needs an operating owner who can act on a missed result and a finance partner who can validate the calculation. Make those responsibilities explicit when the initiative is approved, so a disappointing result leads to a decision about the process rather than a dispute over who owns the report.
“Funding does not establish that a project has changed how people work.”
For a length-of-stay initiative, accountability belongs with the leader who can coordinate throughput and care progression. A project management office can track milestones and organize dependencies, but the operating leader must authorize changes to practice. For contract labor, accountability should sit with the leader responsible for scheduling and unit-level staffing. Finance validates the baseline, costs, and savings; operations is responsible for the actions intended to produce them.
Metric design needs two distinctions. The first is leading versus lagging: use of a standardized scheduling template shows whether behavior is changing, while labor cost per adjusted discharge shows the financial result, which may take longer to emerge. Neither measure replaces the other, and changes in volume or case mix can affect the financial result. The second is realized versus modeled value. Keep the business-case forecast separate from actual results so a dashboard cannot present an expected benefit as an achieved one.
Peer benchmarks can inform the forecast, but their relevance depends on local conditions. Market mix, physician relationships, payer dynamics, and legacy platforms affect what a health system can implement and at what cost. Use a benchmark to test an assumption, then identify the operating differences that could make the same result harder or easier to achieve locally.
A technology component introduces another dependency: clinicians and operators must be able to use the tool within their normal workflow. Positive pilot feedback does not establish that a system can deploy it across sites, maintain use, and achieve the intended outcome after the original champions move on.
Suppose a decision-support or AI workflow tool receives positive pilot feedback, but use falls after rollout because it adds time or documentation. The program may still be reported as active even though the expected behavior change has stalled. That pattern calls for a review of workflow fit, tool performance, and the authority to respond.
“Falling use alone does not show that the model is sound or that workflow is the only cause.”
Before rollout, specify which roles are expected to use the tool, what appropriate use means, and what an operational leader can do when adoption declines. Include a route for reporting usability and safety concerns. Budget for changes to templates, order sets, and escalation paths as well as training; instruction alone cannot remove an unnecessary step from the workflow.
A focused readiness review can examine workflow fit, data integrity, and decision rights before deployment. A two-to-three-week review may be a useful starting scope for a bounded rollout, with additional time where complexity requires it. Use the findings to assign owners to unresolved dependencies and decide which issues must be addressed before rollout.
Governance is easier to use when each initiative connects to a defined enterprise outcome and a clear escalation path. Adding committees does not resolve competing priorities. Leaders still have to decide which initiatives deserve capacity and which should wait.
One workable structure combines a monthly executive sponsor group at the CEO, CFO, and COO level with the weekly operator-led value council. Initiative workstreams use a common intake process that tests strategic fit, operating capacity, expected value, and dependencies. Record decisions to defer or decline work as well as approvals; otherwise, the intake process adds reporting without controlling demand.
Published frameworks offer useful points of comparison. HIMSS's Digital Health Indicator includes governance and workforce among its four dimensions. IHI's Going Lean in Healthcare connects improvement to leadership commitment and staff participation in process redesign. John Toussaint and Roger Gerard's On the Mend describes ThedaCare's experience with Lean transformation. These sources support examining how leadership and daily operations connect; they do not prescribe the particular meeting structure proposed here.
Board reporting should distinguish the performance of the base business from transformation spending and benefits, while reconciling both to the overall financial result. This helps directors see whether a shortfall reflects existing operations, investment during implementation, or benefits arriving later than expected. Do not assume the base business is stable. Explain the actual performance, the remaining investment, and the milestones that would justify continuing or changing the program.
Before approving the next initiative, confirm who can make the required decisions, how exceptions will be resolved, and whether managers have the capacity to run the new process. Those commitments give the executive team a practical basis for judging readiness and following up after launch.
Connex convenes senior healthcare operators in confidential forums to compare implementation decisions, operating constraints, and results. That exchange can help leaders assess whether a practice used elsewhere is feasible in their own system.