August 2019CIOAPPLICATIONS.COM9learning from those failures, do we understand, improve and grow. A DevOps transformation cannot succeed in a fear-based culture. DevOps at its core is about empowering people to do their jobs safely, encouraging autonomy, and trusting your staff to make decisions. With that trust, comes the risk of failure. But does your culture fear failure so much, that you avoid it at all costs? Create an environment where people can fail safely. Where experimentation is allowed and encouraged.A real world example from my company--A team worked on a new feature for quite some time. On the day of the release, the feature ran into some major problems. We had prepared for failure, however, by wrapping the feature in a feature flag. Additionally, key metrics were identified for monitoring. When the metrics indicated failure, we turned the feature flag off and everything went back to normal. We celebrated this partial victory! We received valuable information that we couldn't replicate in a test environment and we were able to do it with very little impact to the overall user community. We shared that experience with other teams so they could replicate the pattern as well. We fixed the production edge cases, and a week later, the second release was completed without a hitch.DevOps at its core is about empowering people to do their jobs safely, encouraging autonomy, and trusting your staff to make decisionsWhen you have a fear-based culture, employees are always worried about retribution or punishment. This fear causes us to draw ourselves inward. It forces us to erect silos in order to ensure that our work has nice, clean, sharp edges. We want to make sure that my work and your work could never be confused as to avoid getting wrapped up in your failure. This fear creates a culture of disengagement amongst team members. People lose focus on the overall goal of a task and instead focus on delivering to the letter, the specific request that was asked of them. This absolves the team member of any responsibility, because they simply did as they were requested. This behavior robs the organization of the expertise an employee might have, because they don't offer it. There are great resources for helping to build a culture that can be free of fear. Sydney Dekker deals with the topic extensively in his book Just Culture: Restoring Trust and Accountability in your Organization. Blameless Postmortems are a tool used commonly in the DevOps community. David Zwieback tackles the subject in his book, The Human Side of Postmortems. These are both excellent starting points on how to begin engaging your teams in an open, honest and trust building manner. Now, ask yourself honestly, do you have a culture that can embracefailure, learn from it and improve? Or are you a punitive culture that punishes mistakes and buries them instead. Are you losing the 98 successes just to avoid the two failures? If you are, you'll never see that DevOps dream. You'll just have new tools shackled by the same old fears. Jeffery Smith
< Page 8 | Page 10 >