Product should be the glue between teams and create efficient flow of data between stakeholders. Imo the problem with Product Manager is it's a catchall term w

Product should be the glue between teams and create efficient flow of data between stakeholders. Imo the problem with Product Manager is it's a catchall term when there are 4 types. Research, OPS, UX/UI and technical. They are all very different in their execution and value but they are seen by some as 'you manage the backlog but with data to prove my ideas aren't wrong' Zero point of having a PM if this is how they get deployed. It's too bad as the role, when assigned and matched well, can cut through to the core pain points. Also 100% agree, you want to talk to high, medium and low supporters to get a good map. For one I worked at, I deployed receptive.io (now part of Pendo) and it showed every customer demographic wanted a specific feature and ALL their great ideas where shit on by the users. The echo chamber at C level is, imo, the reason PMs get sidelined.