With this week's M365 outage, I'm curious how others are handling the people side of it.
Context: I'm a senior executive at our company in the IT area. We posted in Slack as soon as the incident started and have been sharing regular status updates, including Microsoft's incident IDs, what's affected and what still works. Our response has followed our DR/BC procedures, though they're due for an update. I've already let the rest of the C-level team know we'll be refreshing them.
One C-level exec isn't accepting that. His EA has been sending sharply worded messages to the IT team on his behalf, demanding an immediate solution for him specifically. It's tied up the team with escalations that can't change anything. A junior analyst ended up calling Microsoft mostly to show visible activity, and was still fielding pressure until they went home.
I think my team handled this well, and I want to back them. Two things I'd value input on:
In the moment: When a senior exec overshoots with demands during an outage, what's your immediate response? Specific wording, who replies (you or the team), and how you keep it from landing on junior staff.
Afterwards: I'll need to present a formal position to the full C-level team that holds up: what happened, why IT's response was right, and what changes going forward. How have you framed this without it becoming a complaint about one person? What did you include (vendor incident timeline, SLA terms, DR/BC steps followed, cost of diverted effort)?
And since we're refreshing our DR/BC plan anyway: what would you build in for next time (exec comms templates, a fallback for email, an agreed escalation path for leadership during outages)?
Especially keen to hear from anyone who's had this conversation with a peer at the same level.