Comment Operations resist change. (Score 4, Interesting) 57
I'm not saying this is the case in this event. But it could be a factor.
In almost all organisations I have worked in, the Operations area resists change. There is good reason for operations to resist change. Change adds risk. In sensitive environment any level of risk is to be avoided.
Specifically almost all operational areas have an up time KPI. Changes especially frequent changes present a risk to up time. Most if not all operational managers are have a pay component tied to uptime/availability.
Secondly it's often quite common for operations to also own the patch cycle. This is fairly straight forward at the OS level and standard apps level. It's not so straight forward with vendor and PaaS / SaaS platforms. PaaS/SaaS platforms often have data transforms attached to the patches and upgrades. Operational managers are NOT application owners. They generally have very little understanding of how the platforms are used, what is important and how the day to day works of business workflows. So generally operational managers will not patch platforms at all unless someone else takes the responsibility and accountability.
So it is possible that this exec had conflicting responsibilities and did not understand the risks of not patching vs other responsibilities like uptime.
( I have avoided the topics related to devops and agentic owned environments. I don't believe either of these apply in this case. )