What is a product manager?: As mentioned directly in the book, product management is one of those roles where you wear many hats, often without much direct authority. I mostly agree when the author captures this well by pointing out that a product manager’s responsibilities are broad, but their power is limited. If something needs to get done, it’s the product manager’s job to make sure it happens, even if it’s outside your official scope. As the “middle” between engineering, design, marketing, and leadership, you’re tasked with aligning teams and keeping everyone on the same page. I recently met with a product manager from Google, and they said product managers act as the “translators” between the functioning arms of a team. This interpretation seems to best align with the author’s perception of product manager’s being the “mini CEO” of their team.
What IS’NT a product manger?: But the author understands it’s important to understand what product management isn’t. The author makes it explicitly clear that you’re not the boss. While you might influence major decisions, you’re not the one giving orders. Nor are you responsible for building every aspect of the process from scratch. Instead, your role is to guide the process, ensuring that each function collaborates effectively. And if you’re waiting for someone to tell you what to do, you’re in the wrong mindset. Being proactive and taking ownership is crucial in this role. As the person in between functional arms of a team, you should supposedly pay most attention to making sure everyone is operating as a well oiled machine.
What is a good product manager?: I also agree with how great product managers are shaped by their experiences, both good and bad. Every project, success, and failure will teach you something valuable. That’s why staying open to challenges is so essential. Especially since the role comes with a lot of ambiguity, and the best product managers are those who can navigate uncertain waters confidently. They embrace the unknown and creatively turn obstacles into opportunities, steering their teams through the chaos to deliver great products. It could also be said, that good product managers leverage their diverse background to most creatively tackle issues; they draw on experiences in engineering, business, communications, etc. to solve ambiguous issues.
Questions for the author:
- How do you recommend a new product manager prioritize learning technical skills versus business and customer-focused skills?
- What are the most effective ways for an aspiring product manager to gain experience if they don’t have direct product management opportunities yet?
- How can someone new to product management demonstrate leadership and influence within cross-functional teams without formal authority?
- What advice do you have for preparing for product management interviews, especially when coming from a non-technical background?
- How do you recommend managing the transition from early-stage user research to building and validating a minimum viable product (MVP)?
