Matt LeMay’s Product Management in Practice reframes product management from authority to alignment. A PM’s role isn’t to dictate what to build, but to help a team learn what’s worth building. The best PMs don’t lead with answers. They connect people, context, and purpose so the team can move decisively in the same direction.
This view resonates with my own experience. On strong teams, the PM isn’t the loudest voice; they’re the clearest. They cut through noise, ask sharp questions, and bring shared understanding to complex work. LeMay’s idea that a PM’s craft is communication captures what makes the role both difficult and meaningful.
I also value his rejection of rigid frameworks. Too many PMs mistake process for progress. LeMay’s “minimum viable process” is a reminder that tools serve outcomes, not the other way around. The real skill is managing attention by knowing which conversations matter and which distractions to drop.
Still, I wonder how his approach holds up under pressure. How does a PM maintain empathy and alignment when deadlines loom? Where’s the balance between inclusion and speed? And how do you know when to stop seeking consensus and make the call? These are tensions I’d want to ask him about.
Finally, I’d ask how he defines success. Is it user impact, business results, or team cohesion? LeMay suggests it’s less about metrics and more about meaning and that a great PM helps people do their best work together.
That’s the kind of PM I want to become: not a decision factory, but a clarity engine.
