Leading under pressure: why crises reward systems, honest information and the right to disagree

Crisis stories are usually told as stories about individuals. A calm, decisive leader takes control, rallies the team and refuses to accept failure. The story is appealing and partly true: in a crisis, people do look to a leader, and confidence matters. But it leaves out most of what actually determines the outcome. Whether a business handles a crisis well depends far more on what was in place beforehand: who has authority for what, whether the people with the right expertise are trusted to use it, and whether accurate information reaches the people deciding.

Two failure modes are especially common in small businesses. The first is dependence on one person’s judgement: a strong, persuasive owner or manager who becomes the approval point for everything, so that nobody challenges them and nothing moves without them. The second is information that bends under pressure: the problem nobody mentions because they fear the reaction, the estimate softened to avoid a difficult conversation, the shortcut taken last week that suddenly matters this week. Both stay invisible until a crisis exposes them.

This article explains how to treat crisis leadership as a system rather than a personality trait, why honest information is an operating control and not only a personal virtue, how to keep a strong leader challengeable, and how to move from emergency back to normal. It is general information. Specific incidents, such as product safety problems, injuries, data breaches or environmental incidents, may carry legal reporting obligations; know which regulators you would need to contact before you need them.

A crisis response is a system

Five properties make a crisis response work:

• a shared definition of the problem, so people are solving the same thing;
• clear authority and escalation, so decisions are made by the right people at the right level;
• fast access to reliable information;
• trusted specialists with room to solve problems within agreed limits;
• disciplined communication that separates facts, assumptions and decisions.

The leader’s behaviour switches this system on. It does not replace it. Calm communication cannot make up for poor preparation; confidence without accurate information, clear roles and practised routines creates false reassurance.

Three misreadings undermine crisis responses:

• Decisiveness means speed. Fast decisions help only when they are good enough for the consequences and can be reversed if wrong.
• Calm communication compensates for poor preparation. It does not; it only delays the moment the gaps become visible.
• A crisis is the time to sort out who decides what. By then, decision rights, escalation points and technical authority should already be understood.

Work the problem, not the emotion

A crisis produces emotion, blame, speculation and pressure from customers, staff and others. Structure helps precisely because judgement becomes less reliable under stress. A simple rhythm for each crisis meeting keeps attention on evidence and action:

1. Current state: what do we actually know right now?
2. Immediate threat: what could get worse in the next few hours or days?
3. Assumptions: what are we assuming, and how could we check?
4. Options: what could we do?
5. Decision: what are we doing?
6. Owner: who is doing it?
7. Next review: when do we meet again?

It can feel mechanical. That is the point.

Centralise priorities, decentralise expertise

The strongest crisis responses centralise priorities and decentralise expert problem-solving. The owner or senior leader sets the objective, decides what level of risk is acceptable and allocates scarce resources. The people who know the technical detail, whether that is the quality lead, the maintenance technician, the IT provider or the bookkeeper, then need freedom to solve problems within those limits.

This avoids two extremes: chaotic autonomy, where everyone does what they think best, and micromanagement, where every technical judgement waits for the owner. A useful guide for any decision:

Trust has to exist before the crisis. A business that routinely overrides its specialists in normal times should not expect them to act with confidence under pressure.

Honest information is an operating control

Owners cannot personally inspect every job, machine, account or customer. They rely on others to describe reality accurately. That reliance is what makes integrity an operating control, not just a personal value. If people hide problems to protect a deadline, soften estimates to win approval or keep quiet because they fear the reaction, every other control becomes weaker, because decisions are being made on distorted information.

Most damaging behaviour does not start as dishonesty. It starts as rationalisation: “we’ll catch up next week”, “the customer doesn’t need to know yet”, “it’s only an early estimate”, “everyone knows the risk”. Pressure builds gradually: a target becomes hard to meet, a date has been promised publicly, someone senior has staked their reputation on the plan. Small omissions feel defensible while the goal still seems achievable.

Three questions reveal whether information is likely to be honest:

1. Can people report reality without unreasonable personal cost?
2. Do incentives reward truthful reporting or favourable appearances?
3. Can significant decisions be traced to evidence, authority and reasoning?

Trust also has an economic effect. Where it is high, a business can delegate confidently and move quickly. Where it is low, it adds approvals, checks and supervision, which cost time and money. The bad news early article covers how a business teaches people when it is safe to speak up.

Keep a strong leader challengeable

A persuasive, confident leader can be a great asset, especially in difficult times. People commit more readily, work harder and believe coordinated action is possible. But strong personal influence changes how decisions are made. People may support a proposal because they trust the leader rather than because of the evidence. Silence can look like agreement while hiding fear, resignation or simple dependence. A record of past success can make challenge feel unnecessary just when conditions have changed.

The answer is not to weaken strong leadership. It is to build independent capability around it:

• Independent evidence: performance information that does not depend on the leader’s own account.
• Constructive dissent: people with the standing and safety to challenge both facts and framing.
• Decision boundaries: the leader is not automatically the approval point for everything.
• Succession and capability transfer: strong leaders make the business more capable, not more dependent.
• Review after the event: examining whether confidence, status or loyalty distorted judgement.

Four tests help an owner check their own position:

• Challenge test: can capable people disagree with me openly without penalty?
• Evidence test: can the business tell my conviction apart from verifiable results?
• Dependency test: what would fail if I were unavailable for a month?
• Succession test: am I increasing others’ capability and authority?

The key person dependence article covers reducing reliance on any one individual.

Communicate facts, assumptions and decisions separately

In a crisis, staff, customers, suppliers and sometimes regulators all want to know what is happening. Messages written in a hurry tend to blur three things that should be kept apart:

• Facts: what has been confirmed.
• Assumptions: what is believed but not yet confirmed.
• Decisions: what the business is doing, and when it will say more.

