Skip to content
All articles

Crisis Management & Resilience for Engineering Leaders

Dean Jain

Dean Jain

Senior Staff Software Engineer · Enterprise AI, Data & Cloud Architect

· 5 min read

Crisis ManagementResilienceEngineering Leadership
---
config:
  theme: dark
  fontSize: 17
  themeVariables:
    fontFamily: "Comic Sans MS, Comic Neue, Chalkboard SE, cursive"
---
flowchart LR
    T["🚨 Threat appears"]:::danger --> W["⏱️ Recovery window<br/>(fast action minimizes damage)"]:::warn
    W -->|"act fast on imperfect info"| MIN["✅ Damage minimized"]:::good
    W -->|"wait for certainty"| MAX["❌ Damage compounds"]:::danger
    classDef danger fill:#FFB3B3,stroke:#D14545,stroke-width:2px,color:#0F172A
    classDef warn fill:#FFE6A8,stroke:#E0A106,stroke-width:2px,color:#0F172A
    classDef good fill:#BFEFC8,stroke:#3FA34D,stroke-width:2px,color:#0F172A

Figure 1: Every crisis has a recovery window. Acting fast on imperfect information beats waiting for certainty that never comes.

The instinct in a crisis is to gather more information before acting. That instinct is usually wrong. Every crisis has a recovery window, a period when fast action can minimize the damage. and it closes while you’re still collecting data. Leading through a crisis is about acting decisively on incomplete information, keeping your team moving, and then having the personal resilience to do it again tomorrow. Both are learnable. Here’s how.

TL;DR

  • Speed beats perfection. There’s a recovery window; fast, deliberate action inside it minimizes damage. Waiting for certainty forfeits it.
  • Raise the alarm early even if you might be wrong. And listen when others raise red flags to you.
  • Act in a loop: assess the situation, gather input, form a small flexible plan, break bottlenecks, and be ready to pivot.
  • Prepare for the messy middle. Progress is uneven; help the team keep momentum through setbacks, and stay close.
  • Resilience is built, not born on purpose, values, connection, and adaptability. You can’t lead a team through a crisis you’ve personally crumbled in.

1. Speed beats perfection

In normal operations, deliberation is a virtue. In a crisis, it’s a liability, because the cost of delay rises faster than the value of additional information. The reframe: a crisis isn’t a problem to solve perfectly it’s a window to act within. The leader’s job is to move while the moving is still useful.

That starts before the crisis is even confirmed. As a threat looms, alert people even though you could be wrong a false alarm is cheap; a missed window is not. The flip side matters just as much. Listen when others raise red flags to you. Many crises are preceded by someone junior trying to warn someone senior who waved them off. Building a culture where early warnings are welcomed, not punished, is itself crisis prevention. The leaders who handle crises best are the ones who already made it safe to sound the alarm.

2. How to act in a crisis

Acting fast doesn’t mean acting recklessly. It means running a tight loop: act, learn, adjust repeatedly:

---
config:
  theme: dark
  fontSize: 17
  themeVariables:
    fontFamily: "Comic Sans MS, Comic Neue, Chalkboard SE, cursive"
---
flowchart LR
    A["🔍 Assess<br/>the situation"]:::gov --> G["👥 Gather<br/>input fast"]:::obs
    G --> P["📝 Small, flexible plan<br/>(reasonable assumptions)"]:::server
    P --> B["✂️ Break bottlenecks<br/>clarify priorities"]:::gate
    B --> PV["🔄 Pivot as<br/>you learn"]:::good
    PV --> A
    classDef gov fill:#E0D6F5,stroke:#9B7EDE,stroke-width:2px,color:#0F172A
    classDef obs fill:#AED6F1,stroke:#2E86C1,stroke-width:2px,color:#0F172A
    classDef server fill:#A8E6D0,stroke:#2FA37C,stroke-width:2px,color:#0F172A
    classDef gate fill:#D7C3F2,stroke:#8E5BD0,stroke-width:2px,color:#0F172A
    classDef good fill:#BFEFC8,stroke:#3FA34D,stroke-width:2px,color:#0F172A

