A product manager’s role involves being “in the middle” of diverse teams, connecting people, aligning various perspectives, and ensuring that products are built with users’ needs in mind. This concept really resonated with me because it highlights how a PM’s job isn’t about being the technical expert or visionary, but about enabling collaboration across all departments. Product managers are responsible for bringing clarity to ambiguity, navigating conflicting interests, and ensuring the team remains focused on the core goals.
What stood out to me is how the book avoids romanticizing the product management role. Instead, it portrays the day-to-day grind of balancing strategic vision with execution, often without clear guidelines. LeMay also emphasizes the importance of not waiting for someone to tell you what to do. Product managers are expected to take initiative, anticipate challenges, and bring solutions to the table without waiting for explicit instructions. This proactive mindset is something I’ve experienced firsthand in my previous roles, where anticipating issues and stepping in to resolve them was key to driving progress.
If I could ask the author a few questions, they would be:
- For someone with a finance background, what skills are most transferable to product management, and which should I focus on developing further?
- For non-technical product managers, what’s the best way to build credibility with engineering teams without pretending to be a technical expert?
