From the preface and Chapter 1 of Product Management in Practice, what really struck me is how product management is like walking a tightrope between leadership and ambiguity. Matt LeMay brings out the reality that being a PM is less about following structured frameworks and more about adapting to shifting needs while bringing people together. It made me realize that PMs are not just product experts—they’re relationship builders who have to juggle priorities and manage the dynamics of multiple teams, all while having little direct authority. I found this incredibly challenging but also fascinating.
The part that resonated most with me was the idea of “lots of responsibility, little authority.” As a PM, you’re essentially accountable for the product’s success or failure, but you’re not always the one making the final call. This requires a delicate balance of influence, where you’re not pushing people, but rather guiding them toward a shared vision. It’s about earning the trust of engineers, designers, and stakeholders who might not report to you but need to feel your leadership. For someone like me, who thrives in structured environments, learning to embrace this fluidity seems like it would be one of the hardest yet most rewarding aspects of the job.
Another point that stood out was LeMay’s emphasis on dealing with ambiguity. There’s something freeing in knowing that you don’t need to have all the answers but instead need to be curious and resourceful. The idea that successful PMs are the ones who ask the right questions and adapt in real-time resonates with me because it aligns with my belief that leadership is more about listening and facilitating than micromanaging.
Here are a few things I’d love to ask Matt LeMay:
- How do you manage to lead without official authority—what’s your strategy for building trust, especially with those who may have different priorities?
- When faced with constant ambiguity, how do you decide what to focus on and how do you keep your team motivated?
- For someone who is used to technical roles, where there’s often a clear path, how do you suggest making the leap into product management, where ambiguity seems like the norm?
LeMay’s take on product management being more about people than products really shifted my thinking. I now see the PM role as one that requires not only technical understanding but also emotional intelligence, adaptability, and the ability to keep things moving even when everything feels uncertain. It’s a tough balancing act, but one that seems incredibly impactful when done right.
