Kaizen and Skin in the Game
A key principle in DevOps is to not blame workers for failure. Instead, when failure occurs, the business is to identify the reasons behind the failure. (e.g. "Was the worker set up for failure? Or does the worker have defects that can be remediated?")
At first face, this idea of "no blame" runs contrary to the idea of skin in the game. For if I am not punished for my failures, how am I held responsible for my actions?
What actually happens is that DevOps redefines the game you have skin in. The game is no longer success, but improvement. So you are not held responsible for perfection, but for making things better.