The air felt thick, metallic, and heavy with the smell of burnt electrical insulation. Not smoke, exactly, but the prelude to it. Sarah-office manager, unofficial fire warden, and now, unintended protagonist-was standing in front of the silent alarm panel. It should have been screaming. It was just dark. She reached for the shelf, pulling down the three-inch spine labeled ‘Business Continuity Protocol, V4.8.’
The panel was dead. Completely unresponsive. Sarah’s hands, slick with unexpected stress, flipped the cover open. The first page she landed on listed the Emergency Response Team. The contact for Daniel, VP of Facilities, was still there, despite him having retired 38 months ago. His current role was listed as ‘Critical Incident Lead.’
Rethinking Contingency
That binder-a monument constructed from 48 hours of planning meetings, countless drafts, and an internal resource cost that we conservatively estimated at $8,778-was already a historical artifact. We spend agonizing time building these magnificent structures of contingency, these architectural marvels of documentation, yet the moment the true unexpected hits, we realize we built a stage set, not a fortress.
The great deception of modern preparedness is the belief that resilience is a function of documentation. We criticize the poor implementation of previous plans (because they were rigid), but then we respond by demanding more rigidity. We mandate V5.8, V6.8, requiring deeper appendices and complex flowcharts that no human could possibly navigate under the pressure of a genuine emergency, particularly when the systems they describe have already failed in novel ways. We double down on the details when we should be simplifying the capacity.
The Lure of Control vs. The Reality of Chaos
I deleted an email this morning, one I was halfway through drafting, full of furious, millimeter-accurate precision about someone else’s obvious incompetence. That feeling-that raw, physical need to control the narrative, to assign blame, to impose order-is why the binders exist. We crave the illusion of certainty, the comfort of knowing that *if X happens, then Y is the documented response*. But chaos doesn’t read the script. It rips out the pages and demands an improvisation act.
That urge to be absolutely right, even if it’s uselessly right, is profoundly human. We prefer the comfort of a detailed but irrelevant plan to the difficult, anxiety-inducing work of building genuinely adaptive, resilient teams. The plan is a security blanket disguised as an instruction manual.
Reference Manual
VS
Muscle Memory
The Reactive Driver: Max L.M.
This brings me back to Max L.M., my driving instructor when I was 17. Max was an absolute terror of precision. He didn’t teach defensive driving; he taught reactive driving, the kind that acknowledges the world is full of unpredictable, lethal variables. His training method was brutal and, honestly, probably highly irregular. On the 48th lesson, he grabbed the wheel while I was doing 58 mph on the highway and jerked us violently toward the shoulder. I corrected, heart hammering, ready to curse him out.
“You followed the rules,” he said, his voice completely flat. “The rule is: hold the line. But when the idiot next to you forgets the rule, the *only* rule is survival. Your training needs to assume the manuals fail.”
He explained that 98% of accident manuals teach you what to do when *you* break the rule. 2% teach you what to do when *reality* breaks the rule. He forced us to practice emergency stops and slides until responding to a skid wasn’t a documented process in our brains, but a muscle memory-a capability born from repeated, stressful failure. We criticized his methods, calling them reckless, but every single one of us built resilience by throwing away the map when the pavement disappeared.
The Plan Becomes the Obstacle
I made this mistake myself, managing a small data center relocation eight years ago. We had a magnificent, color-coded plan-238 steps, signed off by 28 managers. It covered everything except the one thing that actually happened: the backup generator transfer switch failed. Not silently, as the manual described, but with a dramatic, sparking roar. Our plan assumed generator transfer was clean; we had no procedure for a catastrophic, immediate power failure requiring physical intervention.
18
We wasted 18 precious minutes arguing about who had the authority to pull the manual cutoff lever-because the plan didn’t assign that role under “Smoke and Sparks” conditions, only under “Planned Maintenance.” The plan itself became the obstacle.
We stood there, referencing sections 4.8.1 and 4.8.2, while smoke billowed out of the electrical closet.
The Pivot: Trusting Active Expertise
We must stop treating the plan as a prophylactic measure, hoping its sheer volume wards off disaster. But it’s not an inoculation; it’s a blueprint for a disaster that was *supposed* to happen, not the one that actually showed up.
When an actual unexpected event occurs-a broken transfer switch, flooding in the basement, or an immediate need for external protective services because the building’s internal systems are compromised-you need immediate, flexible capability, not a reference document. When Sarah’s binder fails, and it always does, you need true operational coverage, which often means trusting responsive experts like
The Documentation vs. Delivery Gap
We confuse documentation for delivery. We feel productive drafting Section 8.8 on communications redundancy, but true productivity happens when we admit that Section 8.8 is probably impossible to execute when the network backbone is actively melting.
Documentation Effort (Drafting)
95%
Actual Adaptive Rehearsal
5%
The hardest, most expensive part of planning-the rehearsal, the simulation, the intentional creation of stress to expose flaws-is often the first budget item cut. We love the appearance of security (the binder sitting neatly on the shelf); we hate the work of actually being secure (the uncomfortable, stressful, simulated failure).
It’s not the plan that protects you, it’s the panic you overcome.
Instinct Over Instruction
The goal isn’t to write a perfect 1,238-page document; the goal is to make the 38 seconds after the catastrophe entirely instinctive, collaborative, and directed. Sarah didn’t need Daniel’s retired phone number. She needed the immediate, shared, organizational understanding that paperwork doesn’t stop sparks.
Capacity built through practice, not passive reading.
So, go look at your binder. Ask yourself honestly: In the moment of genuine, terrifying, unexpected failure, will this document serve as a guidepost, or merely the kindling? Because until you’ve practiced the moment the plan *fails*-not the moment the plan *works*-you haven’t built a contingency. You’ve just written a very detailed, very comforting work of fiction.
