Yeah, but a lot of companies view risk management as -preventing- deployments unless every stakeholder has signed off on it. The process generally doesn't leave

Yeah, but a lot of companies view risk management as -preventing- deployments unless every stakeholder has signed off on it. The process generally doesn't leave room for making decisions quickly when everything is on fire. But I wasn't just referring to that; I was also referring to lead time in hardware requisitions and changes. I've been in environments where, to get Jenkins running, we put in an order for a box. It finally arrived (it actually came pretty quickly, within a week of our order, since we just expensed it, rather than went through the approved channels of requesting one from IT). We configured it. We needed to punch a few ports open in the corporate firewall so we could get push notifications when our hosted git repos were updated. We requested it, specifying only ~these~ ports, ~from~ this IP, ~to~ this other IP...aaaand, the powers that be denied it. To remain in process we could have escalated, taking even more time, but instead we just did what we should have done in the first place; we put our Jenkins in AWS (which we already have permission to use, and is not subject to the corporate IT policy), and the box we purchased was used for broadcasting to a monitor various data visualizations of our systems.