But if you understand the problem, you'll also understand why the bureaucracy exist...
The problem is complexity of our systems, of modern society, has grown beyond the capacity for people in view of the problems to understand them.
I've seen systems with incompatible configurations cause issues like this. An application needs a security related setting turned on to ensure it doesn't pass bad data to an upstream server. This security related setting causes another problem with a necessary application on the server causing connection problems with it.
The upstream application put the bad data issue as a low priority issue because there is a workaround. The vendor application also has it as low priority with about a 5 month lead time because they also have a workaround. Both teams see the issue as fixed for now in their eyes because they cannot grasp the use of the tools in a system that interacts with an immense number of other applications. All of these issues get bundled up to management groups that argue back and forth about priorities because they have 100 other fires burning to, many of them serious issues like exploits in software and such.
And this is just software, something that is inherently flexible. Now imagine things like infrastructure where you have all kinds of critical systems stacked on top of each other, for example beside a new building or a new road. You can set schedules on working on the stuff in order, but these schedules break all the time because when you start digging you find even more issues. Suddenly projects are being pushed back months while drivers are screaming in frustration because the road is down to one lane forever.
The problem is complexity of our systems, of modern society, has grown beyond the capacity for people in view of the problems to understand them.
I've seen systems with incompatible configurations cause issues like this. An application needs a security related setting turned on to ensure it doesn't pass bad data to an upstream server. This security related setting causes another problem with a necessary application on the server causing connection problems with it.
The upstream application put the bad data issue as a low priority issue because there is a workaround. The vendor application also has it as low priority with about a 5 month lead time because they also have a workaround. Both teams see the issue as fixed for now in their eyes because they cannot grasp the use of the tools in a system that interacts with an immense number of other applications. All of these issues get bundled up to management groups that argue back and forth about priorities because they have 100 other fires burning to, many of them serious issues like exploits in software and such.
And this is just software, something that is inherently flexible. Now imagine things like infrastructure where you have all kinds of critical systems stacked on top of each other, for example beside a new building or a new road. You can set schedules on working on the stuff in order, but these schedules break all the time because when you start digging you find even more issues. Suddenly projects are being pushed back months while drivers are screaming in frustration because the road is down to one lane forever.