Beyond Blame: Learning From Failure and Success

by Dave Zwieback

Failure is inevitable and a postmortem analysis, conducted in an open, blameless way, is the best way for IT techs and managers to learn from outages and near-misses. But when the "root cause" is determined to be "human error" (or worse, particular humans), the real causes and conditions are lost.

In this insightful book, IT veteran Dave Zwieback shows you an approach for making postmortems blameless, so you can focus instead on addressing areas of fragility within systems and organizations. If you re involved with assessing why something goes wrong on a project or at your company as a system administrator, developer, team manager, or executive the concrete steps in this guide will help you find a real solution that works.Recognize and mitigate the effects of stress during outagesLearn how to communicate effectively in a charged, high-stakes postmortem conversationCollect the necessary data before the postmortem beginsFocus on determining the actual causes and conditions of an outageLearn techniques for writing up a postmortem for either internal or external use"

Genres: Business, Leadership, Management, Engineering, Technology, Nonfiction

105 pages, Kindle Edition

First published October 29, 2015

About the author

Dave Zwieback has been working with complex, mission-critical I.T. services and teams for three decades. His career spans small high-tech startups, non-profits, and behemoth engineering, financial services, and pharmaceutical firms.

Dave is a trusted advisor & mentor at Mindweather LLC, which offers extraordinary support for tech leaders.

Reviews

[Leena S N · Rating 4 out of 5]

Small but lovely book talking about why root causes fail by stopping at blames and how organisations stop learning from such failures.

It was interesting to see the reference to Cynefin model, for complexity and learning models.

[Pavel · Rating 4 out of 5]

The book describes a pretty typical outage in a large organization, focusing on how to analyze root cause without blaming people. Four stars is because characters look over-typical. The engineer was fired for “causing an emergency” even it was obvious that he didn’t cause it, the atmosphere in the Company was very toxic but then over a few pages and citations of Kanneman’s book it overturned 180 degrees.

Doubtful, but okay.

[Tom · Rating 5 out of 5]

It is really a very good read, with some very useful insights. The way it is written is enabled me very fast to identify myself with the story, this will happen for everyone who worked in NW engineering and was hit by bug - yes Cisco I am looking at you.
It also encourages you to dive a little bit deeper into the topic of cognitive biases and how they affect us. Really recommended small book.

[Esraa · Rating 5 out of 5]

I love the book , As a computer engineer , I can definitely relate to the network outage.
We need to look beyond blame and shame and see what we can learn ,

[Sandro Manke · Rating 5 out of 5]

Finally came around to read this one and I think its a great intro to that topic even with further reading attached. Very much worth reading if that topic is of interest :)

[Jan-Willem Van · Rating 5 out of 5]

Kort verhaal waarom je verder moet kijken dan een persoon bij het inventariseren van problemen.

[BRIAN C NEWMAN · Rating 4 out of 5]

Short and illustrated through a storyline that takes you through a situation not unlike any in software development today.

[Lauren Villarreal · Rating 5 out of 5]

Incredibly clever fictional story which explains how to shift from the process of blame in the workforce to failing forward.

[Yiorgos Adamopoulos · Rating 3 out of 5]

Interesting, fast read, especially if you're in one of the most thankless professions in the world.

[Jan-Joost Bouwman · Rating 3 out of 5]

Never mind the format, this booklet introduces some important concepts and ideas. The blameless postmortem in itself is already important, but it also touches on a couple of interesting other ideas that lay at the basis of the blameless postmortem. Definitely will dollow up on some further reading. And will use the checklist in the end to have a look at our own postmortem process.
Yes, the story is not brilliant. I didn't get at all why the chapter about Linda's son was in there (or even what the point of her background was, where the other characters didn't have auch a baxkground scetch). And the switch Raj made from undisxlosing to advocate seemed farfetched. But he, that is ok. The message atands.

[Dak · Rating 5 out of 5]

A must-read for root cause analysis ... Which all too often stops at "found a scapegoat"

So you've been in a blame and shame culture, and you know it can be better. Here's a framework that expands on some very useful work published in HBR.

I can't wait to take it for a spin. It is consistent with the best root cause analyses I've been invoked in, and the worst.

[Jon · Rating 3 out of 5]

Nearly the entire book is in faux-case-study narrative. This book would have been a lot more useful if it had broken narrative to discuss the concepts at play rather than leave it up to a mix of reader deduction and insert-words-into-characters' mouths. There are certainly some great principles here, but needs a LOT more depth.

[Ivan Dimitrov · Rating 2 out of 5]

Pretty short, does not go into character building at all. Looks like a conference talk written as a book. At the end there is a short Appendix with a checklist on what/how to do post-mortems, that I've copy/pasted to my internal policy.

[Jens Rantil · Rating 3 out of 5]

Not so many surprises. I got what I expected. A great book for 1) managers that work in a toxic organization environment or 2) general people working in toxic american organizations. I believe we have less of these toxic company cultures in Sweden.

[Travis Volker · Rating 2 out of 5]

A fair concept regarding blame free debriefs and no consequence as long as you give a full honest account of everything that occurred. I didn't care for the story telling. It's clunky.

[Mike Fiedler · Rating 5 out of 5]

Short and sweet narrative that explores a scenario from multiple angles. Introduces some new terminology to handle communication about technical situations that have previously been confusing.

[Alev Haddadieh · Rating 5 out of 5]

Author has introduced a very useful framework than can be applied to any IT project. I have actually enjoyed the philosophical approach to the story telling.