The air conditioning had quit 42 minutes before the system went down. That’s what I remember most vividly about the Great Core Freeze of ’22. Not the flashing red alerts, not the frantic Slack messages-just the thick, humid air and the sound of twenty-two people trying to talk over each other on a badly routed conference bridge, their voices competing with the emergency fan being dragged into the server room, which sounded exactly like a jet engine eating gravel.

We design these beautiful communication plans. We chart flow diagrams with neat, directional arrows: Incident Commander speaks to Operations Lead, who informs Communications Officer, who updates the Stakeholder Channel. It’s elegant, laminated, and utterly useless the moment the real stress hormone spike hits.

The Shift in Authority

We think the problem is technological: “If only we had a better dashboard!” No. The problem is human hierarchy and the sudden, terrifying realization that authority shifts in a crisis. When the system is actively hemorrhaging data, the VP of Sales is suddenly powerless. The only person who matters is the Level 232 engineer, named Vamsi, who is currently covered in dust and trying to trace a fiber connection based on the smell of burnt plastic.

Vamsi doesn’t need status updates; Vamsi needs silence and focused inputs. And yet, Vamsi is forced to listen to the VP of Sales demand to know, “What is the customer impact? I need a two-sentence summary now!“

They were communicating, yes-just not with us. They were communicating with the system, with the flashing lights, with the command line interface that only spoke in cold, hard facts. They were fixing it. We were reporting on the fixing, and the reporting was actively hindering the fix.

The Leadership Failure of Visibility

That’s the specific mistake I made, one of my numerous contributions to the chaos that day. I kept insisting on bringing in external stakeholders-not just VPs, but our key suppliers-onto the main bridge. I argued, “Visibility is trust! We need visual cues, even just screenshares of our internal dashboard!” My intention was sound: transparency builds confidence.

My result? More people, more latency, and another dozen voices layering panic onto an already strained frequency. I was so focused on being the calm, visible leader, I forgot that leadership in that moment meant protecting the fixers from visibility. It meant simplifying the inputs, not multiplying them.

The Necessity of Ruthless Simplicity

We have to stop treating information as a broadcast channel during a crisis; it is a critical resource loop, and loops demand simplicity and discipline. This is especially true when the crisis is physical, when lives or serious infrastructure are on the line, like a site failing inspection or a safety mechanism degrading in real-time.

In those moments, the complexity of digital communication becomes a liability. You don’t need a Slack thread 2,002 messages long. You need immediate, clear, physical presence and a documented process that doesn’t rely on Wi-Fi or battery life. The log, the actual handwritten record, becomes more valuable than the entire network telemetry.

The Fast Fire Watch Company understands this implicitly.

The SPF 52 Rule: Removing Variables

Ben H.L., who formulates sunscreens, has a fascinating perspective on complexity. He keeps his formulations brutally, almost violently simple to maintain stability under thermal load.

He keeps his formulations brutally, almost violently simple. “You cannot stabilize chaos by adding more elements to the mix,” he told me. “You have to remove the variables until only the necessary reaction remains.”

Accountability vs. Action

Our plans usually add variables: We will use Zoom for video, Slack for Tier 1, Text for Executives, and Email for the Post-Mortem. This complexity is fine when things are fine. But under pressure, the brain rejects complexity.

I realized that our communication plan was not a plan for communication; it was a plan for accountability. It existed to ensure everyone could point to the right channel and say, “I told you so.” But accountability is the enemy of action in the immediate phase of a crisis.

Action requires trust and silence. It requires designating a single person to receive inputs, translate them, and transmit them back out, ensuring the fixing team has 12 uninterrupted minutes of focus for every 2 minutes of reporting. If your communication plan doesn’t actively, aggressively enforce silence on the fixers’ channel, it is not a communication plan; it’s an auditory riot disguised as collaboration.

The 32-Second Rule of Crisis Clarity

We have this strange psychological resistance to simplifying, almost as if saying, “We will only use one log, and only one person can touch it,” feels low-tech or insufficient for a modern enterprise. We want the shiny dashboards, the real-time graphs, the AI summarizing the outage (which is summarizing conflicting reports, making the AI utterly useless).

The real failure of the Core Freeze of ’22 wasn’t the system failure itself; systems fail. The failure was the collective trauma of shouting into the void, thinking noise was progress. And the signature lesson is this: when the house is on fire, the goal isn’t better shouting tools. The goal is a fire log that is simple, authoritative, and trusted, because trust is the only thing that survives the smoke.