The people writing these updates are very obviously not technical and are least one step removed from the actual work being done to fix this.

▲

EvanAnderson a day ago | parent | next [-]

To be fair: I want the people who can speak most competently to a problem to be working on it versus writing commentary. Those highly-technical people can shine in the postmortem report.

▲

skeeter2020 a day ago | parent | next [-]

I disagree; the communication aspects - including external - are a hugely important part of any incident response. IME the biggest challenges in these situations are the many levels & combinations of communication and coordination. You don't need your best DevOps person doing it, but there should be plenty of competent technical product managers or engineering managers who could do this well.

	▲	NetMageSCW 6 hours ago \| parent [-]
		And how do those product or engineering managers get information on what’s being tried and what is being discovered without slowing down the process of fixing the issue?

▲

cyberax 21 hours ago | parent | prev [-]

Microsoft is not a small startup where the CTO is getting pulled into firefighting.

They should have established procedures for large-scale events, and they must include a coordinator whose entire job is to manage the external and internal communication.

▲

codingdave a day ago | parent | prev [-]

And that is a good thing. Well, maybe not good. But the last thing you need in a crisis is to pull people away from fixing the problem and make them type up status updates. Admittedly, having tech knowledge would help the writers - a technical incident management team would be better. But ain't nothing wrong with letting the PR folks write up words while the tech folk work on problem solving.

Actual tech write-ups can come later.