Crisis Leadership for COOs: Staying Composed When It Counts

When a crisis hits, your team does not read the incident plan first. They watch you. Your face in the first meeting, the questions you ask, whether your voice is steady or clipped, whether you name the problem or pretend it away — those signals set the emotional temperature for everyone downstream. The plan matters, but the plan is executed by frightened, tired people, and your job is to keep them functional.
This is the leadership half of crisis work, and it is different from the process half and the communications half. The operational playbook for running the response covers structure: who is on the crisis team, how decisions escalate, what the continuity plan says. The crisis communication plan covers messaging: who says what to whom, when. This guide is about the person in the chair — how you stay composed, decide with half the facts, protect the people doing the work, and last more than one adrenaline-fuelled day.
Strong crisis leadership is not heroics. It is being the steadiest, clearest person in a room full of people who want to panic, and doing that hour after hour without burning yourself or your team to the ground.
Composure is a skill, not a personality trait
The single most useful thing a COO does in a crisis is stay visibly calm. Not fake-calm, not falsely reassuring — calm in the sense of "I have seen the problem, it is serious, and I am still thinking clearly." Composure is contagious in exactly the same way panic is. A leader who walks in tight-jawed, talking fast, and interrupting spreads that state to twelve people who then spread it to sixty.
Composure is trainable. It comes from separating the two things that arrive together in a crisis: the emotional charge, and the actual decision. Weak crisis leaders act on the charge — they make a big visible move in the first ten minutes to feel like they are doing something. Strong ones let the charge pass through, spend ninety seconds getting the facts straight, and then move.
| Situation | Weak leadership response | Strong leadership response |
|---|---|---|
| First alert lands | Immediately broadcasts alarm, floods channels | Confirms the facts, then activates the team calmly |
| Facts are incomplete | Freezes waiting for certainty, or guesses wildly | Names what is known, what is not, decides on the known |
| A team member panics | Snaps at them or ignores it | Gives them one clear task to anchor them |
| Blame starts flying | Joins in or lets it run | Parks blame: "root cause later, containment now" |
| Hour six, energy fades | Pushes through on adrenaline, makes errors | Rotates people, protects sleep, slows the cadence |
Decide with incomplete information — on purpose
Crises rarely give you clean data. You will be asked to make a call worth real money or real safety with maybe half the facts you would want in a normal week. The instinct to wait for certainty is the most expensive instinct there is, because the situation keeps degrading while you wait.
The discipline is to decide at the point of "enough," not the point of "sure." Enough means: you know the containment options, you know roughly what each costs and risks, and you know which one is reversible. Favour reversible moves early — the decision you can walk back is cheap to get wrong, so make it fast and buy yourself time to learn. Save the slow, careful deliberation for the irreversible calls.
Say a fulfilment centre loses power and your systems are down. A strong COO does not wait for the utility company's restore estimate before acting. They say: "We reroute today's priority orders to the backup site now — that is reversible if power comes back. We hold the non-urgent batch. We tell customers within the hour." Three decisions, made on partial facts, each chosen because it can be undone if the picture changes. A weak COO waits for the estimate, the estimate slips, and half a day of orders is lost to indecision.
Name your assumptions out loud when you decide. "I am assuming power stays out past noon — if that is wrong, we revisit at 11." This does two things: it lets someone correct a bad assumption before it costs you, and it models that deciding under uncertainty is normal, not reckless. A useful supporting habit here is the same risk-based prioritisation you use in calmer risk work — sort actions by impact and reversibility, not by who is shouting loudest.
Protect the people, or lose the response
The response runs on people, and people in a crisis degrade fast — decision quality falls, small errors multiply, and by hour ten someone is making mistakes that create a second crisis inside the first. A COO who treats the team as an infinite resource is not being tough; they are being naive about how humans work under stress.
Protecting the team is concrete, not soft. It means rotating people through the hot seats so nobody works twenty hours straight. It means giving a visibly anxious person one specific, ownable task — "you own the customer-status page, update it every thirty minutes" — because a clear job is the fastest cure for panic. It means saying "go sleep, we have this" to your most committed person before they crash, because their guilt-driven overwork will cost you tomorrow.
It also means absorbing pressure rather than transmitting it. Pressure flows downhill by default: the board leans on the CEO, the CEO leans on you, and the natural move is to lean harder on the team. Strong crisis leaders act as a shock absorber — they take the heat from above, filter out the noise, and hand the team clean, prioritised work instead of raw anxiety. The team should feel demand, not dread. This is where everyday engagement work pays off: teams that already trust you will follow you into a hard week; teams that do not will scatter.
Set a decision cadence and hold it
The chaos of a crisis is partly real and partly a failure of rhythm. When decisions happen randomly — whenever someone pings you — everyone stays keyed up waiting for the next surprise, and you make scattered calls with no coherence. A cadence fixes this. It replaces "constant reactive scramble" with "predictable pulse."
Set a fixed rhythm early: a full crisis-team sync every hour in the acute phase, dropping to every two or four hours as things stabilise. Between syncs, people execute; they do not relitigate. Each sync runs the same short loop — what changed, what is the current top risk, what are we deciding right now, who owns each action, when do we reconvene. Fifteen minutes, not sixty. The predictability itself is calming: people know that if something is not on fire, it waits for the next sync, so they can put their heads down and work.
Here is a rough cadence a COO might run through the arc of an incident:
| Phase | Sync frequency | Leader's main job | What good looks like |
|---|---|---|---|
| Acute (hours 0–4) | Every 60 minutes | Contain, stabilise, protect people | Bleeding stopped, team calm and tasked |
| Managed (hours 4–24) | Every 2–4 hours | Sustain the response, rotate people | Predictable rhythm, no heroics needed |
| Recovery (day 2+) | Twice daily | Restore normal ops, keep morale up | Systems back, team not burnt out |
| Review (after) | Once, scheduled | Blameless post-mortem, capture lessons | Real fixes, no scapegoats |
Lead the recovery, not just the fire
The crisis is not over when the immediate threat passes, and this is where a lot of leaders quietly fail. The team is exhausted, the adrenaline drains, and if you declare victory too early you leave people flat, the real fixes unmade, and the same crisis free to return. Recovery is a leadership phase, not an admin task.
Two things carry it. First, mark the transition clearly — "the acute phase is over, we are now in recovery" — so people can exhale and shift gears. Give the team specific recognition, not generic. "You kept the status page updated every thirty minutes for nine hours and it saved us a hundred support calls" lands. "Great job everyone" does not. Second, run a blameless post-mortem, and mean the "blameless" part: fix the system, do not find a person. The moment a review turns into a search for who to punish, you guarantee that next time people hide problems instead of surfacing them. The mechanics of turning that review into durable improvement sit in the crisis recovery guide, and the pattern-library of how real leaders handled real incidents lives in these crisis leadership case studies.
Sustain yourself so you can sustain others
You cannot be the calm centre if you are running on empty. A COO who skips sleep, skips food, and stays wired on stress hormones for two days will make a bad call at exactly the wrong moment — and everyone downstream inherits it. Managing your own state is not self-indulgence during a crisis; it is a load-bearing part of the job.
The basics are unglamorous and they work: eat, drink water, and take a short break every few hours even when it feels wrong. Delegate hard so you are not the single point of failure — if the whole response routes through you, you become the bottleneck the moment you flag. Have one person you can be honest with about how it is actually going, because bottling it up degrades judgement. The broader habit set here overlaps with ordinary executive stress management; a crisis just raises the stakes on skills you should already be practising. A leader who models sustainable pace under pressure gives the team permission to do the same, and a team that paces itself outlasts one that sprints and collapses.
Key takeaways
- Your team reads your composure before they read the plan — staying visibly calm is the highest-leverage thing you do in a crisis.
- Separate the emotional charge from the decision. Let the charge pass, get the facts straight, then move.
- Decide at "enough," not "sure." Favour reversible moves early and name your assumptions out loud.
- Protect the people: rotate the hot seats, anchor anxious team members with one clear task, and absorb pressure instead of passing it down.
- Run a fixed decision cadence — predictable syncs beat a constant reactive scramble.
- Recovery is a leadership phase. Mark the transition, recognise people specifically, and keep the post-mortem blameless.
- You cannot be the calm centre if you are empty. Eat, rest, delegate, and pace yourself so you last the whole response.