I Don't Want the Details

The author recounts a pivotal moment when, after an engineering incident, their SVP of engineering cut off a detailed explanation with a surprising, yet profound, statement: 'I don't want the details. I want to know what we're changing.' This seemingly dismissive remark became a lesson in effective incident management, shifting the focus from understanding past mistakes to implementing future preventative measures.

• The SVP's core message wasn't to ignore the problem, but to assume competence and trust the team, moving directly to solutions.
• Traditional incident reviews often focus on 'why did this happen?', leading to detailed explanations that satisfy curiosity but don't always drive change.
• A good explanation can hinder change by normalizing the incident as an understandable, albeit unfortunate, sequence of events.
• The article advocates for asking: 'What are we changing so that the same class of failure is less likely next time?'
• This approach assumes 'reasonable people produced this outcome' and seeks to alter the system, not just assign individual blame.
• Effective corrective actions should be system-level, durable even if team members change, rather than relying on 'organizational folklore' or people remembering a specific conversation.
• While aiming for system-level fixes, it acknowledges that not every failure warrants a new process; conscious risk acceptance is sometimes appropriate.
• The SVP's initial statement, initially perceived as impatience, was a powerful declaration of trust, emphasizing systemic improvement over dwelling on individual actions or intricate timelines.

The piece ultimately champions a leadership style that, by trusting its people, can bypass unproductive blame games and instead channel energy into tangible, systemic improvements that genuinely prevent recurrence.