Post Mortem Culture: Learning from Failure
summary
Survey of 45 engineers shows only 40% read postmortems and 60% don't practice them. Chaos Game Days run with a master of disaster, a first-on-call, and the team and finish when a written postmortem exists. A toolbox called Gaveta automates planning and orchestration, implemented in Go, using Terraform to provision AWS/GCP, Gremlin or Chaos Toolkit for attacks, Datadog for observability, Google Suite/Slack for scheduling/notifications, and Confluence/Jira for postmortem and action tracking, aiming to cut the typical 90-day planning effort.
AI-written summary · about
chapters (13)
- 0:00About me
- 1:17Have you written a Postmortem?
- 1:53Agenda
- 2:29What is a Postmortem?
- 3:53If Postmortem are good, why don't we do it?
- 5:28How to change a blameful culture?
- 5:43Chaos Engineering
- 6:01Chaos GameDays
- 7:12What does it mean in practice?
- 9:00Gaveta
- 11:50Gaveta uses a hexagonal architecture
- 19:00Promoting postmortem culture
- 19:35Thank you!
related talks
28mBlameless Postmortem Culture
25mCultural post mortems: an approach to learning and recovering when your people systems fail
51mEmbracing Failure and Learning from Our Mistakes with Effective Post Mortems
43mPostmortems, Learning & Blameless Culture
22mAfter Death
10mSimplify your postmortems and focus on scaling
07mDia de los Muertos - Postmortems that save lives
38mWhy software developers should build a resilience culture based on chaos engineering