It's actually very hard to generalize these statements. I wholeheartedly agree that a great PM is a great advocate for the team, bringing team issues forward a

It's actually very hard to generalize these statements. I wholeheartedly agree that a great PM is a great advocate for the team, bringing team issues forward and freeing the way to get stuff done. On the other hand it's often a tight rope to walk. I've seen situations often enough where a dev team would like to change frameworks/backends/dev environments/codebases, whatever it might be. And this has to be weighed between short- and long-term success. This is where a more technical product manager shines. On the other end of the scale I've seen dev teams walk all over their (non-technical) PM because they knew they could do so. It's a give- and take between team happiness and advocacy as well as end-user satisfaction and what the company needs at any given point in time. Being a great PM is actually much harder than it seems at first.