Keeping them separate protects credibility. If an assumption turns out to be wrong, the business has not misled anyone. Name one person to speak externally, keep a short log of what was said to whom and when, and promise the next update at a specific time, then keep that promise even if there is little new to report.

Preparation reduces improvisation

A prepared business needs to improvise less. If likely scenarios have been talked through, information sources are known, technical authority is clear and backup resources exist, the leader can focus on the genuinely new parts of the situation. An unprepared business spends its first precious hours discovering basic responsibilities.

Preparation for a small business can be modest: a one-page list of likely crises, who leads, who has technical authority, who speaks to customers and regulators, and which thresholds trigger each step. Walk through one scenario a year with the team.

Recovery is a different phase

Crisis leadership does not end when the immediate danger passes. Recovery needs a deliberate move from emergency mode back to normal governance:

• Decide when emergency authority ends. Staying in crisis mode too long creates fatigue and over-centralisation.
• Review temporary workarounds and remove or formalise them.
• Give deferred risks owners.
• Explain what happened to staff, customers or others who need a fuller account.
• Turn lessons into permanent changes, and lift temporary restrictions that are no longer needed.

Also distinguish a genuine emergency from ongoing uncertainty. Some work is always uncertain: new products, experiments, changing requirements. Treating it as a permanent crisis makes urgency the default culture and crowds out the participation and experimentation such work needs.

A worked example

This is an illustration. A small food manufacturer receives a customer complaint late on a Thursday: a small metal fragment found in a packaged product. The owner is energetic and well liked, and makes most decisions personally. The first instinct, voiced loudly, is that “it can’t be from our line”.

The owner stops and runs the meeting differently. Current state: one complaint, one fragment, one batch code. Immediate threat: consumer injury and other affected product. Assumptions: the source is unknown. Options: wait for more information, hold stock, trace distribution, contact the food authority. Decision: hold all stock from that production day and trace where it went. Owner of technical investigation: the quality lead, with the maintenance technician. Owner of customer and regulator contact: the owner. Next review: 7 pm.

The owner also asks a question the team had never heard: “What do we know that we’d rather not say? Nobody will be penalised for anything shared tonight.” After a pause, the production supervisor says the metal detector had been bypassed for part of two shifts earlier in the week during a rush, and the bypass was not logged.

That one piece of honest information changes everything. The investigation now has a likely window. The quality lead traces the bypass period to two days of production, and with the state food authority’s guidance, the business recalls those batches rather than a full week’s output. The fragment is traced to a worn guard on a mixer.

Recovery is handled deliberately. Emergency arrangements end the following Monday. Bypassing the metal detector now requires two people and is logged automatically. The team walks through a recall scenario twice a year. And the owner, reflecting on how close the supervisor came to staying silent, changes how production pressure is discussed: deadlines can be missed with notice, but checks cannot be skipped without a decision from the owner.

How this applies to a small Australian business

• Write a one-page crisis sheet: likely crises, who leads, who has technical authority, who communicates, and when to escalate.
• Know your regulators: which authorities you would need to notify for product, safety, privacy or environmental incidents, and how.
• Use a simple meeting rhythm in any crisis.
• Let specialists solve technical problems within clear limits.
• Make it safe to share bad news, especially in the first hours.
• Check whether you are challengeable, and build others’ authority and capability.
• Rehearse one scenario a year.
• End emergency mode deliberately and turn lessons into permanent changes.

Signals worth watching

• Every decision waiting for one person.
• Silence in meetings when the owner has stated a view.
• Problems discovered by customers before staff mention them.
• Controls bypassed under time pressure without record.
• Crisis-mode working that never ends.
• Lessons discussed after incidents but never acted on.

Common mistakes

• Treating crisis leadership as personal heroics.
• Inventing roles and authority during the crisis.
• Centralising technical judgements that specialists should make.
• Punishing the messenger, then wondering why bad news arrives late.
• Confusing enthusiasm for evidence.
• Staying in emergency mode after the danger has passed.

Frequently asked questions

Is directive leadership bad? No. In a genuine emergency, more direction is often appropriate. The point is to direct priorities and boundaries while leaving technical problem-solving with the people who know most.

How do we make it safe to share bad news? Respond to it well, every time. Thank people for early warnings, focus on the problem rather than blame, and show that information changes decisions.

What if the owner is the main source of challenge-free decisions? Start small: invite one trusted person to play devil’s advocate on major decisions, and ask “what would make this wrong?” before deciding.

How detailed should a crisis plan be? For most small businesses, one page per likely scenario is enough. What matters is clarity on roles, contacts and thresholds.

When does a crisis end? When someone decides it has, explicitly. Name the date emergency arrangements stop and what normal governance resumes.

Questions to ask

• Who leads in each likely crisis, and who has technical authority?
• Which regulators would we need to contact, and how?
• What would we need to know in the first hour, and who would know it?
• Can people tell us bad news without fear?
• Which decisions depend entirely on one person?
• How will we know the crisis is over?

Bringing it together

Good crisis responses come from systems, not heroes: a shared definition of the problem, clear authority, fast and reliable information, trusted specialists and disciplined communication. Honest information is the foundation, and it depends on whether people can report reality without fear and whether incentives reward truth over appearances. Strong leaders remain valuable when they stay challengeable and build others’ capability rather than dependence. Prepare modestly, decide with a steady rhythm, let expertise solve technical problems, and end the emergency deliberately, turning what you learned into lasting change.

---

Source: KEVOS notes, drawing on project leadership teaching material on crisis leadership, charismatic leadership, ethics and trust, including the Apollo 13 mission as an illustration of crisis problem-solving. Examples in this article are illustrations. This article is general information, not legal advice.