ATTENTION, PEOPLE WHO HAVE STARTED A CRISIS UPDATE WITH “JUST A QUICK FYI”!
PEOPLE WHO HAVE WRITTEN “FLAGGING THIS” WHILE THE FLAG IS ACTIVELY ON FIRE! PEOPLE WHO BELIEVE A ROW OF RED-ALERT EMOJIS IS A CHAIN OF COMMAND!
Are you tired of not having a calm evening interrupted by four words and a link?
Has somebody ever sent “there may be an issue,” then vanished into the mist — leaving a roomful of people to interpret may, issue, and the thrilling question of who gets to decide what happens next?
Then congratulations.
For the next several minutes you are eligible to receive the Five Number One Rules of Leading When the Message Is the Emergency, a complete crisis-brief, escalation and handoff system containing not one, not two, but FIVE NUMBER ONE RULES.
“Wait,” you’re yelling at the incident channel, “they can’t all be Number One!”
That’s exactly what Big Numbering wants, while it sells “communicate clearly” as though clear words could replace a decision owner — or “be decisive” as though decisive people could replace an escalation path.
Crisis failures are specialists.
Facts create shared reality. They don’t assign authority.
Ownership doesn’t say when to bring in more people.
A severity threshold triggers escalation, but can’t tell anybody what judgment to use once they arrive.
Intent permits judgment — and evaporates at shift change if the handoff was never practised.
So here they are.
Five rules.
Five Number Ones.
No substitutions. No “just keeping everyone in the loop.” No passing a live decision around the room like a cursed office birthday card.
RULE #1: SAY WHAT HAPPENED BEFORE EXPLAINING HOW YOU FEEL
Introducing VIBE-TO-VERDICT™, the emergency messaging appliance that converts “I’m concerned this could be bad” into information another human being can act on before their coffee achieves legal consciousness.
The opening brief starts with status.
What happened. What’s known. What isn’t known yet. What decision is in play. Who owns it. When the next decision or update happens.
The point isn’t to sound detached. It’s to give every recipient the same operating picture before interpretations start multiplying — because they multiply fast, and they never converge on their own.
“We have a situation” is not status.
“Customer access is impaired; cause still under investigation; decision owner is named; next update when that owner reaches the next decision point” is an operating path.
One separates observation from forecast and decision from emotion. The other is a mood with a distribution list.
Johnson & Johnson’s 1982 response carries the hard version of this. In September, seven Chicago-area deaths were traced to Tylenol capsules laced with cyanide after they left the factory.
The relevant status was not that the company felt terrible, though it certainly did. The relevant status was the traced cause, and the decision was whether to act nationally before any legal requirement forced it.
The company recalled roughly 31 million bottles inside about a week, halted production and advertising, and offered exchanges — with no obligation to recall a product contaminated downstream.
James Burke had a decision reference already sitting there: a one-page credo, written in 1943, placing responsibility to the people using the products ahead of shareholders.
Fact. Decision. Owner. Next move. In that order, at speed.
“Just a quick FYI” announces an audience and withholds what the audience needs. It’s a fire alarm with a tasteful note reading perhaps investigate heat?
A crisis brief earns attention by naming reality, responsibility, and the next moment that matters.
Feelings belong in the room. They don’t get to chair the first update.
RULE #1: NAME THE DECISION OWNER AND THE NEXT DECISION
NOW AVAILABLE: EVERYBODY-OWNS-IT™ — the leadership solution in which every stakeholder receives the message, nobody owns the call, and the emergency is politely asked to wait for alignment.
Name one decision owner.
Name the decision that owner has to make.
Name the next decision or update point.
Recipients can be informed, consulted, or assigned work. None of those silently converts anybody into the person accountable for deciding.
A crisis does not become more democratic because the distribution list got longer. It becomes slower.
The useful term is DRI — Directly Responsible Individual. One named person, accountable for a decision.
The logic is sharpest in async work, where a message only functions if readers can identify exactly who’s expected to act, rather than broadcasting to a group and hoping a volunteer materialises.
In a crisis, that stops being a nicety.
A stakeholder list tells people who’s watching. A DRI tells them where the decision lives.
The owner makes the named decision under the stated mandate. Experts feed it. Operators execute it. Stakeholders receive its consequences.
That’s a division of work. It isn’t an insult to anybody’s expertise, though it will occasionally be received as one.
And the same rule governs what happens when authority changes hands — a successor needs the decision, the mandate, the context, and the boundaries. Promotion into a crisis role requires a different skill set, not simply more of the previous one.
A copied stakeholder is informed. A named owner is accountable. Do not invoice one role for the work of the other.
If nobody can say who decides next, the message hasn’t reached leadership. It’s reached a group project.
RULE #1: STATE THE ESCALATION THRESHOLD
BEHOLD SEVERITY-O-MATIC DELUXE™ — a tiered assortment, an enormous red button, and no more standing in a digital hallway wondering whether this is “worth bothering someone” while the answer develops its own weather system.
State the condition that causes escalation, and the response it triggers.
A threshold rule removes one very specific delay: the delay caused by treating the decision to ask for help as a separate crisis requiring its own consensus.
PagerDuty documents severity tiers, each with written qualifying conditions and a mandated response. A SEV-1 pages an incident commander and notifies stakeholders. A SEV-5 becomes a routine ticket.
And for ambiguous cases the documented rule is to default upward rather than pause to deliberate — which is the part worth stealing even if you never adopt the tiers.
Google’s SRE guidance takes a different route to the same place: escalate when an incident involves multiple teams, or when responders cannot estimate an upper bound on how long it will run.
That second condition is quietly excellent. “I don’t know when this ends” is a measurable state, and it’s a better trigger than anybody’s sense of how embarrassing the call would be.
Which structure fits depends on the organisation. A customer-facing company may need named severities because the tier itself is part of what customers and executives get told. A flatter expert pool may need a judgment rule instead.
The test is the same either way: is the condition, and the response, clear before the incident?
An escalation threshold is not a label for the emergency. It is permission to stop carrying it alone.
The threshold is the moment a team stops debating whether to pull the alarm, and pulls it.
RULE #1: GIVE THE TEAM INTENT, NOT JUST TASKS
From the makers of “FOLLOW THESE STEPS EXACTLY” comes the exciting sequel: “THE WORLD CHANGED DURING THE INSTRUCTIONS.”
Watch a beautiful, detailed plan become a historical document in real time.
Tasks tell somebody what to do under the assumptions that existed when the task was written.
Intent tells them what outcome must be protected, which priority governs a tradeoff, and what boundary must not be crossed.
Tasks start movement. Intent keeps it coherent once conditions move — and in a crisis, conditions always move.
Mission command trains people to execute against stated intent rather than a fully detailed order. The clearest large-scale development of it ran through the German Reichswehr officer corps between 1919 and 1935.
Note the dates. Sixteen years of training subordinate judgment.
The mechanism was never a superior sentence that makes decentralised execution appear like a rabbit from a helmet. It was the training underneath.
So state the outcome and the boundaries. Protect people. Preserve the ability to serve affected users. Make no irreversible external commitment without the named owner.
Inside those boundaries, whoever is closest to the work uses judgment.
Intent without boundaries becomes a group art project. Tasks without intent become brittle obedience. Both fail, in opposite directions, at roughly the same speed.
Johnson & Johnson had that priority order sitting in a document from 1943, and the cost of using it was real. Tylenol’s market share fell from roughly 35% before the poisonings to about 8% immediately after, and the crisis cost more than $100 million.
A crisis-time cost-benefit calculation might well have delayed the call. The pre-committed rule didn’t have to run one.
Within ten weeks the company introduced tamper-evident packaging; within about a year, sales had recovered.
That story doesn’t prove doctrine alone caused the outcome — case studies never do. It shows what a decision rule looks like when delay carries a price.
Intent is the part of the order that survives contact with changed conditions.
Don’t give people a script for the weather. Give them the reason they’re carrying the umbrella.
RULE #1: PRACTISE THE HANDOFF BEFORE THE INCIDENT
THIS IS THE ONE THEY TRIED TO SHIP WITHOUT TRAINING.
Presenting HANDOFF-BY-OSMOSIS™: say “you’ve got the context, right?” at the end of a shift, then trust the ambient office air to transfer status, action lists, contingencies and authority.
A usable handoff has four parts, and dropping any one of them breaks it.
A written record, carrying stable context across time.
A verbal exchange, letting the receiver question what’s uncertain.
Training, so the structure is available under stress rather than only in calm.
And synthesis by the receiver — saying it back — which is how you learn whether an operating picture actually arrived.
I-PASS is the named example, and its evidence is worth quoting carefully. A 2014 study had resident physicians use a structured handoff covering illness severity, patient summary, action list, situation awareness and contingencies, and receiver synthesis — paired with a written document, training, and observation across nine hospitals and more than 10,000 admissions.
Afterwards: a 23% relative reduction in medical errors, and a 30% relative reduction in preventable adverse events.
Now the casing those numbers need. That study measured a bundle, in resident-to-resident paediatric handoffs, at academic teaching hospitals. It didn’t measure communication quality directly. And it certainly didn’t show that a crisis script recited once, without training or documentation, produces anything similar somewhere else.
SBAR makes the complementary point. Its four fields appear in major patient-safety curricula and are recommended for handovers — yet outcome evidence for SBAR in isolation is mixed. The benefits show up most reliably when it’s bundled with structured rounding, escalation protocols, and dedicated training.
Which is the whole lesson, twice.
An acronym is a shape. A practised handoff is a system.
A handoff is complete when the next actor can act, not when the previous actor has stopped talking.
If the handoff lives only inside one person’s head, its disaster-recovery plan is hope.
BUT WAIT, THERE’S MORE!
“What if the emergency is technical, operational, reputational, or a physical safety incident?”
Same rules. State what happened. Name the decision and its owner. State the escalation condition. Give intent and boundaries. Hand off in a form the next person can use.
“What if the incident leader has to leave?”
Same rules. The successor receives current status, the open decision, the authority, the action list, contingencies, and the next update point. Authority does not transfer by telepathy or by the mysterious power of a status emoji.
“What if the severity is genuinely unclear?”
Same rules — and use the written rule you wrote earlier. Default upward, or escalate when multiple teams are needed and nobody can bound the duration.
“What if we already have a template?”
Same rules. A template earns its place only when it produces a factual brief, an owner, an escalation path, intent, and a practised receiving handoff. A beautiful template nobody can execute is stationery with an incident number.
The details change.
The architecture doesn’t.
THE FIVE, WITHOUT THE PANIC MUSIC
Say what happened before explaining how it feels: status, knowns, unknowns, the decision, the owner, the next update.
Name the decision owner and the next decision. Keep informed stakeholders distinct from the person accountable.
State the escalation threshold and its mandated response — and default upward when it’s ambiguous.
Give intent, priority and boundaries. Not just a brittle list of tasks.
Practise the handoff, with written context, verbal structure, training, and synthesis by the receiver.
ACT NOW, BEFORE THE MESSAGE HAS TO SAVE YOU
Tonight, open the crisis template — or the quiet drawer where procedures go to become folklore.
Write a short brief. Current status. Known and unknown. The decision in play. The named owner. The next update.
Don’t make it eloquent. Make it runnable.
Then write the escalation rule beside it. If you use severity tiers, write the qualifying condition and the mandated response for each. If you escalate on judgment, write the conditions: multiple teams involved, or no estimate of an upper bound on duration.
“Escalate when appropriate” is an optimistic weather report. Delete it.
Name the DRI for the next live decision, and list separately who is merely informed, consulted, or assigned work.
Then write the intent. The outcome to protect. The priority that governs tradeoffs. The boundary nobody crosses without the owner.
That’s what turns a person leaving the room into a handoff rather than a gap.
Finally — and this is the step everybody skips — run it with another person. Give the brief. Have them say back the status, the owner, the action list, the contingency, and who to contact next.
You will find out immediately whether any of it transferred. Better tonight than at 2 a.m.
For the low, low price of naming the next decision before it becomes an existential group chat, the complete Five Number One system is yours.
No fog machine. No executive catchphrase. No heroic montage where one person knows everything and everybody else waits for the cape.
And if you act now, we’ll include the one item no emergency can manufacture after the fact:
a clear handoff.
Operators are no longer standing by.
The operator is the person named to decide next.