I used to work for an Independent System Operator (ISO)[0] and we used to have a sometimes painful process for rolling out any changes to production. It's been

I used to work for an Independent System Operator (ISO)[0] and we used to have a sometimes painful process for rolling out any changes to production. It's been a while and I don't remember it all, but it went something like this: 1. Fill out out a change request (CR) form and print it. 2. Have it signed by your manager and the managers of every system it touched, including business owners. 3. Attend the 2x a week meeting and explain your CR. In this meeting, explain what was happening, why, who authorized it, what to do if it failed, what to do if it initially worked but failed later (e.g, on a weekend). 4. Hope your CR passes the vote. 5. Implement your roll-out plan. This is a robust process. Where it breaks down--I felt--is when you need to fix a typo on the public-facing website that's managed by a CMS. 0 - https://www.eesi.org/files/070913_Jay_Caspary.pdf https://www.eesi.org/files/070913_Jay_Caspary.pdf