Smash Notes

Back to Anthony Eden - Making Business Look Simple, with Anthony Eden.

How Did Anthony Eden Make Blameless Incident Reviews Routine?

Post-incident reviews were institutionalized so every incident follows one set process. Even internal incidents still get a post-incident review. The only way to get better is to record what happened in a blameless post-incident report and state that the team will take action.

The reports are never perfect. Some post-incident reports were not resolved in a satisfactory way, and the shortfall became a lesson while the process kept evolving. No company, person, or entity is ever going to be perfect. Admitting incidents happen is the first step to getting better, and a lot of companies do not want to admit them. The stigma is a fear of lawsuits. Anthony Eden does not think a suit happens as often as people believe. Big companies have made the news for being sued, but for every one of them tens of thousands of other incidents never led to a suit. Oftentimes the motive is saving face and a wish to look perfect. Accept mistakes, learn from them, and get better.

Transcript

Anthony Eden - Making Business Look Simple ·

From the transcript

Oh yeah. Yeah. It has to be part of, in fact, so what we did is we institutionalized those processes at the end simple. And every single incident that we have, even if you all never see it, like these, these are things that happen internally, everyone and then gets a PIR, which is post incident review. Everyone follows, like we have a very, very set process because it's the only way we're going to get better is by recording what happened in a blameless post incident report and saying we will take action.

And we, it's never perfect. Like we've had times where we've done post incident reports that we haven't resolved in a way that has been satisfactory to us, but we've learned from that. And so we continue to evolve it and to get better and better. And no company, no person, no entity is ever going to be perfect, but we can always strive to get better and admitting that incidents happen, which apparently a lot of companies just really don't want to admit, is the first step.

See in transcript

IndieRails

More from this episode

  1. How Did Anthony Eden Become an Early Dot Com Seller?Anthony Eden passed the technical accreditation test to become a domain registrar in seven days in 1999, during deregulation of the dot com namespace, and…
  2. How Did Rewriting an Encrypted Job Application in Two Weeks in January 2004 Start Years of Work on .mp?On IndieRails, Anthony Eden says the story that got Anthony Eden into .mp began on New Year's Day in January 2004, when somebody in Hawaii reached out.
  3. How Did Postgres Copies Cut Australia's Hour-long Reload?On IndieRails, a name server in Australia could take almost an hour to reload because it connected to the core database and pulled all the zone data, while…
  4. What Hot Mess Pushed Anthony Eden Into Long-haul Domains?Anthony Eden says a domain name system business only runs at any sort of scale when the operator stays willing to continue evolving over time.
  5. How Did Building a Knowledge Base Refocus DNSimple?On IndieRails, DNSimple made a conscious decision to do a set of things and do them well.
  6. Why Does Anthony Eden Leave Space Open for New Ideas?Anthony Eden says optionality means you prepare and you open up so you are ready. If you do too much to fill all of your time, you have no optionality.

People

More answers like this

More with Anthony Eden

Related episodes

Plays from this note through the rest of the episode.

Weekly highlights

One letter a week.

The notes worth hearing, with the minute they were said.