The Psychology of Crisis - How Technology Professionals Respond to Disasters

You've dealt with disasters before. You know exactly what it feels like.

The alert fires. Slack explodes. Your phone won't stop ringing. And somewhere between the first alert and the fourth cup of coffee, something quietly goes wrong.

Not with the database, but with the people trying to fix it.

The DBA who's been doing this for fifteen years suddenly cannot make a decision.

The team that runs like clockwork in normal conditions goes completely silent.

Someone abandons the well-written runbook and starts improvising.

And the whole time, the clock is running, the business is bleeding, and everyone is looking at you.

You trained for the technical failure. Nobody trained you for this.

This session is about the part of disaster recovery that nobody puts in the documentation: the human part. We'll look into why smart, experienced engineers fall apart under pressure, why your team communicates worst when it needs to communicate most, and why the runbook you trust with your career gets ignored at the exact moment it matters.

This isn't soft skills fluff. It's cognitive science applied to the scenarios you actually live through. It's the 2 a.m. calls, the executive escalations, and the post-mortems where you sit there wondering how it got so bad so fast.

Because the gap between a one-hour recovery and a six-hour one usually isn't the technology. It's what happens inside you that matters.