I'm curious about how everyone else approaches root cause analysis (RCA) and postmortem discussions. Do you find these documents are just one-time reports, or do you actually implement changes based on what you learn? If you do reuse the lessons learned, how do you go about it?
3 Answers
I like to structure my RCAs with a clear format. I start with a summary and timeline, then provide a deeper technical analysis, followed by action plans. Typically, I focus on immediate changes like reviewing certain rules or making adjustments, plus longer-term suggestions for improvement—like advising clients not to store secrets within their code. It's straightforward and helps everyone stay on track!
Honestly, I'm surprised you all find these helpful. In our last meeting, the dev team basically shrugged and said they wouldn’t fix the issue but were planning a complete redesign of the app. Seems a bit drastic, right?
In my experience working at a bank, the main takeaway we've had is that we always need more approvals for changes. Usually ends up being a red tape nightmare!
Haha, right? The beatings will continue until morale improves! Classic!