Why can I handle small crises but not the big ones?
Picture it exactly. Your best engineer quits the week before launch. Or the client who promised the deal pulls out, in front of your team, right after the board meeting. You don't freeze because you lack skill. You freeze because this crisis attacks something a missed deadline never touches — your sense of who you are and what the team thinks of you. Small crises are solved problems wearing new clothes. You've handled fifty of them. The big ones feel unsolved because they come bundled with a story — about your judgment, your worth, your team's trust in you — and you try to fix the story and the fire at the same time. You can't. Nobody can. Your team feels this before you say a word. When the big one lands, they check your face before they decide how scared to be. If you're sorting the loss from the meaning in your head, it shows. If you're not, that shows too.
The big ones overwhelm you because you've only trained for the small ones. A missed deadline needs triage — a known problem, a known fix. A collapsed deal or a key person quitting mid-launch needs something else: separating what is actually lost from what you fear it means about you. Train that separately, before it happens.
What changes unlock by starting
- You and your team have a written first move for your worst three scenarios, decided before you need it.
- You separate the loss from the story faster, with less heat, in the room.
- Your team reads your face accurately and takes a calmer cue from it.
- Fewer events get filed under 'the big one' because you've already sized them down in advance.