https://en.wikipedia.org/wiki/Peter_Principle
https://en.wikipedia.org/wiki/Parkinson%27s_law
Mind you, I'm not sure getting rid of the managerial staff is enough to address these problems fully.
I wonder if there's any managers around who also code? Maybe 50% of their time could be management, 50% coding. Nothing like getting hands dirty with the company code to see where things are at.
Shared management roles could also be an option. Or, manage by committee? There's enough design by committee happening, surely we can all jump in on management decisions?
An important part of the reason why so many technical people have an "overblown" idea about the inefficiency added by management is negative experience.
I have met maybe a dozen people who were in management position and were not completely and utterly incompetent at what they were managing. More often than not, the managers I meet were people who started out as programmers, but quickly realized they don't stand a chance building a career out of it. This is an incredibly common career path.
I had one really good coder cow-orker who became my manager. He tried, and it was pretty poignant at times, but eventually realized the truth. Until he did, he mostly sucked at both jobs.
I think this becomes one of the reasons that so many managers end up being viewed in a negative light.
Surely part of a manager's job is to protect the team from external pressures. The decision to delegate should be made on the basis of the impact of delegating / not delegating, not on how dreadful the task is.
Its awesome at getting rid of "pass the buck" and awesome for everyone else in the org to have a single point of contact (even if its a different human each week). Not so awesome around changeover time or if your docs aren't up to spec or when you discover the hard way someones code isn't good. Also not so hot at fixing major architectural issues (like, its going to take more than a week to fix this correctly, and I'm only on duty for a week, so whip out the band aids...)
As much as DevOps is being promoted, there are still two fundamentally different skillsets and job descriptions, and if its just the Ops side of the house getting the 2am wake-up pages, you're going to get a decidedly different attitude toward Things Wot Breaks Prod than if the developers are on that rotation as well.
Plus it means rotation comes up that much less often, which is a good thing.
Yes.
Though there is such a mental disparity between coding and higher level management that it is not 100% efficient.
You're either coding or you're managing. You can't be knee deep in an obscure rendering bug whilst also still mentally committing to keeping track of what everyone else is doing. Getting back up to speed (from either one to the other) always takes a small amount of time.
There are plenty of things that managers do, that could just as well be done by some kind of junior administrator.
Comment above about Parkinson's Law and the Peter Principle are duly noted. ;-) I was a manager for a while, so I don't exempt myself from those observations.
One of them had worked in the past for Microsoft and said the fed was remarkably similar. I suspect any organization approaches the fed exponentially as its size approaches, say, tens of thousands.