The Yin and Yang of DevOps
A key part of building a no-blame culture is about how to do the postmortem. How do you do the retrospectives correctly, so that blame is not an issue? How do you create the environment where, if somebody makes a mistake and it causes an outage, that they raise their own hand and say, "Hey that was me, I did that, and what do I need to learn because that happened?" Through that kind of attitude, the whole team will learn.
What you do in the postmortem stays in the room, because the team trusts each other, and they'll solve it. I find that a lot of organizations don't build trust this way, and people in those organizations tend to be focused instead on building security for themselves in their jobs. The result is that those people will sometimes be opposed to each other.
Viktor Farcic: This is surely related to what you were saying at the very beginning of this discussion: that companies were, or still are, too much focused on how to prevent...