August 2021 Summaries

Lisa Karlin Curtis has joined our team after working as a Tech Lead at GoCardless. Previously, she was a consultant at Accenture and transitioned into development accidentally. She will be focusing on building the product, particularly the API and developer experience. In her personal life, Lisa enjoys sports like cricket and rugby, and also likes cooking for large groups of people. You can learn more about her through the Machine Unlearning podcast or by following her on Twitter at @paprikati_eng.

The text discusses the importance of conducting an incident debrief after resolving a problem or crisis, also known as post-mortems or incident analysis. It emphasizes that while every incident provides learning opportunities, it's crucial to decide when and how much time to invest in these activities considering other pressing tasks such as product features and system improvements. The article suggests several factors to consider when deciding whether to conduct a debrief: the benefits of simply showing up during incidents, leveraging policy or regulation requirements for learning, using incident severity as a threshold, seeking input from those involved, identifying local fixes to global problems, considering human error as a starting point for investigation, and demonstrating good debriefs to encourage more participation. The author concludes by acknowledging that while there are numerous reasons to conduct debriefs after incidents, it's essential to balance these activities with other responsibilities in an organization.