A terrible, horrible, no-good, very bad day at Slack

Re:A terrible, horrible, no-good, very bad day at Slack by cuu508 on Tuesday July 07, 2020 @04:23AM (#23756906)

That's an excellent TL;DR, thank you!

Postmortems should start with a summary paragraph like the above, and then go into story and full details below.

[ Parent | on HN ]

Re:A terrible, horrible, no-good, very bad day at Slack by yawaramin on Tuesday July 07, 2020 @07:49PM (#23765584)

BLUF style–Bottom Line Up Front. Often used by the military for field action reports.

[ Parent | on HN ]

Re:A terrible, horrible, no-good, very bad day at Slack by pradn on Tuesday July 07, 2020 @11:05PM (#23766523)

The internal Google postmortem format does require a 1-2 sentence summary. Absolutely vital for being able to learn from mistakes. No one is going to parse walls of text when browsing through post-mortems.

[ Parent | on HN ]

Re:A terrible, horrible, no-good, very bad day at Slack by antoinealb on Wednesday July 08, 2020 @06:32PM (#23774933)

Here is an example of such a postmortem format if people wonder: https://landing.google.com/sre/sre-book/chapters/postmortem/

[ Parent | on HN ]

Re:A terrible, horrible, no-good, very bad day at Slack by kergonath on Tuesday July 07, 2020 @04:30PM (#23763684)

This. The linked post is unreadable.

[ Parent | on HN ]

Re:A terrible, horrible, no-good, very bad day at Slack by jacksonpollock on Tuesday July 07, 2020 @02:20PM (#23762331)

agreed!

[ Parent | on HN ]