Figure 2: The crisis loop. Assess, gather input, make a small flexible plan, unblock the team, and pivot as you learn.

  • Assess and gather input. Quickly read the situation and pull input from the people closest to it fast, not exhaustively.
  • Make small, flexible plans. Build on reasonable assumptions and known information. In a crisis, a big rigid plan is a liability; a small adjustable one lets you course-correct as reality clarifies.
  • Break bottlenecks and clarify priorities. Remove whatever is slowing the team. Make the top priorities unmistakable, so people move without checking in on every decision.
  • Be ready to pivot. Your team may create the most value by switching perhaps temporarily to a new role. Hold roles loosely; the org chart serves the crisis, not the other way around.

Then prepare for uneven progress. Crises don’t resolve in a clean line there’s a “messy middle” of setbacks and false starts. Your job there is to help the team maintain momentum through it and to stay close during the uncertainty. Visibility from the leader is itself stabilizing: a team that can see you steady is a team that keeps working.

3. Resilience: the capacity to keep leading

Crisis management is the external skill. Resilience is the internal one that makes it sustainable. The APA frames it as a process rather than a trait: adapting well in the face of adversity, trauma, threats or significant stress.

You cannot lead a team through something you’ve personally crumbled under.

Resilience isn’t self-indulgence. It’s a leadership requirement. It rests on four sources you can actively cultivate:

---
config:
  theme: dark
  fontSize: 17
  themeVariables:
    fontFamily: "Comic Sans MS, Comic Neue, Chalkboard SE, cursive"
---
flowchart TD
    R["💪 Resilience"]:::gov
    R --> P["🎯 Purpose<br/>solve problems, develop others, contribute"]:::good
    R --> V["🧭 Values<br/>act from what you stand for"]:::server
    R --> C["🤝 Connection<br/>lean on others"]:::obs
    R --> A["🌱 Adaptability<br/>curious, positive, smart risks"]:::gate
    classDef gov fill:#E0D6F5,stroke:#9B7EDE,stroke-width:2px,color:#0F172A
    classDef good fill:#BFEFC8,stroke:#3FA34D,stroke-width:2px,color:#0F172A
    classDef server fill:#A8E6D0,stroke:#2FA37C,stroke-width:2px,color:#0F172A
    classDef obs fill:#AED6F1,stroke:#2E86C1,stroke-width:2px,color:#0F172A
    classDef gate fill:#D7C3F2,stroke:#8E5BD0,stroke-width:2px,color:#0F172A

Figure 3: The four sources of resilience: purpose, values, connection and adaptability.

  • A sense of purpose connect the hard work to something meaningful: solving real problems, developing others, learning, contributing to a cause. Purpose is what makes adversity worth enduring.
  • Living your values acting from what you stand for (honesty, respect, service, responsibility) gives you a stable footing when everything else is shifting.
  • Connection resilience is not solo. Lean on relationships; isolation amplifies stress, connection absorbs it.
  • Adaptability stay curious, look for the positive, embrace the new, and take smart risks. The rigid break in a crisis; the adaptable bend and recover.

This applies to your team too. Protect their resilience the way you protect your own. Watch for burnout, provide psychological safety, and pay attention to mental health, for yourself and for them. A depleted team can’t sustain a crisis response, and a leader running on empty makes worse decisions exactly when good ones matter most.

Why it matters: crises are not rare exceptions in an engineering leader’s life they’re a recurring feature. The leaders who come through them aren’t the calmest by nature. They’re the ones who act fast inside the recovery window, run a tight assess-plan-pivot loop, stay close to their team, and have deliberately built the resilience to keep showing up. Speed and steadiness, paired that’s the whole job when it’s hardest.

Further reading