The crises that healthcare organizations face are rarely random. Eric Cecava’s view, developed over sixteen years of hospital and health system leadership, is that most of them are predictable — and that the organizations equipped to prevent them share a common trait: operational discipline built before the crisis arrives.
Healthcare tends to respond to crises well. The capacity to mobilize quickly, to make fast decisions under pressure, and to direct resources toward an immediate problem is something that hospitals develop out of necessity. What healthcare does less consistently is build the operational infrastructure that prevents crises from developing in the first place. The reactive capacity is strong. The preventive capacity is often underdeveloped.
Prevention Has a Process Problem, Not a Knowledge Problem
The knowledge of what good operational practice looks like in healthcare is widely available. There are evidence-based frameworks for infection control, medication safety, patient fall prevention, sepsis identification, and dozens of other high-stakes clinical processes. There is no shortage of guidance on what hospitals should be doing.
The gap is in process execution — in the consistency with which standard practices are followed, in the reliability of the systems that are supposed to catch deviations before they become harm events, and in the organizational culture that treats standard work as non-negotiable rather than as a best-effort target. Most adverse events in healthcare do not happen because nobody knew what to do. They happen because the process for doing it reliably was not in place, was not followed, or was not monitored closely enough to catch the failure in time.
Operational discipline addresses the process problem. It is the systematic commitment to defining how work should be done, training staff to do it that way, measuring whether they are doing it that way, and responding quickly when they are not. It is the opposite of the assumption that good intentions and professional training will produce consistent performance without process support.
The Data Has to Be Visible to Be Useful
Cecava’s background in business intelligence and process excellence shaped his approach to operational discipline at both Adena Health System and McLaren Port Huron. Data visibility is a precondition for operational discipline. If frontline leaders cannot see, in real time or near real time, how their unit is performing against operational standards, they cannot manage to those standards. They are managing to impressions, to what the last walk-around revealed, or to whatever gets reported in the monthly meeting that happened two weeks after the month ended.
The investment in data infrastructure is not just a technology question. It is an operational question about what information leaders need, at what level of frequency, and in what format in order to make the operational adjustments that prevent small problems from becoming large ones. The hospitals that catch patient safety issues early, that identify capacity problems before they become throughput crises, and that recognize workforce problems before they become turnover crises are the ones where the right information reaches the right people at the right time.
Process Improvement Is Not a Consulting Project
One of the patterns Cecava observed across multiple healthcare organizations is the tendency to treat process improvement as a periodic initiative rather than a continuous operational function. A quality problem surfaces, a consultant is engaged, a rapid improvement event is held, a new process is designed, and then the organization moves on to the next problem. Six months later, the new process has eroded, the old behavior has returned, and the problem is back.
Sustaining process improvement requires embedding it in operational management rather than treating it as a project to be completed. Standard work needs to be owned by frontline leaders who are accountable for adherence. Metrics need to be reviewed in daily and weekly operational huddles, not in monthly quality committee meetings. Deviations need to trigger a response in days, not in the next performance review cycle.
The Lean operational model, which Cecava applied first in manufacturing and then in healthcare, is built around this principle. The value of tools like daily management systems, standard work audits, and visual management boards is not in the tools themselves but in the operational discipline they create: the expectation that performance is monitored continuously and that problems are addressed immediately.
Executive Leadership Has to Model the Discipline
Operational discipline cannot be delegated down. It has to be modeled at the executive level. If senior leaders are rigorous about standard work in the areas they touch — if they follow the budget process the way they say it should be followed, if they respond to performance deviations with the urgency they expect from their direct reports, if they make time for operational rounding and demonstrate that they take what they find seriously — then the organization internalizes those expectations. If senior leadership treats its own processes with flexibility while holding frontline staff to standard work, the message is clear and it is destructive.
The organizations that sustain operational discipline over time are the ones where the expectation is consistent from the board level through the frontline, and where lapses in standard work are treated as organizational problems to be solved rather than individual failures to be punished. Building that culture before the crisis arrives is what makes the difference between an organization that prevents most crises and one that just responds to them well.