This seems like it changes something with potentially super-high impact, 6 days from request by the CEO to release to production is a pretty good release time.
This seems like it changes something with potentially super-high impact, 6 days from request by the CEO to release to production is a pretty good release time.
As demonstrated by the end of the scenario, the 'solution' was the president to more directly intervene.
The failure in this scenario isn't necessarily that the process got in the way, it was that when the President and IT Director kicked off the action, they were not fully aware of the efforts and overrides required to escalate to 'do this now'. A converse failure is that the intent of the President and IT Director was not properly communicated to all stakeholders in the process.
Lol, nah. This is fiction, no company IRL is going to start laying off people after a few days of noticing a small dip in production.
The whole premise of "We own this company but if this code change doesn't go through in X days we will fire people instead" is completely stupid.
But it is an entertaining story and it gets the point through that internal bureaucracy gets in the way of many things.
I like the description Jason Fried gave of policies being "organizational scar tissue" in response to a "cut" (i.e. something bad happening). He suggests that we don't scar on the first cut: