For the Chief Operating Officer

The day lens is your domain. The engagement traces every visible failure to its upstream cause.

The COO carries operational accountability for what shows up in the actual rhythm of the day -- first-case starts, turnover variance, block utilization, end-of-day overrun. Every visible failure has an upstream cause. Perioptimal engagements surface those causes in the institution's own data, with an active clinician at the table to address staffing-side drivers credibly.

The seat

Operational accountability for the rhythm of the OR

The Chief Operating Officer carries the institution's perioperative throughput. The questions on your desk -- why first cases keep starting late, why turnover times vary so much, why blocks go unused, why the end-of-day overrun keeps creeping -- have to be answered with numbers traceable to specific upstream causes that can be fixed. Generic operational frameworks often produce recommendations that don't land because they don't address the staffing-side and clinical-side drivers visible only from inside the OR.

Every visible operational failure has an upstream cause. The engagement decomposes the rhythm of the day into root drivers and traces each back to the lens where it actually originates -- often the team lens or the patient lens, surfacing as a day-lens symptom.

Perioptimal engagements give the COO a working analytics layer the institution operates after the engagement concludes -- not a report that sits on a shelf. The internal improvement team typically becomes the natural ongoing operator of the layer, equipped with the methodology to keep applying it.

What an engagement delivers to the COO seat

Specific outputs at the day lens (with upstream attribution)

The day lens is examined exhaustively. Every engagement delivers, at minimum, the following to the COO and operational leadership:

Output 01

First-case on-time start, with cause attribution

Decomposed into the actual upstream conditions producing the late starts -- pre-op staffing, anesthesia readiness, surgeon arrival patterns, room readiness, patient-related delays. Each cause traced to the lens where it originates.

Output 02

Turnover time variance and outlier root-cause

The variance is more revealing than the average. Outlier turnovers traced to specific structural drivers (case-mix mismatch, equipment availability, staffing transitions) rather than generalized "team performance" framing.

Output 03

Block utilization decomposition

Booked vs. released vs. unused, by surgeon, service, and time of day. The signal hospital systems most often want and most often cannot extract cleanly from internal reporting.

Output 04

End-of-day variance with predicted-vs-actual

Predicted finish from the case schedule against actual finish. The systematic overrun pattern (or under-run pattern) decomposed by service, room, and add-on impact.

The questions a COO actually has

Five recurring questions the engagement is designed to answer

Question 01

Where is the structural ceiling on our throughput, and how much headroom do we actually have?

Capacity headroom is one of the four institution-lens metrics. The engagement decomposes nominal capacity from operational capacity from realized capacity, and identifies which gap is the actual constraint -- often staffing methodology rather than physical room availability.

Question 02

Why does our first-case on-time rate plateau no matter what we try?

First-case starts are typically a multi-cause failure. The engagement decomposes them by upstream attribution, and most institutions discover that 60-80% of the variance comes from causes outside the OR director's direct control -- pre-op staffing, anesthesia readiness, surgeon-side patterns. Fixing the right cause moves the metric.

Question 03

Are we getting the throughput we should from the blocks we have?

Block utilization is decomposed into booked, released-and-rebooked, released-and-unfilled, and never-released-but-unused. The pattern reveals whether the constraint is on the demand side, the surgeon-allocation side, or the operational-fill side.

Question 04

Will recommendations require capital, or are they structural?

Most Perioptimal recommendations are structural -- changes to staffing methodology, block allocation, supervision models, workflow integration. Where capital investment is the right answer, it is sized against the operational gain in the engagement deliverables, not recommended speculatively.

Question 05

How does this work alongside our existing internal improvement team?

The internal team is the most important partner during and after the engagement. The analytics layer is designed to be operated by the internal team afterward. Knowledge transfer is part of the engagement scope, not an afterthought. See the comparison →

The COO sits at the day lens. Engagements decompose the rhythm of the day into upstream causes the operational team can act on -- and leave the institution with a working analytics layer that keeps decomposing them.
Frequently asked

Questions other COOs have asked at scoping

What does a Perioptimal engagement deliver to the COO specifically?

A working analytics layer the institution owns covering first-case on-time start with upstream cause attribution, turnover time variance and outlier root cause, block utilization decomposition, end-of-day variance with predicted-vs-actual, and capacity headroom against the institution's operational ceiling. All produced inside the institution's environment by an active clinician working alongside the internal improvement team.

Why retain Perioptimal instead of asking our internal Performance Improvement team to do this?

Internal teams have institutional knowledge external advisors cannot match, and they handle routine throughput measurement well. Perioptimal is engaged when politically sensitive findings need to be surfaced from outside the reporting structure, when an active clinician's authority is required to address staffing-side causes credibly, or when the existing improvement work has plateaued. See the build-vs-buy comparison →

How does engagement output integrate with our existing operational dashboards?

The engagement produces an analytics layer that lives inside the institution's environment using the institution's own data sources -- SurgiNet or equivalent OR systems, anesthesia staffing systems, block schedules, financial reporting. The internal improvement or operational team continues operating it after the engagement concludes. There is no separate vendor dashboard to maintain.

What capacity gain is realistic from an engagement?

Specific outcomes vary by institution and pre-engagement state. Engagements are scoped against the institution's own pre-engagement baseline and outcomes attested over a 24-month measurement window. Capacity headroom is one of the four institution-lens metrics reported, alongside contribution margin, growth runway, and resource investment ROI.

Will recommendations require capital investment to implement?

Most do not. The bulk of Perioptimal's recommendations involve structural changes to staffing methodology, block allocation, supervision models, and workflow integration -- not new capital. Where capital investment is the right answer, it is sized against the operational gain in the engagement deliverables.

For other roles

Continue reading

Begin a confidential conversation.

Request consultation →