Not changing production systems at will; obviously you need processes and permissions in place to ensure you're not just trampling over prod whenever a dev thin

Not changing production systems at will; obviously you need processes and permissions in place to ensure you're not just trampling over prod whenever a dev thinks a change should happen. But I've been in corporate environments where "We need to deploy a new instance" requires four weeks of lead time. Or a new release is tested and ready to go, and rather than just running Chef to deploy it, both the devs and the devops people had to work with a team whose sole job was to run prod, setting up a time with them, and then handholding them through running the right commands, because they weren't sufficiently involved (or maybe one was, but the person you got today to run it wasn't). Etc.