The screen went from standard green-on-black terminal output to a blinding, angry crimson flash-a color that meant the perimeter wasn’t just breached, it was vaporized. Not a knock on the door, but a rocket blast through the window. It happened at 2:16 PM, precisely when the key response committee decided this was the week for synchronized family cruises.
I was sitting three rows back from the Junior Devs, who were, to their infinite credit, fighting the fire with nothing more than pure adrenaline and a rapidly flooding backchannel Slack group named “OH_Crap_506_Error.” They were running manual scripts, patching holes with digital duct tape, while the official Command Center remained sterile and silent. The air conditioning was probably the loudest thing in the room. This silence was the sound of the 36-page Incident Response Protocol failing spectacularly.
The Illusion of Control
I mean, we spent six months building that thing. Six months of meetings and flowcharts and acronyms. It was Document 1,236 in the shared drive, meticulously indexed. And when the actual, complex, novel crisis hit-the kind of crisis that doesn’t announce itself with a gentle chime-nobody could remember the login for the shared drive, let alone the required escalation path for a Tier 4 event, which involved locating the 6 key members currently enjoying the buffet in international waters.
Insight: We build boundaries around catastrophe.
I checked my wrist. Not for the time, exactly, but for the instinctual need to measure the failure. It reminds me of trying to meditate the other morning. I’d told myself: 20 minutes of stillness. But every 6 minutes, I felt this compulsion to check the clock, to quantify the experience, to put boundaries around the boundless quiet. That’s what we do in corporate planning. We build rigid, quantifiable boundaries around catastrophe, pretending that chaos follows a Gantt chart. We don’t want resilience; we want documentation. We want something we can wave at the auditors and say, “Look, we thought of this!”
Complicated vs. Complex
We hire people whose expertise lies in measurement and comparison. Take Zara W., for instance. She’s a safety compliance auditor I worked with in Denver. Zara is brilliant; she can spot a non-compliant fire exit sign or a missing training log from 46 paces away. She operates entirely in the realm of the complicated. Complicated means you have many moving parts, but if you follow the manual (Procedure 876), you get the predictable result. A flat tire is complicated. You have tools, steps, torque specifications. Zara can audit a flat tire plan.
Many parts, predictable outcome. Follow the manual.
Interdependent parts, unpredictable outcome. Requires agility.
But a crisis? That’s complex. Complex means the relationship between the parts changes moment to moment, and the outcome is unpredictable. You cannot plan for complexity, only train for agility. When I tried to explain the difference to Zara, she just shook her head and pointed to Section 16 of the fire safety binder: “If it is not written, it did not happen.” That’s the core of the illusion: believing the written plan is the reality of our preparedness.
My own confession: I built the chains.
I confess, I was one of the architects of these binders back in my younger days. I meticulously designed the communication cascade charts and the secondary failover procedures. I wanted that illusion of control. It felt good. It felt responsible. But what I was actually doing was creating competence atrophy. The minute you rely on a 36-page document to tell the expert what to do, you’ve signaled that you trust the static text over their living, breathing, tacit knowledge.
Google Maps vs. The Expert Driver
Think about the difference between Google Maps and a seasoned professional driver. Google Maps is the corporate disaster plan. It knows the shortest route (the procedural checklist), the posted speed limits, and the predicted traffic flow based on historical data. It assumes normalcy. It is complicated.
THE DIVERGENCE
Now imagine a true crisis: a blizzard hits I-76 West, zero visibility, wind sheer at 46 knots, and a sudden, unmapped closure due to a jackknifed semi. The Google Map recalculates endlessly, spitting out irrelevant data. The plan fails because the environment is now complex. What saves the passengers is not the algorithm, but the driver who knows that particular stretch of highway-the one who remembers the subtle crown of the road on the 6th mile, the unlisted gravel shoulder where you can safely pull over, and the specific micro-climates of the Divide. That driver knows that the safest route might involve a six-hour detour through local logging roads that Maps doesn’t even recognize.
This is precisely the value proposition of a service provider who deals in reliable transportation through unpredictable terrain. Companies like Mayflower Limo don’t just rely on GPS; their drivers accumulate and deploy a deep reservoir of specific, local, dynamic expertise. They sell you the ability to handle the blizzard that the generic plan missed. The plan says: ‘Proceed West.’ The expert says: ‘Wait. We take the low road now, the one nobody ever uses.’ The difference is life and death, or at least, the difference between reaching your destination and spending 16 hours frozen in a ditch.
The Accountability Trap (Data Visualization)
Liability Protection Focus
Goal: $6,786 Fine Avoidance
The real failure of our incident response protocols is that they prioritize accountability over outcome. We write the plan so that if we fail, we can show a judge or an insurance company that we followed Step 236. We are protecting ourselves from liability, potentially incurring a $6,786 fine, but sacrificing actual operational survival.
The Solution: Six Rules for Agility
I’ve tried to correct this approach in my own work-and failed six times before I got it right. My mistake was assuming I could write a ‘better’ plan. I couldn’t. The solution wasn’t a better binder; it was a smaller one, consisting of only six rules:
Secure Perimeter
Immediate Containment
Empower Expert
Give the developers the keys
Communicate Truth
Tell the truth about vulnerability
Identify Novelty
What is different?
Ignore Bureaucracy
Suspend all committees
Debrief & Rewrite
Immediately while fresh
It’s fundamentally counterintuitive. To gain control, you must relinquish the illusion of control. The very systems we build to manage risk are the ones that paralyze us when true risk arrives. We train for the choreography of the fire drill-where we know exactly when the alarm will sound and where the exits are labeled-not for the blinding smoke and melted infrastructure of the actual conflagration. We are experts at preparing for the past, which is why the future always catches us unprepared.
How do you measure expertise when the map has just been destroyed?