In this case, it's management giving the impression that they are "doing something." We see the same thing with, "can we add more developers to speed this up?" The answer is almost universally "no" and, presumably, any manager in the modern era should have read (or at least be familiar with) the over 40 year-old book, "The Mythical Man Month." But, from a senior management position, there aren't many levers to pull--and when the heat is on, they have to be seen to "do something."
One interesting source on the topic (there are many others):
https://www.nytimes.com/2014/09/05/upshot/4th-down-when-to-g...
A certain design and a certain set of requirements is what defines the time table. You can influence it to a very small degree by adding more people, but that's it. Nothing anybody can do will make it faster, unless they propose a better more efficient design or way of doing it. Or reduce the requirements.
Worse, too many are interested in building a general solution when they haven't even done a single concrete solution. I have yet to find a proud developer that said, "I used the boring choices for this problem and got a solid solution."
This is akin to expecting an artisan to give better results for a standard kitchen than a builder would get from buying Ikea.
And don't take that as some sort of value judgement either way. Builders are there own to of Craftsman. Different doesn't need a hierarchy.
My gut for why this is? In a fiercely competitive field, leverage from success is the primary driver. And you get more leverage and success by being different. The upside is huge. Naturally, so is the downside. Survivor bias kicks in and people think they succeed from wiser choices, so they are incapable of reflecting and making less risky choices as they age as an org. Which requires an influx of young risk takers that have not hit a downside yet.
That said, probably nothing too deep. I certainly wasn't aiming for it.
My main points:
* Most of us in engineering focus on intrinsic measurements of our code's quality. These don't generalize well to product quality
* Nothing wrong with being a builder, instead of an artisan. Especially when it comes to building.
* Most people that succeeded fall to survivor bias and think they know why they succeeded. They are usually wrong.