Fabricio Buzeto CTO @ bxblue Postmortems are a well-established way to document the history of a project, especially when things break or don't go as planned. Most teams have a hard time keeping up with it. Among those who do, to get value out of it is also another challenge. Let me share how my team brought postmortems as part of our process. By not only making it a must-have when handling emergencies but also celebrating it we transformed it as a tool for team bonding. Also, bringing postmortems as an onboarding tool to newcomers. To finish, I'll share two occasions where our postmortems helped us avoid issues and paid themselves. — 0:00 Intro 0:26 Preamble 0:53 What's Postmortem? 1:55 Pre-mortem 2:28 = Autopsy 2:37 = Tool for learning 2:59 Types of Postmortem 3:35 Root cause analysis 3:56 The Detective 4:24 The Open Problem 5:03 The Celebration 5:35 How to keep up? 6:39 Conclusion — 🥇 Gold Sponsor: StackPulse 🥈 Silver Sponsors: Aval Digital Labs BoomerTechnologyGroup bxblue Certus Cybersecurity Chaos Native CrowdSec bol.com effx FireHydrant GoCardless Gremlin Locelle Nuaware PagerDuty Zühlke Group 7bulls.com 🤝 Media Partners: The New Stack Manning AWS Inside Dev — Website 🚀🪐 https://www.conf42.com Reach out 📧📭 mark@conf42.com Conf42 Discord 🧑‍🤝‍🧑💬 https://discord.com/invite/dT6ZsFJ5ZM LinkedIn 👨‍💼💼 https://www.linkedin.com/company/49110720/ Twitter 🎵🐦https://twitter.com/conf42com Conf42Cast @ Spotify 🎧 https://tinyurl.com/bnyj6a8y