Earlier quoted context omitted.
If we remove and automate away as much red tape as possible, is the remainder really that bad we still need a dedicated manager over a hybrid? Will somebody of the team not feel the urge or the will to pick it up instead? Do we still need a manager who has power over the developers and partially decides which jobs exist, giving them not only an incentive to create extra work, but have a trump card on anyone who would…
Manager as facilitator works awesome. Manager as controller sucks. One path gives the team power, the other gives the boss power.
For the former, a great manager will regularly ask, "What can I do to help you do your job well?" This person fights the political battles that need to be fought, takes bullets for the team, gets the team the resources they need, removes roadblocks, recruits, etc. The team already wants to work hard, wants to do their job well, and "manager-as-controller" is absolutely the wrong way to lead.
But when you're managing a team of undermotivated people doing more dreary work (which, honestly, might be most people and most jobs), a great manager will occasionally pick up a hammer and do some of the hard work themselves to boost morale. They'll find and remove the major pain-points of the day-to-day, improve training so the team is more productive, cheerlead a bit, try to improve compensation, make sure the team's major wins are visible to upper management so they can get the resources they need, etc.
But critically, this second type of manager ALSO needs to be able to crack the whip once in a while to make it clear that being deadweight won't be tolerated, and complaining won't be rewarded. When the work is somewhat painful, you really want to foster a kind of contagious, optimistic busy-bee state where everyone is eager to do their part and help one another, and you'll have to put on your "manager-as-controller" hat once in a while to get there.