Skip to content

Leading Through Crisis

A crisis rarely arrives as a single event. It arrives as a stretch of weeks or months in which the usual work continues while something serious runs alongside it. This guide sets out how to lead through that stretch: what to say and to whom, how to keep culture from slipping, how to protect people from the pressure of an emergency, and how to keep yourself capable of leading at all.

What a crisis asks of a leader

In unsettled periods, colleagues watch how the person in charge behaves for signals the official updates leave out. They are trying to work out whether the situation is under control and how much alarm is warranted. Treating that attention as part of the job, rather than something to manage for appearance, keeps your conduct aligned with what you actually know.

A useful starting point is to separate the crisis into two questions. First, how bad is it, and what is the realistic range of outcomes? Second, who needs to know what, and when? Answering the first honestly keeps your communication grounded. Answering the second deliberately stops information from leaking out unevenly and being replaced by rumour.

Some leaders find that time pressure sharpens them; others find it draining. Neither response is a virtue in itself. What matters is knowing your own pattern so you can compensate for it. If pressure makes you fast but impatient, build in a second opinion. If pressure makes you slow and cautious, set a decision deadline. Do not manufacture crises to get the best out of yourself or anyone else.

A three-phase decision checklist:

  • First 24 hours: who owns the response, what is the honest severity assessment, and what is the first internal message?
  • First week: what does the team need to keep doing normally, what is paused, and when is the next update due?
  • Recovery: what changes so a repeat is less severe, and who is credited for getting through it?

Internal communication: early, detailed and honest

Inside the business, the case for saying more rather than less is strong. If people sense that something significant is happening and have not been told, they will fill the gap themselves, and the version they construct is usually worse than the reality.

A workable internal rhythm looks like this:

  • Say what is known, what is not known, and when the next update will come.
  • Name the people who are working on the problem, so the rest of the team knows the response has an owner.
  • Be explicit that you understand the concern, including the concern about jobs, without pretending the concern does not exist.
  • Keep the update short enough to be read and specific enough to be useful.

There is a limit to inclusion. Involving everyone in solving the problem can stall the rest of the business. The better pattern is to keep most people doing their normal work well, and give a smaller group the focused task of fixing the issue. That division is itself a message: the business is still running, and the problem has dedicated attention.

Honesty is the foundation of trust here. Concealing something material and having it emerge later does more damage than the original difficulty.

Customer communication follows a different rule

Customers need honesty too, but the timing and the level of detail are different. The aim is to show that you can contain the problem, minimise its effect and restore normal service, without causing alarm that outruns the facts. A field map for the two audiences: While the issue is live, tell customers what affects them, what you are doing about it and what they need to do, if anything. Avoid speculative detail about internal causes. Once a fix is in place, you can be much more open about what happened, what you learned and what changes are coming. Retrospective openness builds confidence; premature openness can spread it. Consider a hypothetical dependency failure: a key data source or supplier stops delivering and the product degrades. The customer-facing message is about impact and remedy, not about the internal scramble. Internally, the same event is a full and frank conversation about cause, contingency and what happens if it recurs. The two messages are consistent in substance but differ in scope, and that difference is deliberate rather than evasive. If you want to publish a real incident as an example, use your own documented case.

Culture is tested when it is inconvenient

Culture is easy to maintain when results are good. The real test is whether the same treatment of people survives a bad quarter, a technical failure or a wider emergency. A short culture check for a crisis period: Are training and coaching still happening, or were they the first things cut? Are individuals still being treated as individuals, with their circumstances known and respected? Are the commitments you make to customers and suppliers still being honoured? Would a team member say the organisation behaved in line with what it says about itself? If the answer to these is no, the crisis has not just interrupted the culture; it has revealed what the culture actually was. That is uncomfortable but useful information. The response is to restore the practices, not to rewrite the values statement. Where a crisis directly affects colleagues, the response has to be concrete: safety, practical help and clear information to customers about continuity. Describe only the support your own organisation actually provided.

The human cost of a fast fix

When a problem is technical, the pull towards an immediate fix is strong. The risk is that the fix is achieved by asking people to work longer, skip breaks and drop everything else, and that the human damage is invisible in the incident report.

The consequences are predictable. People lose confidence in the leader, trust in the business falls, and the organisation is seen to have acted against the values it promotes. A team member's reasonable question is: you did not look after me when it mattered, so why should I rely on you now?

A checklist before you ask for extra effort:

  • Have you named the contribution people are making, rather than treating it as expected?
  • Is there anyone for whom the current demand is genuinely too much, and have you asked?
  • Are people able to say they are at capacity without being seen as disloyal?
  • Is the long-term relationship being protected, or only the short-term deadline?

Morale is not a soft extra. It is the capacity the team will need for the recovery phase.

The leader's own capacity

A prolonged crisis does not only consume the team. It consumes the person leading it, often without obvious signs until much later.

One pattern worth recognising: time off that is not real time off. A holiday during which you check the news first thing, check it again through the day and check it last thing at night is not recovery. It is the same vigilance in a different location. Over months, that pattern erodes sleep, exercise and attention, and it reduces the quality of the leadership it was meant to sustain.

A self-monitoring checklist:

  • Sleep: is the pattern stable, or has bedtime and wake time drifted?
  • Exercise: has it stopped entirely, and for how long?
  • Disengagement: can you name a period in the last week when you were not monitoring the crisis?
  • Support: who else can carry part of this, and have you asked them?
  • Family and close relationships: are they receiving the attention they need from you?

None of this compares to the direct experience of people at the centre of a crisis. But a leader who is exhausted is less able to help them, and that is a practical reason to manage your own energy, not a self-indulgent one.

Belief that the situation can be survived

The people around you take a cue from whether you believe the situation is survivable. That belief has to be honest, not a slogan. It is built from evidence: previous difficulties that were worked through, the specific capabilities the team has, and a realistic view of what recovery would look like.

Two practices support it. The first is sharing responsibility with the right people rather than carrying the whole problem alone; done properly, this gives others real ownership rather than a token role. The second is keeping enough people focused on their strengths so that the business is not entirely consumed by the crisis.

A short reflection exercise for the end of a crisis week:

  • What did we get through this week that we were not sure we could?
  • Who took on something difficult, and have they been told it mattered?
  • What is one thing we will change so that the next occurrence is less severe?
  • What is one thing we will keep doing because it worked?

Frequently asked questions

Should a leader show stress during a crisis?

Show that you understand the situation and share some of the concern, but keep your outward behaviour steady enough that people can function. Hiding everything can look distant; visibly panicking transfers the anxiety to the team.

How much should customers be told while a problem is unresolved?

Tell them what affects them, what you are doing and what they need to do. Keep speculative internal detail for the retrospective, once a fix is in place and you can talk about the future with confidence.

Is it better to involve the whole team in solving a crisis?

Usually not. Keep most people doing their normal work well, and give a smaller group the focused task of fixing the issue. Involving everyone can burden the whole business and slow everything down.

What is the first sign that a leader's own capacity is failing?

Time off that is not real time off is a common early sign: checking updates first thing, through the day and last thing at night. Drifting sleep and stopped exercise usually follow.

How do you know whether culture survived a crisis?

Look at whether training, coaching and individual consideration continued while the pressure was on, and whether people would say the organisation behaved as it claims to. If those slipped, the culture was revealed rather than interrupted.