Psychological safety, values, rituals, onboarding, engagement

Engineering Culture

Wanted to open up a discussion on how we handle postmortems - not just as a checkbox, but as a tool for real insight and organizational improvement.

Two-track postmortems is useful with different audience:

 Deep dive, full RCA (5 Whys, Fishbone analysis etc.), technical details.

 Timed summary aligned to incident severity - goal is visibility and buyin

 Great failures are opportunities to drive systemic improvements

 Failures should be looked at from the customer’s perspective -

 how did the outage manifest to the customer

 Postmortems should reach not just engineering leadership, but 

Embed remediation status into ops cadence:

 Roll up themes into monthly ops reviews- 

 look like for different severity levels? 

Curious to hear how others are scaling postmortem culture and closing the loop from incident to insight to improvement.

Making Postmortems Count – Beyond RCA to Organizational Learning

Home

Forum

Events

Content

People

Contributors

Albums

Chapters

Chat

Channels

Sub-Communities

Tools

Help

ELC is a safe, supportive space for engineering leaders to connect, learn, and grow. We value authenticity, sharing, and thoughtfulness, with a mission to unite leaders and advance tech leadership.

Copyright

Terms of Service

Privacy Policy

Code of Conduct

Login to the ELC community to connect with others, attend community events, and more!

Login or Sign Up for even more

To unlock all parts of the community and get the best experience, complete your profile.