Comment by xp84

This seems like a "glass half full/empty" question: The top quintile (or so) of developers need little but to be given a mission statement or overall goals and commit access, but some managers bog down those people with improper use of meetings, process that gets in the way, too much 'digital paperwork' (did you fill out all 15 fields of the Jira ticket? etc), etc.

The bottom quintile never get anything done and hopefully you have fired them or convinced them to stop being bottom-tier. For the rest, to accomplish good work they need (A) to give a shit, which often is directly under your influence: how much they think their boss appreciates and cares about them is important. (B) to know what their strengths and weaknesses are so that they can improve, and (C) to be allowed to focus on the important things and not be pulled in 100 directions, which a good manager constantly keeps aware of and constantly tries to tune. A bad manager fails to do A, B, and C, and as such their teams are less likely to accomplish things.