Chapter 1 discusses how being a product manager means embracing a wide range of responsibilities. This aligns with what we covered in class about the broad PM role but not as deep as the product designer or developer. This makes sense, as the core skills of a PM, as outlined in the book, are communication, organization, research, and execution.
The broad scope of the PM’s responsibilities helps bridge communication between different departments and stakeholders. PMs need to have a general understanding of everything to “translate” between, for example, a designer and a developer. As mentioned in the book, PMs must inspire, align, and motivate their team through communication and collaboration, acting as connectors across teams, whether it’s UX, business, or technology, to keep everyone aligned and informed.
Another key skill highlighted in the book is research. A crucial part of this is conducting user experiments. I would like to ask the author for more clarity on the framework for conducting user experiments, as that part remains somewhat ambiguous.
The author also mentioned that PMs often have to navigate through the atmosphere of ambiguity. I would want to learn about how to “navigate” because sometimes feelings of lost are counterproductive for a team. It ultimately hurts the team morale…
