Functional siloing - "dev", "ops", etc. - make it easier to pass the buck and blame others when things go wrong. In an environment where dev, ops, and other business functions co-operate and work together, it's not so easy to fall back on traditional scapegoats. DevOps approaches encourage us to move away from the harmful (and counterproductive) apportioning of blame for failure, but it takes effort and commitment from all involved.
I'll discuss the philosophy and motivations of "blamelessness", along with ways to understand the vital role humans play in making complex socio-technical systems safe, even when things go awry, along with advice on how to promote and foster a blameless culture in your workplace, and techniques for analyzing and learning from failures without resorting to finger-pointing and scapegoating.
This talk was originally given at DevOps Days Minneapolis on 18 July, 2014: http://devopsdays.org/events/2014-minneapolis/
A transcript is available at http://ind.ec/fallible