How your engineering team can get more from incident reviews

How your engineering team can get more from incident reviews

You can’t build software without encountering incidents – from critical bugs to full-blown outages, dealing with incidents are an inevitable part of the process. But while there are plenty of tips for writing a good incident report, very few of them tell you how to facilitate the critical meeting where that report is assessed and discussed.

Ask five key questions

These questions facilitate discussion and encourage a growth mindset

The lessons and takeaways weren’t clear enough

By focusing on a single event with set questions, they often overlooked commonalities and trends across incidents.

Feedback informed our approach

To make sure these techniques were working we started sending automated surveys to our incident review Slack channel after each review.

Experimenting with the meeting format

Main improvements

Incident reviews are a mechanism of change in any company

If the way your organization processes failure is broken, boring, or painful, then your organization can’t reach its full potential

Flex your facilitation muscles

Facilitation is a learned and practiced skill – hard to perfect but hugely rewarding when done right

Let participants guide the conversation

Set a goal to generate at least four strong talking points: two based on the particular incident under review and two that addressed common themes

Source

Get in