Running a health system with three sites is a specific operational challenge. Eric Cecava ran multi-site systems for years — first at Adena Health System with three hospitals, then at McLaren Port Huron with a hospital, a skilled nursing facility, and an integrated medical group. The problems that come with that configuration are specific, and they are worth naming clearly.
The transition from single-site to multi-site leadership is often described in terms of scale: more beds, more staff, more revenue. But the more significant change is structural. A multi-site system requires coordinating organizations that have their own cultures, their own operational rhythms, and their own relationships with the communities they serve, while simultaneously building the shared infrastructure that makes system-level performance possible. The tensions that result are predictable, and the organizations that manage them well are the ones that name them directly rather than pretending they don’t exist.
Standardization and Local Adaptation Are Both Right
The first tension in multi-site operations is between standardization and local adaptation. System-level standardization creates efficiency, enables performance comparison across sites, and simplifies the work of developing and deploying new clinical programs. But clinical sites are not interchangeable. They serve different populations, operate with different workforce compositions, and have established clinical cultures that cannot be overwritten by system mandate without significant disruption and resistance.
The organizations that navigate this tension well distinguish clearly between what must be standardized and what should be locally adapted. Clinical quality standards, patient safety protocols, infection control practices, and regulatory compliance requirements are non-negotiable — they should be standardized across all sites, fully, without exception. Operational practices, staffing models, scheduling approaches, and community engagement strategies often benefit from local flexibility within system parameters.
Where multi-site organizations get into trouble is when they either over-standardize — imposing system uniformity on things that should be locally adapted — or under-standardize — allowing local variation in areas that require system consistency. Both errors are common, and both are costly in different ways.
Quality Performance Across Sites Does Not Manage Itself
In a multi-site system, quality performance variation across sites is inevitable. Different sites have different patient populations, different physician cultures, and different baseline performance levels. The question is not whether variation exists — it does — but whether the system has the infrastructure to see it, understand it, and address it.
The infrastructure that makes cross-site quality management possible includes: shared data definitions and measurement methodologies that make performance genuinely comparable across sites; regular system-level quality review processes where site performance is visible to all sites and to system leadership; and the organizational will to address persistent underperformance at specific sites rather than averaging it away in system-level metrics.
The tendency in multi-site systems is to manage quality at the site level and report it at the system level. The problem with this approach is that system-level metrics can look acceptable even when individual site performance is seriously deficient. Multi-site quality management requires holding both levels simultaneously: understanding system performance in aggregate while maintaining accountability for each site’s performance on its own terms.
Clinical Programs Need Operational Support to Survive
One of the recurring challenges in multi-site health systems is the development and sustainability of specialized clinical programs. A health system with three sites can theoretically offer more specialized programs than any individual site could support alone — but only if the operational infrastructure to support those programs is deliberately built and maintained.
Clinical programs that exist in name without the operational support to function effectively create more problems than they solve. Physicians recruited to lead programs that don’t have adequate support staff, equipment, scheduling resources, or referral infrastructure will leave. Community members who are directed to programs that cannot actually deliver the promised care will lose trust. The reputational damage from a poorly supported clinical program can exceed the benefit of having announced it.
The discipline that multi-site systems need is the willingness to say no to new program development that cannot be supported operationally, and to invest in the operational foundations of existing programs before expanding the program portfolio further.
Facilities Expansion Is an Operational Commitment, Not a Capital Event
Multi-site systems often undertake facilities expansion — new buildings, renovations, technology upgrades — as capital projects. The capital committee approves, the project management team executes, the ribbon is cut, and the project is complete. What is underestimated is the ongoing operational commitment that a new or expanded facility represents.
New facilities require additional staff, additional maintenance, additional regulatory compliance, additional supply chain management. They change patient flow patterns across the system. They create new interfaces between sites that have to be operationally managed. A capital project that is approved without a clear plan for the ongoing operational requirements it creates can destabilize the system’s operational and financial performance even if the project itself is executed well.
Cecava’s approach at McLaren Port Huron was to treat facilities expansion decisions as operational commitments first and capital events second. The question was not only whether the organization could fund the project but whether it had the operational capacity to absorb the ongoing requirements it would create. That discipline is harder to apply than it sounds, particularly when there is community pressure for a new facility or when a competitor is expanding in the same market. But it is the right discipline for organizations that want to remain operationally stable as they grow.