Five pitfalls that turn a crisis into a catastrophe
In a crisis we are under pressure, and under pressure we take shortcuts. These failure modes are not signs of an incompetent team — they are predictable features of human decision-making, and the reason crisis handling has to be supported by structure rather than by good intentions.
Exponential blindness
Evolution taught us to expect change to happen gradually and linearly. Pandemics, fires and reputational crises spread exponentially. On 23 February 2020 there were ten registered COVID-19 cases in the United Kingdom; a month later there were more than 12,000 and the first lockdown had arrived. The same arithmetic applies to a damaging social media post: ten people share it, and by the end of the day thousands or millions have seen it.
The failure: Assuming the crisis grows at a speed you can keep up with, and therefore missing the signals that should change your course.
Design around it: Prepare for the worst-case scenario, and make sure no signal is lost. Honnimar's dashboard makes the incident's own timeline visible — status changes are logged as they happen, so escalation is a decision made against a record rather than against recollection.
Focus on outcomes
We remember the fires we put out and forget the strategies that failed. The incident commander recalls the calls where pumping more water worked, not the ones where it did not. This bias compounds: every time we get away with a little more, the next decision is a little more daring. Before the Columbia disaster in 2003, NASA had got away with at least 14 earlier shuttle damage events — the threshold for what counted as acceptable crept up with each safe return.
The failure: Reaching for the solution that worked last time instead of reasoning from the situation in front of you.
Design around it: Action cards are written in advance, in calm conditions, and they present the options rather than a single habitual reflex. They are also revision-controlled, so lessons from the last event change what the next team sees.
Confirmation bias
Our brains reward information that confirms what we already believe and discount what contradicts it. In a crisis, that means the plan is assumed to be working because the people who wrote it want it to work.
The failure: Not being willing to conclude that the plan has failed and must be replaced.
Design around it: Plan for the possibility that the plan must be scrapped — and log the deviation when it happens. A documented deviation is not an admission of failure; it is the evidence that produces a better plan.
"More heads are wiser than one"
It is widely assumed that a group makes more balanced decisions than an individual. The research says otherwise: without the right support, information and challenge, a group will accept greater risk than an individual. Irving Janis described the phenomenon in 1972 as groupthink — an unshakeable belief in the group's own decisions, sustained by group pressure and self-censorship.
The failure: A tight, cohesive crisis team that cannot hear its own doubts.
Design around it: Deliberately compose the team from different dispositions, and give someone the explicit role of devil's advocate — the task of questioning and pointing out the weaknesses in other people's ideas. A person who was not involved in writing the original plan is more likely to propose a different approach when one is needed.
Going against the current
Solomon Asch's line-comparison experiments in the 1950s showed how far people will go to fit in: roughly three out of four participants gave a wrong answer at least once, simply because others in the room had given it first. Put that dynamic into a crisis team under pressure, where the wrong decision could turn a crisis into a disaster, and ask how many people would stand up to their colleagues.
The failure: Silence. The person who sees the problem says nothing.
Design around it: Asch also showed the remedy. When just one other participant was instructed to give the correct answer, more of the unwitting participants held the correct answer too. And when participants wrote their answers down privately instead of declaring them in the room, fewer conformed. Technical solutions that let the parties respond from different locations rather than gathering in one room reduce group pressure. Honnimar's mobile app and web access let responders report status and input from where they are — the harbour, the terminal, the bridge, another agency — rather than from a single table where the loudest voice sets the tone. The action log then records the input as it was given.
Four practices that follow
Plan, exercise, plan, exercise
Incidents rarely unfold the way we expect, so the plan gets adjusted mid-flight. Plan in conditions where you have time to think it through, then rehearse until the fast decisions are the right ones. It is impossible to plan for every crisis — it is entirely possible to plan and exercise a wide range of scenarios and build transferable skills.
Hold structured status meetings
Under pressure we lose our sense of time, and nobody reliably notices when the crisis is outrunning the plan. You need a system that gathers and summarises the key signals for decision-makers and raises an alert when it is time to stop and reconsider — even when nobody feels there is time. Long or frequent meetings need structure to avoid confirmation bias and groupthink: a defined process requiring decision-makers to respond to specific prompts, and pre-agreed criteria for signals that must not be ignored.
Build the team dynamic
A successful crisis team collectively holds the knowledge required, which may mean operations staff alongside external specialists. It is not enough to have one person from each discipline; they have to work towards a shared goal and communicate honestly.
Use a digital crisis management tool
With a digital tool, the crisis plan is always at hand and the response is a few clicks away — and the software and mobile app can guide people through the situation, minimising errors and making sure everyone is included.
You cannot train the biases away. You can design around them.
See how Honnimar's dashboard, action cards, checklists and mobile reporting remove the single-room dependency that produces groupthink.
Book a demo