Defining the Hospital Chief Operating Officer role

by Brian de F.

The role of the Chief Operating Officer (COO) varies widely between organizations. In some hospitals, it is essentially a facilities and support-services role; in others, it functions as an enterprise “chief of operations,” with pan-organizational involvement across both clinical and administrative performance. Many organizations fall somewhere between these extremes—which is perfectly workable, as long as all stakeholders share a clear, written understanding of what the COO owns, what is co-owned, and what is explicitly outside the role.

In most hospitals, the roles of the CEO, CFO, CMO, and CNO are relatively well understood and socially “settled.” The COO role, however, is often the troublemaker—not because the person is problematic, but because the role is inherently boundary-crossing. It sits in the space between domains, where the real causes of poor performance live (handoffs, flow, interfaces, trade-offs). If the organization does not explicitly define (and communicate) the COO’s scope, decision rights, and escalation pathways, the COO will either become a glorified coordinator with no leverage or will trigger predictable resistance from other executives who experience the role as an intrusion into their “territory.”

For this role to be effective, it is imperative to clearly understand the rationale for wanting the role in the first place, and also the current state of the organization. For an organization with relatively weak department heads and a need for significant pan-organizational change and improvement, there will be a need for a strong COO with a broad mandate. In a more mature organization with strong functional leaders, the COO mandate may be narrower and focused on operating cadence, integration, and performance management—without substituting for line leadership.

The COO role fails when organizations want enterprise solutions but maintain domain-based authority. You cannot hold someone accountable for cross-functional performance while allowing functional leaders to block them.

A recurring failure mode is appointing a COO to solve enterprise problems while leaving authority fragmented by “domains.” I have seen situations where there were many performance issues in the procurement process. Still, when the COO attempted to improve the related procurement processes, he was blocked by the CFO because procurement was in “her domain.” Similarly, I have seen situations where operating theatres and related services, such as diagnostics, were sub-optimal—but when the COO attempted to identify the root causes and correct them, he was blocked by the CMO and the head of surgery, as these areas were the responsibility of “medicine.” Additionally, a common problem is an overburdened ED waiting room—especially on weekend evenings. Correcting this involves engagement across ED, bed management, inpatient units, diagnostics, transport, discharge processes, and staffing models. The chronic fragmentation across “front door” and support functions—marketing, sales, patient experience, call center, reception, portering, and nursing—further obscures ownership and blurs the COO’s remit. These are only a few examples of many.

The pattern is consistent: many of a hospital’s biggest performance problems are cross-functional. This creates a strong case for a COO—but in some organizations the correct answer is not a “steady-state COO.” It is a “organizational strengthening” COO with a specific transformation mandate.

AI/cyber translation of the same pattern: most failed AI deployments and most “surprise” cyber vulnerabilities are not caused by a lack of tools—they are caused by cross-functional breakdowns: unclear ownership, inconsistent workflows, weak process discipline, and uncontrolled interfaces/integrations. The COO transformation mandate is the mechanism to fix the conditions that make AI safe and make cyber recovery fast.

Note: Some organizations have done away with the COO role altogether (or merged it into another executive role) and redistributed operational accountability across service-line leaders, the Chief Nursing Officer, a Chief Administrative Officer, and/or directly under the CEO. This is usually done to simplify decision-making, reduce overhead, or shift to a different operating model. Recent examples include

• Oregon Health & Science University (OHSU) — eliminated the COO role and reassigned responsibilities across other leaders. Becker’s Hospital Review+1
• Beebe Healthcare (Delaware) — eliminated the EVP/COO position and reassigned duties to other leaders. Delaware Online+1
• Confluence Health (Washington) — eliminated its COO role amid restructuring and financial pressure. Becker’s Hospital Review

However, in this context, the right move is not to remove the COO role, but to define it as a transformation role with explicit authority to drive cross-functional improvement and strengthen department leadership.

The “organizational strengthening” COO model

If the organization’s priority is transformation and capability building, the COO mandate should explicitly focus on:

• Operational transformation: driving pan-organizational improvements across silos (flow, throughput, reliability, cost-to-serve, experience).
• Leadership development: strengthening weak department heads through coaching, accountability, and capability building.
• Standardization: implementing standard work, a common operating cadence, and consistent systems/processes across departments.

Define success before defining the job

Before finalizing the role, leadership should answer:

• What must be fixed (patient flow, margins, quality/safety indicators, staff turnover, access delays)?
• What does “fixed” look like at 12 / 24 / 36 months?
• How will we measure the COO’s impact and benefits realization?

Authority architecture (the make-or-break element)

If the COO is accountable for enterprise outcomes, authority must be written—not assumed. At minimum, clarify:

• Decision rights: what the COO can decide alone vs. what requires CEO approval?
• Cross-functional mandate: ability to launch initiatives that span domains without requiring consensus from every function.
• Medical staff interface: define how COO authority intersects with medical staff governance for clinical operations (OR, ED, inpatient flow). Clarify COO-CMO/department chair conflict escalation.
• Performance transparency: direct access to department performance metrics and the ability to run a tiered operating cadence (daily/weekly/monthly).
• Operating model authority: authority to redesign processes across departments, restructure operations, and require corrective action.
• People authority: clear rules for performance improvement plans and (when required) leadership changes through a defined process.
• Escalation rules: prevent end-runs around the COO; if domain owners can routinely override by appealing elsewhere, the COO role will fail. The CEO must commit: operational disputes get redirected back to the COO for resolution.

Example Decision-Making Matrix

COO decides (within approved guardrails):

• Cross-department process redesign (end-to-end pathways, handoffs, bottlenecks)
• Operating cadence and performance standards (huddles, escalation, weekly reviews, standard work)
• Resource reallocation within approved budgets (staffing deployment, schedules, sessions, coverage models)
• Corrective action plans for underperformance (PIPs, turnaround plans, timelines, consequences)

Requires CEO approval (and Board where applicable):

• Capital expenditures above the defined threshold
• Executive-level hiring/termination
• Major strategic shifts that change the clinical service model, risk posture, or market commitments

The goal: minimize decisions that require broad agreement. Consensus is the enemy of cross-functional accountability.

Time-bound mission

Consider framing this as a 2–3 year transformation assignment with milestones:

• Year 1: assessment, quick wins, baseline standardization, operating cadence.
• Year 2: major cross-functional initiatives, leadership development, structural fixes.
• Year 3: sustainability, second-line capability, handoff to steady-state governance.

Reporting, governance, and communication

• Establish governance that resolves cross-functional issues quickly (e.g., an executive operations council with defined decision pathways).
• Set expectations with stakeholders in the right order: Board → department heads → medical staff leadership → all staff.
• Communicate the purpose directly: “We need a COO because our operating performance and operational leadership capability are uneven. This role exists to strengthen execution—by developing current leaders and, when necessary, changing leadership.”

The key question

What does the organization need to accomplish; and who will be responsible for accomplishing it?
Define the COO role based on what must be accomplished, build strong KPIs tied to those outcomes, and communicate the role’s responsibilities, scope of duties, and level of authority to all stakeholders—so the COO can solve enterprise problems rather than become trapped between domains.