Learning from Incidents in Software

Learning from Incidents
in Software

Incidents are costly. Without spending time analyzing and determining the conditions that exist in order for an incident to take place, we won't learn how to successfully remove nor recover from these conditions in the future. Let's help each other learn.

View Latest Posts

Papers and Books (COMING SOON)

Outside Software (COMING SOON)

Operational Surprises

Featured Posts

Obstacles to Learning from Incidents

"This might just sound like a matter of swapping out words, but it's actually a way of changing approaches"

February 5, 2020

Characteristics of Next-Level Incident Reports in Software

January 14, 2020

Most Recent

Obstacles to Learning from Incidents

"This might just sound like a matter of swapping out words, but it's actually a way of changing approaches"

Characteristics of Next-Level Incident Reports in Software

Improving Incident Retrospectives at Indeed

"Lighten up the retrospective template."

The Changing Climate of Resilience in Software

Teaching "the smell"

If the decisions we make during an incident impact how the incident progresses, then ignoring those decision making processes and what information they are based on ‘in the moment’ is detrimental to how well the team will learn.

Patience in Implementing Effective Incident Reviews

In all this hurry to get things done, to move on to the next project, to dig wide and deep into "the good stuff", it's easy to forget that learning, the real concrete durable expertise needed in a crisis, doesn't happen overnight.

Operational Surprises

OOPS! Learning from the incident you didn't have

"Incident severity is negotiable, but I've never heard engineers argue over whether something was a surprise or not."

Lorin Hochstein

Let's shake things up a bit.

Join the newsletter

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form