A product manager’s role is a dynamic balance between strategy, execution, and communication. They act as a bridge between various teams—engineering, design, sales, and marketing—while ensuring the product vision aligns with business goals and customer needs. The job often requires making difficult timelines, prioritizing tasks. Successful product managers mix analytical thinking with creativity, all while improving collaboration and solving conflicts.
In Matt LeMay’s book, “Product Management in Practice,” one of the core concepts he emphasizes is the importance of focusing on outcomes over outputs. This resonated with me because product management isn’t just about delivering features but about achieving meaningful impact for users. A PM must always be questioning what real-world problems the product is solving and how to measure success.
The book also emphasizes the importance of strong communication skills for a product manager. A PM often works in a cross-functional capacity, which means they must bridge gaps between different teams with varying goals, languages, and concerns. This requires not just technical knowledge but also empathy, as a PM must navigate conflicting priorities while fostering a collaborative work environment. LeMay’s advice on managing these relationships without formal authority is particularly important, as it underlines influence and trust in the role.
If I had the opportunity to ask him a few questions, I would ask:
- When there is a conflict between what drives revenue and what users find valuable, how should a PM prioritize?
- How can a PM be quick and efficient when there are constantly changing requirements from stakeholders or unforeseen technical constraints?
- What specific strategies should a PM have to build trust without formal authority, especially in cross-functional teams?
