C-Suite Leadership Strategy · The Step-Up
COO Leading Through a Crisis: How to Command, Not Just Cope
The plant is down, the recall is live, or the supply chain has snapped — and every function in the building has turned to look at you. This is not the methodical operational fix you were built for. It is command.
When an acute crisis lands — a product recall, a plant fire, a supplier collapse, a sudden stock-out across every channel — the enterprise stops asking its COO to optimise and starts asking you to take command. The reflexes that made you a superb operator, patience, consensus, the careful root-cause fix, become the wrong instincts overnight. This engagement prepares you to run the war room with decisive authority, hold the organisation together through its worst weeks, and step out of the fire larger rather than scorched.
Does this sound like you?
If several of these land, this engagement is built for you.
- A crisis has landed on your desk overnight — a recall, an outage, a supplier failure — and every function in the building is now waiting for you to say what happens in the next hour.
- You know how to run a methodical six-month improvement programme, but commanding a fast-moving emergency, where the decision cannot wait for the data to arrive, feels like an entirely different discipline.
- You keep trying to build consensus in a room that needs one fast call, and the minutes you spend seeking agreement are costing the enterprise real money and real trust.
- The chief executive and the board want hourly certainty you cannot honestly provide, and you are unsure how much to promise, how much to withhold, and exactly when to escalate.
- You are holding operations together while the fire burns, yet almost no one outside the war room can see the weight you are actually carrying.
- You suspect that how you handle these few weeks will set your standing for the next decade, one way or the other, and no operating career ever trained you for precisely this.
Why a crisis is command, not a workstream
For the operator, a COO leading through a crisis is being asked to do the opposite of everything that earned them the seat. Your whole career rewarded the patient discipline of the operating leader: diagnose the true cause, build the coalition, sequence the fix, let the improvement compound over quarters. An acute crisis obeys none of that logic. The house is on fire now, the information is a third of what you would want, and the cost of a slow, perfect decision is far higher than the cost of a fast, good-enough one. The skill is not operational excellence; it is judgement under a clock that will not stop, with an audience that will not wait.
The tempo is what breaks most operators. In a normal quarter, decision rights are distributed, debated and owned collectively; in the first days of a real emergency they collapse, correctly, onto one person, and that person is usually you. The organisation does not want a facilitator in that moment — it wants a commander who can absorb chaos, name the two things that matter, and give the plant, the call centre and the market a single clear instruction. Running a crisis like a workstream, with steering committees and consensus, does not feel cautious to the people watching. It feels like nobody is in charge.
The operator reflexes that betray you in the first 48 hours
The reflexes that make you excellent in steady state are precisely the ones that will sink you in the opening hours, and they fire automatically because they have been rewarded for twenty years. The instinct to wait for complete data leaves you silent while the market fills the vacuum with rumour. The instinct to distribute ownership leaves the war room leaderless at the exact moment it needs a single point of command. The instinct to protect people from the full severity leaves your own team under-briefed and your escalations too late. None of these are failures of character; they are strengths pointed in the wrong direction under a tempo they were never built for.
The antidote is not recklessness but a different operating stance, deliberately switched on for the duration and switched off again when the emergency passes. In command mode you decide on partial information and revise openly as it improves; you concentrate authority rather than diffuse it; you over-communicate severity upward and stabilise it downward. Knowing which reflex to suppress, and when to return to your patient operating self, is the difference between a COO who is enlarged by a crisis and one who is quietly blamed for it long after the fire is out.
- Waiting for complete data before speaking — while the vacuum fills with rumour you cannot later un-tell.
- Diffusing decision rights across a committee — when the war room needs one commander and a clear chain.
- Softening the severity to protect the team — leaving your own people and your escalations dangerously behind reality.
- Reaching for the permanent root-cause fix first — when the immediate task is to stop the bleeding, not to cure the patient.
The cost of running it slow
A crisis is unforgiving about hesitation in a way a normal operating problem never is, because the losses compound by the hour rather than the quarter. Every hour a contaminated batch stays on shelves is a widening recall and a hardening regulatory posture. Every hour a supply line stays broken is a distributor learning to route around you. Every hour the market hears nothing is an hour it assumes the worst and prices it in. The operator who treats the first day as a fact-finding exercise, sensible in any other context, discovers that the situation they were carefully diagnosing has metastasised into three situations while they gathered data.
There is a reputational compounding too, and it is personal. Boards and chief executives form their lasting picture of a COO not in the calm years but in the fortnight of maximum pressure, and that picture is remarkably durable. Handle the emergency with visible command and you are marked, for the rest of your tenure, as the person who can be trusted when it matters most. Handle it slowly, or let someone else step into the vacuum and command in your place, and no quantity of excellent steady-state operating will fully erase the memory that when the building was burning, you were still convening a meeting.
Command without recklessness — the reframe
The reframe that unlocks this is that decisive command and operational rigour are not opposites; they are the same discipline running at different speeds. The commander who earns trust in a crisis is not the one who abandons analysis for bravado — that leader makes fast confident errors and loses the room within a day. It is the one who compresses their rigour into the time available: naming the two decisions that actually matter, making them cleanly, sequencing the rest, and being visibly willing to own the outcome. Your operating depth is not the thing to discard in a crisis; it is the thing that makes your fast decisions better than a bolder rival’s.
So the work is not to become a different kind of leader but to add a mode you can enter and exit on purpose. In command mode you trade completeness for speed, consensus for a clear chain, and reassurance for honesty, holding a steady public face while telling your own war room the unvarnished truth. Done well, the enterprise experiences it as calm under fire rather than panic or paralysis, and your operating credibility is what makes the calm believable. The recall or the outage becomes, in the retelling, the moment the COO proved they could lead the whole enterprise, not merely run it.
Decisive is not the opposite of rigorous — it is rigour run at emergency speed. The COO who is enlarged by a crisis compresses a quarter of judgement into a night, owns the two calls that matter, and lets the operating depth make the fast decisions right.
Coming out larger, not scorched
The reason this problem is worth preparing for in advance is that a crisis is the single fastest route a COO has to being seen as enterprise leadership rather than functional leadership — and also the single fastest route to being quietly finished. The same fortnight that can mark you as the obvious successor to the top job can, handled without command, mark you as competent-but-not-a-leader for years. The stakes are asymmetric and they are personal, and they are decided by choices you make under more pressure and less information than you will face at any other point in your tenure.
This engagement is built to prepare you for that exact test before it arrives, or to steady you inside one that already has. Across two partner conversations, a diagnosis and a written roadmap, we locate the operator reflexes most likely to betray you, design the command stance for your specific kind of crisis and organisation, and set out how to escalate, communicate and own the outcome so that the worst weeks of your tenure become the ones that enlarge it. The aim is that when the enterprise turns to look at you, it sees a commander who has already thought about this — not an operator improvising under fire.
How it plays out
The COO who ran the recall that could have ended her
Consider the chief operating officer of a mid-sized packaged-foods company — call her S — twelve years of impeccable operating record, known across the group as the person who could wring reliability out of any plant or supply line. Then a contamination scare surfaced in a flagship product across three states, and within a day it was on regional television and in a regulator’s inbox. Her instinct, the instinct of a great operator, was to convene the quality, legal and manufacturing heads, commission a proper root-cause analysis, and come back with a considered position. For thirty-six hours she ran the biggest emergency of her career like the careful improvement programme she was brilliant at.
The diagnosis, delivered fast, was blunt. S was doing everything an outstanding operator should do and nothing an incident commander must. While she gathered data, distributors were pulling the whole brand rather than the affected batches, the market was assuming contamination far wider than the facts, and the chief executive was being asked questions he had no answers to because his COO had not yet given him a single clear line. The problem was not her competence — it was that she had never switched out of operating mode and into command, and the vacuum where command should have been was being filled by everyone’s worst assumptions.
The turn came when she stopped running a workstream and started running a war room. She took sole command of the response, named the two decisions that actually mattered — the precise recall scope and the single public line — and made them inside an hour on partial information, revising openly as testing came in. She briefed the board hourly with unvarnished severity and gave the market one calm, consistent voice. The contamination turned out to be narrow, the decisive scoping contained both the recall and the panic, and within a fortnight the story had inverted: the board no longer saw a COO who had frozen, but the leader who had commanded the group through its hardest month. She was on the succession slate within the year.
Illustrative composite — every engagement is calibrated to your specific situation.
What the two conversations cover
Session 1 · Diagnosis
- Map the specific crises your operating model is most exposed to — recall, plant loss, supply collapse, liquidity or channel shock — and where command would have to concentrate.
- Identify which of your operator reflexes are most likely to fire wrongly in the first 48 hours, and what they would cost you.
- Assess how the board and chief executive currently read you under pressure, and the gap between operator and commander in their eyes.
Session 2 · The plan
- Design your command stance — the decision rights, the single chain, the escalation and communication rhythm for your specific enterprise.
- Build the switch: how to enter command mode deliberately when a crisis hits and return to patient operating once it passes.
- Set the positioning that turns the crisis into evidence of enterprise leadership, so the worst weeks read as the making of you.
The mistakes to avoid
- Running the first day as a fact-finding exercise — sensible in any normal operating problem, fatal when losses compound by the hour and the market fills your silence.
- Diffusing decision rights across a steering committee when the moment needs one visible commander and a single chain of command.
- Softening the severity upward to avoid alarming the board, so your escalations arrive late and your credibility takes the hit when reality catches up.
- Reaching first for the permanent root-cause fix instead of stopping the bleeding — curing the patient while they hemorrhage.
- Staying in command mode long after the fire is out, exhausting the organisation and confusing decisive crisis leadership with permanent centralisation.
One offering · one outcome
- Two 60-minute one-to-one conversations with a senior Gladwin partner
- A complete diagnostic of where you stand in the market today
- A personalised repositioning roadmap you keep — your gap analysis and 90-day plan
C-Suite Leadership Strategy — Assessment and Roadmap
2 × 60-minute conversations · one booking
- Two 60-minute one-to-one conversations with a senior Gladwin partner
- A complete diagnostic of where you stand in the market today
- A personalised repositioning roadmap you keep — your gap analysis and 90-day plan
Loading available slots…
Frequently Asked Questions
It is a different discipline running at a different speed. Your operating work rewards patience, complete data and distributed ownership; an acute crisis punishes all three. Losses compound by the hour, information stays incomplete, and decision rights collapse onto one person — you. The skill is not operational excellence but judgement under a clock that will not stop, with an audience that will not wait. Your operating depth still matters enormously; it is what makes your fast decisions better than a bolder rival’s. But it has to be run in a mode most operators have never deliberately switched on.
No — and the leader who confuses the two makes fast, confident errors and loses the war room within a day. Real command is rigour compressed into the time available: naming the two decisions that actually matter, making them cleanly on partial information, and revising openly as the picture improves. It is the opposite of bravado. What you discard under fire is completeness and consensus, not analysis. The whole point of the engagement is to help you decide quickly without deciding blindly, using your operating depth as the thing that keeps the speed safe.
You tell them the truth at the severity you genuinely know it, and you separate what is confirmed from what is still being tested. Boards do not lose faith in a COO who says the picture is incomplete and here is how we are narrowing it; they lose faith in one who goes quiet or who promises certainty that later collapses. The discipline is to over-communicate severity upward, stabilise the message downward, and give one consistent line to the market. We design that escalation and communication rhythm for your specific board in the second session.
By treating command as a mode you enter and exit on purpose, not a new operating philosophy. In the emergency you pull decision rights onto a single chain because speed demands it; once the fire is out you hand them back deliberately and return to your patient, distributed operating self. The failure mode is staying in command mode too long, which exhausts the organisation and reads as a power grab. Knowing when to switch back is as much of the skill as knowing when to switch on, and the roadmap sets both triggers for you.
It is the best possible time, because a crisis is the one leadership test you cannot rehearse once it starts. Preparing in the calm means that when it lands you already know which of your reflexes will betray you, what your command stance is, and how you will escalate — so you spend the first 48 hours executing rather than discovering. Operators who prepare in advance step into command; those who improvise under fire usually default to the workstream instincts that make the situation worse. The engagement is built for exactly this pre-mortem.
Not if the fire is still burning, and often not even after. Standing in a crisis is frequently reset by the second act — the leader who was slow on day one but commanding by day three is remembered for the command. What we do inside a live situation is stop you running it as a workstream, name the two decisions that matter, and get you into command mode fast, then rebuild the board’s picture of you through how you own the outcome. A hesitant start is recoverable; a hesitant whole crisis is what you want to avoid.
Yes, and the command dynamics can be sharper. In promoter-led groups the instinct in a crisis is often for the family or chairman to seize the response directly, which can leave a capable COO sidelined at the exact moment they should be commanding — or, conversely, fully exposed if it goes wrong. Regulatory tempo in India, from food-safety authorities to sector regulators, is its own pressure. The roadmap is built around your specific ownership structure and how command should sit between you, the chief executive and the promoter under real fire.
Two 60-minute conversations with a partner, a written diagnostic of the crises your operating model is most exposed to and the reflexes most likely to betray you, and a personalised roadmap document setting out your command stance — the decision rights, the escalation and communication rhythm, and the switch between command and steady operating for your specific enterprise. One price, incl. GST, or $250 internationally. No tiers and nothing further to buy.