I see a product manager’s job primarily as that of a facilitator. According to Matt LeMay’s Product Management in Practice, a successful product manager doesn’t command from above but instead collaborates across functions, ensuring that teams work together to achieve a shared vision. LeMay emphasizes that product managers act as “connective tissue,” bridging gaps between departments, such as engineering, marketing, and design, by translating business objectives into actionable tasks. This requires a deep understanding of the product’s technical intricacies – being able to “speak the language” of the engineers and developers – while also mastering interpersonal skills to manage cross-functional communication. Product managers must constantly mediate between competing priorities and viewpoints, maintaining alignment across the team and helping to steer the project toward a common goal. In this sense, the role demands a unique blend of strategic thinking, technical know-how, and emotional intelligence to balance the needs of various stakeholders.
My questions would be:
- Different companies utilize different hierarchical structures when it come to PMs. Some companies have the PMs at the same level as the engineers while other companies have their PMs higher up in the chain of command. Which structure do you think is best recipe for success?
- What advice would you give to someone starting out in product management to clearly define their role within a team, especially when responsibilities can be so fluid?
