News for hackers. Stuff that matters.
Re:Root Cause Analysis? You're Doing It Wrong by taeric on Monday October 13, 2025 @06:12PM (#45573880)
If your root cause is cross team, then you wind up having to make some implicit assumptions on what the other team could have done. Is akin to ending with "because the gods got angry." Not really actionable.

This is a classic "limit the scope of the feature." You want the document to be written and constrained to someone that is in a position to impact everything they talk about. If you think there was something more holistic, push for that, as well.

Note you can discuss what other teams are doing. But do that in a way that is strictly factual. And then ask why that led your team to the failure that your team owns.

Re:Root Cause Analysis? You're Doing It Wrong by hinkley on Monday October 13, 2025 @07:48PM (#45574604)
If the dynamic is cross functional you need to reschedule the post mortem and invite the other team to the meeting.

This is literally a "the right people aren't in the room" issue.

Re:Root Cause Analysis? You're Doing It Wrong by ghurtado on Monday October 13, 2025 @07:05PM (#45574279)
> on what the other team could have done

If you're wondering what anyone "could have done", you've already missed the point of the article completely.

Re:Root Cause Analysis? You're Doing It Wrong by taeric on Monday October 13, 2025 @07:30PM (#45574465)
I was just commenting further on why you constrain it to your team/area of control. Should have been more clear that I meant my comment as a plus one to some of the other replies.
Re:Root Cause Analysis? You're Doing It Wrong by ghurtado on Monday October 13, 2025 @07:45PM (#45574572)
Ah, thank you and sorry for assuming.