The Failures That Were Visible All Along

What a review finds is never the mistake. It's the condition.

In more than two decades running clinical operations, I cannot recall once seeing a serious event turn out to be a single mistake.

That is not how they happen. What a review typically finds is a condition. Something that had been visible for weeks or months, sometimes quarters, that people had worked around, that everyone recognized and no one owned. The event is the moment the condition finally became unavoidable. It is not the cause.

What matters is how organizations respond to that moment. The examination that follows a serious event looks at who was on shift, what was documented, and what the sequence reveals about which step was missed. That work is necessary and it is rarely sufficient, because it studies the place where the condition surfaced rather than the condition itself. The condition is where the leadership work is.

The problem no one owns

The most common condition I have seen — and the least addressed — is a known performance or behavior problem that leadership has not confronted.

It rarely looks like a crisis. It looks like a schedule built to keep two people apart. It looks like work routed around someone. It looks like the same name appearing in incident reviews that are otherwise unrelated. Everyone on the unit knows. Nobody has said it out loud in a room where it could be acted on.

In the Anchor Leadership Framework this is Deferred Accountability, and it is the condition that does the most damage to the numbers. A unit carrying an unaddressed performance problem is short-staffed on paper by a figure that does not describe what is actually missing.

The staffing grid shows a person in the slot. What it cannot show is that the person in the slot is generating work rather than absorbing it, and that colleagues are compensating in ways no one has measured.

So the unit requests more staff. The request is reasonable and it is aimed at the wrong thing. Hiring against that number will not close the gap, because the gap is not a headcount.

Escalation that exists on paper

The second condition is a pathway that works in the policy binder and not at three in the morning.

Nearly every organization I have worked in had documented escalation processes — a protocol setting out how and when to raise an issue. Far fewer could pass the test I now use. Can a charge nurse, at 0300, name the threshold at which they call? Not the phone number, not the next name in the chain. The threshold. The point at which this stops being theirs and becomes someone else's.

When that threshold is undefined, people substitute judgment. Judgment varies enormously under pressure, and it bends to politics and relationships even in healthy environments.

Some people escalate everything and acquire a reputation for it. Some people escalate nothing and are praised for handling things. Neither pattern appears on any dashboard, and both generate Carried Load — the work a team absorbs that no system records.

That is what makes it compound. Someone raises a concern, watches nothing happen, and adjusts. They are not being difficult; they are responding accurately to how the system has behaved before. And the adjustment does not surface at shift change, in the daily manager huddle, or in the weekly staff meeting, because there is no line on any of those agendas for work that someone simply absorbed.

Load that has outrun the structure

The third condition is a leader who was given more to run without being given more to run it with.

A service line gets added. A vacancy gets absorbed temporarily. Six months later the interim assignment has outlived its stated end date, if it had one. Each decision was defensible by itself. Together they produce a leader whose calendar contains no unscheduled time, who makes consequential decisions in hallways, and whose own work happens after hours as a matter of routine.

Capable leaders absorb this for a remarkably long time, usually out of a real sense of duty to the organization. That is the trap. The more someone can carry, the longer the structure goes uncorrected before anything visibly breaks — which means the correction signal arrives late, and it arrives as harm rather than as a request for help.

Middle managers holding it together

The fourth condition sits underneath the other three. Middle managers translate everything an organization decides into what actually happens, and most are promoted for clinical competence and then left to work out the rest.

An underprepared manager does not fail loudly. They defer the difficult conversation. They leave a policy unenforced because enforcing it would require a confrontation they have no framework for. That is not a character problem. It is a development problem the organization chose not to solve.

What the record shows

Here is the part worth sitting with. All four conditions leave a trail.

Concerns about workload get submitted. Incident reviews name the same individual. Escalation logs show gaps. None of it is hidden. It is distributed across systems that nobody reads together — often because louder problems are competing for the attention of the people who could act.

When something serious happens and a review reconstructs the timeline, that trail is what it finds. Not a hidden failure. A documented one, legible the entire time to anyone willing to look across the whole picture rather than at the part they considered their lane.

That is uncomfortable, and it is also the opportunity. A condition that leaves a trail is a condition you can find before the event, if you go looking on purpose.

What leadership owns

None of this is solved with a policy. All four conditions are structural, which means they respond to structure.

Name the problem you have been scheduling around. It is consuming more of your operation than you have accounted for, and it will not resolve on its own.

Define the escalation threshold in numbers, and test it. Ask a charge nurse on nights to state it. Their answer tells you whether it exists.

Audit your scope against the support beneath it. If the scope has grown and the support has not, that is a resourcing conversation, not a test of personal endurance.

Develop the managers who carry your operation. They are the layer where policy becomes practice, or doesn't.

The failures that produce serious events are rarely surprising in hindsight. The work is making them unsurprising in advance. It is difficult and it is uncomfortable, and it is the job.

Where does your operation carry a condition everyone can see and no one owns?

I work with health system and nursing leadership teams on operational accountability and the structures that hold when leaders are stretched. To discuss a keynote, workshop, or advisory engagement, visit myrtleroy.com/booking.