That strongly strongly strongly depends on the team and contributors.
I'd agree at my startup employers. I would not agree about several teams I worked with at Apple, to pick on a corporate example. Teams built from the ashes of an acquired startup at Apple, again, I'd be more inclined to agree. You can't support a broad conclusion like that anecdotally, because I can counterexample it anecdotally, implying there's more to it.
It really depends on the ICs in question. Startups are far more selective about their ICs because one person has a very big impact. With the exception of Google and a couple others, large-cap corporate throws IC quantity at problems and distinguished, autonomous, "rockstar" (sigh) ICs are far more rare. You need the cat herders there.
It does depend on the contributors, and obviously depends on the culture of the company (ie, if everyone assumes managers are supposed to do it, nobody will do it).
You can't rely on any random grouping of people to decide well on what's important to do and how to effectively break up the work. But adding a random manager to that group doesn't help specifically. Adding a more experienced IC will generally help more than a less experienced manager.
I'd agree at my startup employers. I would not agree about several teams I worked with at Apple, to pick on a corporate example. Teams built from the ashes of an acquired startup at Apple, again, I'd be more inclined to agree. You can't support a broad conclusion like that anecdotally, because I can counterexample it anecdotally, implying there's more to it.
It really depends on the ICs in question. Startups are far more selective about their ICs because one person has a very big impact. With the exception of Google and a couple others, large-cap corporate throws IC quantity at problems and distinguished, autonomous, "rockstar" (sigh) ICs are far more rare. You need the cat herders there.