I don't want the details(michaelheap.com)
448 points by mooreds 20 days ago | 223 comments
tl;dr: When something goes wrong, skip the detailed explanation of why—reasonable people usually made reasonable decisions given their constraints, and empathizing with the causes tends to kill any urgency to change. Instead, ask what systemic change will prevent the same class of failure next time; vague commitments like "we'll communicate better" are organizational folklore, not fixes. Accepting a risk consciously is fine, but only if it's a deliberate choice rather than a way to avoid actually changing the system.
HN Discussion:
  • ↓Understanding causes is essential to designing effective fixes; the two questions aren't separable
  • ↑Agrees details often become blame excuses; focus on systemic fixes is what matters
  • ↑Endorses the SVP's sentiment about trusting rational choices and focusing on systemic change
  • ~Root cause analysis is flawed; complex failures have many contributing factors, and processes need pruning too
  • ↓The SVP was likely just managing a rambling report and executives can't meaningfully contribute without details