<i>The whole point of DevOps is really to get your software developers to share in the pain that certain design &#x2F; development choices can cause.</i><p>This is a great characterization and one of the few views of DevOps I can get behind.<p>Unfortunately, in my experience some higher up emits an edict to &quot;do DevOps&quot; and for whatever reason that has fallen on operations (my area) to &quot;implement&quot; (a hazy concept and task) with little buy in from the design&#x2F;development side; meanwhile, some developers complain that they didn&#x27;t sign up to &quot;be on call&quot;, despite that they are only being tasked with such for their own team&#x27;s code.  In other situations, developers take it upon themselves to deploy stuff without feedback or involvement from the operations experts, and you end up with Shadow IT.<p>It has to be an organization-wide endeavor, and there has to be a culture of involvement of all the areas of expertise.