Getting Ready Is Not the Same as Staying Ready

Every organization I have led or assessed has a version of the same season. The surveyors are coming. The binders come out, the policies get dated, the drills get scheduled, and for about six weeks the place performs at a level it has not performed at all year. The team passes. The binders go back on the shelf. Twenty-three months later somebody says the surveyors are coming.

That is getting ready. It is expensive, it is exhausting, and it does not protect anybody.

Staying ready is a different proposition, and it is the only one that survives contact with a real event. The survey is not the test. The survey is a sample of an ordinary Tuesday. If Tuesday is not good, the sample will not be either, and no amount of preparation in the six weeks prior changes what was true the other forty-six.

The measurement problem nobody wants to name

There is a hard number for the difference between watched and unwatched performance, and every executive should know it.

Researchers in a university hospital intensive care unit compared directly observed hand hygiene against automated electronic dispenser monitoring across 384 hours. Staff performed eight hygiene events per hour when they were not being observed. They performed twenty-one per hour while an auditor was in the room.²

A separate cohort study of more than 31,000 observed opportunities found compliance of 78 percent under overt observation and 55 percent under covert observation. The size of the gap was roughly three times larger among nurses than among physicians and nearly four times larger in outpatient clinics than in intensive care units. The authors concluded that directly observed compliance may not be an adequate performance indicator for infection control at all.⁷

I do not cite that to embarrass anybody. I cite it because it is the clearest available proof that an organization can post excellent numbers and still be unsafe, and because the same mechanism operates in every function I have ever been responsible for. Self-report is worse still. In one study, staff reported hand hygiene compliance before patient contact at 76.9 percent while observed compliance at the same moment of care was 11.7 percent.³

The gap between what an organization reports and what it does is not a character problem. It is a systems problem, and systems problems are fixable.

What staying ready actually requires

Four things, and none of them are a binder.

Written procedures that a stranger can execute. The test I apply is simple and it is not the one most organizations apply. Do not ask whether the procedure is accurate. Ask whether the person who will actually be on duty at two in the morning, who was hired last month, can follow it without calling anyone. A procedure that only works when the person who wrote it is in the building is not a procedure. It is that person’s memory, transcribed.

People who have done it, not people who have read it. Training records prove attendance. They do not prove capability. The only evidence that a plan works is that somebody executed it under conditions they did not control.

Exercises evaluated against the plan, not against the calendar. Most drills are scheduled to satisfy a requirement and are scored on whether they occurred. That is compliance theater. An exercise is worth running only if the evaluation criteria were written before it started and somebody is prepared to record that the organization did not meet them.

Findings worked to closure in practice, not on paper. A corrective action that closes in a tracking system without changing what people do on the floor has done nothing except create a document that will be embarrassing later.

The five habits that hold under pressure

The most useful framework I know for this is the work on high reliability organizations, which studied the places that operate under genuinely unforgiving conditions and rarely fail: flight decks, nuclear operations, wildland firefighting. Weick and Sutcliffe organize it as five principles, and they group them usefully into three habits of anticipation and two of containment.⁶

Anticipation is preoccupation with failure, meaning small anomalies are treated as signals rather than noise; reluctance to simplify, meaning the organization resists the tidy explanation that closes the discussion; and sensitivity to operations, meaning leadership knows what is actually happening on the floor right now rather than what the dashboard said last month.

Containment is commitment to resilience, meaning the organization is built to absorb and recover rather than merely to avoid; and deference to expertise, meaning that when something is going wrong, decisions migrate to the person who knows the most, regardless of rank.

I have sat in rooms where every one of those five was absent and the organization still had a perfect compliance record. The record was true. The readiness was not.

Where the frameworks earn their place

The Baldrige Excellence Framework is the best structural instrument I have worked with for this, and I say that as a trained examiner rather than as an enthusiast.⁵ Its value here is not the award. It is that the framework refuses to let leadership, strategy, workforce, operations, and results be assessed separately. An organization cannot claim operational excellence while its workforce category is failing, because the framework asks how the two connect and expects an answer supported by data.

That is the correct posture for readiness. The emergency plan, the staffing model, the training program, the supply chain, and the culture are one system. Auditing them one at a time is how an organization ends up with five passing scores and one real vulnerability nobody owns.

Learn from the good days too

One more finding, because it changes how I design an exercise program.

Ellis and Davidi studied soldiers running successive navigation exercises and found that performance improved significantly more when the debrief covered both failures and successes than when it covered failures alone. They also found that participants arrived with far richer mental models of their failures than of their successes, and that reviewing both closed the gap.¹

Organizations know why things break. Very few can explain why things worked, which means they cannot reproduce a good outcome deliberately. If the only time you convene a review is after something went wrong, you are teaching your people that review is punishment, and you are leaving the more valuable half of the data on the floor.

The structure of the review matters as well. A meta-analysis of sixty-one studies found that in military settings a highly structured review outperformed a loosely structured one, and that reviews aligned to the team and conducted against objective media rather than memory performed best.⁴

What I am actually selling

Not a binder, and not a passing score. A cycle.

Procedures written to be executed by whoever is on duty. Exercises designed against criteria set in advance. Observation that tells you what is true rather than what is reported. A written improvement plan with dates and owners. Findings worked closed before an external party finds them for you. And a review after every meaningful event, good or bad, so that the organization compounds what it learns instead of relearning it.

Run that cycle and the survey stops being an event. It becomes a Tuesday with visitors.