MENU
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
Why LFI?
Papers and Books (COMING SOON)
Outside Software (COMING SOON)
Operational Surprises
In Practice
How to

Featured Posts

How to
Characteristics of Next-Level Incident Reports in Software
Ryan Kitchens
January 14, 2020
In Practice
Improving Incident Retrospectives at Indeed
"Lighten up the retrospective template."
Alex Elman
January 6, 2020

Most Recent

How to
Characteristics of Next-Level Incident Reports in Software
Ryan Kitchens
1/6/2020
In Practice
Improving Incident Retrospectives at Indeed
"Lighten up the retrospective template."
Alex Elman
12/23/2019
The Changing Climate of Resilience in Software
J. Paul Reed
12/10/2019
How to
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.
Silvia Botros
12/8/2019
How to
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.
Will Gallego
12/1/2019
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
11/28/2019
Why LFI?
Introduction
Let's shake things up a bit.
Nora Jones
11/26/2019

Join the newsletter

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form

HomeCategoriesAboutContact