The Signal You Send When It All Goes Wrong

I’m starting with something you won’t find in any leadership competency framework.

Mops.

Back in February 2018, KFC ran out of chicken across the UK. Hundreds of restaurants shut their doors. People got angry. The brand faced a public mess, fast.

Here is the detail that matters for you as a people manager.

KFC did not fix the crisis with a speech. They fixed it with logistics, including moving non perishables like mops and brushes out of a depot, so they could move chicken through it again. They used temporary warehousing to create space and speed.

On the same day they launched their famous “FCK” apology advert, they also got practical about storage and flow. That combination of clear messaging and boring action helped them reopen most sites quickly.

This is the angle we want you to hold onto. Calm is not a mood. Calm is a signal.

You send it through what you do first, what you say first, and what you refuse to rush. You already know the temptation. Something breaks. Your phone lights up. Your team starts guessing. Someone wants an answer in five minutes. You feel pressure to prove you can move. Speed looks like leadership. Sometimes speed just looks like noise.

When stress hits, your team watches your tempo.

Not your words. Your tempo.

If you jump straight into solutions, you train people to bring you problems late, because they fear you will react. If you fire off messages at pace, you create more messages. If you answer every question the moment it lands, you set a standard you can’t hold.

You do it with three moves.

First, name what you know, in one sentence. Not what you fear. Not what you heard second hand.

Second, name what you do next, in one sentence.

Third, set the next update time, even if you feel you have nothing new yet. That third move changes everything. It stops the team from filling silence with stories. It also protects your attention.

You choose a rhythm, then you lead inside it.

The UK Health and Safety Executive puts a hard edge on this. Communication keeps people safe during operations and emergencies. Clear spoken and written communication matters, because teams rely on it when things change fast.

Ask yourself a blunt question. When your team reads your first message in a crisis, do they feel steadier, or do they feel pushed to panic faster?

Calm is clarity under pressure, not softness.

We’ve talked about US Airways Flight 1549 before, the Hudson River landing in 2009. The public story focuses on the landing. The leadership lesson sits in the cockpit audio and transcripts, which show a calm, direct exchange with air traffic control. The composure stands out because it stays consistent when options shrink.

You don’t need to fly a plane to learn from that. You just need to notice the pattern.

Calm leaders do not add extra words. They do not perform certainty. They keep language simple so other people can act.

In your world, calm sounds like this.

“I have confirmed X. I have not confirmed Y. I need Z from you by 2pm. I will update you at 3pm.”

That is it. No long context. No emotional spill. No attempt to sound inspirational.

Here is the test.

If someone forwards your message to another team, will it reduce confusion, or spread it?

Most crises do not fail because the leader lacked courage. They fail because basic work got ignored, or delayed, or left to the wrong person.

Maersk/Ukraine learned this in 2017 during the NotPetya cyberattack. Their systems went down on a huge scale. They set up an around the clock emergency operation and rebuilt at speed, including thousands of servers and tens of thousands of PCs in around ten days. That did not happen because someone shouted “move faster”. It happened because leaders set direction, protected priorities, and let teams do the dull rebuild work without distraction.

Your version might not involve servers. It might involve rota gaps, a safeguarding incident, a major customer complaint, a safety breach, or a project that suddenly stops. The principle holds.

Calm leaders value the boring steps that unblock the real work.

Here is a practical exercise you can run this week.

Pick one risk you already know sits in your team.

Choose one that feels likely, not dramatic.

Then ask:

• If this happens on Tuesday at 10am, what is the first decision I must make?
• What “mops” will slow us down, because we have not sorted them yet?
• Who owns the first hour, and what do they need from me to do it well?
• What message will my team need in the first five minutes, and what message will they need in the first five hours?

Write your answers in plain language. If you cannot write them, you cannot lead them under pressure.

The calm signal you send starts before the crisis

A crisis exposes habits. It does not invent them. If you want to lead with calm, train your team in calm when nothing burns.

Set norms for how people escalate issues.

Set norms for how you make decisions, and how you communicate uncertainty. Practice short updates. Practice saying, “I do not know yet, I will know at 3pm.”

If you want a different lens on this theme, we touched on it in an earlier post, but this one aims at the mechanics you can use day to day.

If you want support building these habits across your managers, get in touch with TEG UK. Sign up to our newsletter as well.

We share tools you can use immediately, not theory you forget by Friday. And if you take nothing else from today, take this:

When your next crisis lands, your team will not ask you for heroics. They will ask you, silently, to move the mops.