Product Manager’s Job
This chapter took a deep dive into breaking down both the responsibilities of a product manager and what profile exemplifies a good PM. In class, it was discussed that PMs could be viewed as the “CEO of a product”; in some ways, I do see this perspective reflected in the author’s discussion, but it’s important to note that as a PM, you’re not the boss. Instead, your success depends on the trust and hard work of your team.
What I found interesting is the author’s point that there isn’t a single “classic” profile of a great PM. Some might come from technical backgrounds, and some might not, and whatever background it might be, it’s just important that they exemplify qualities like adaptability, curiosity, etc. PMs are responsible for debunking ambiguity, identifying needs and use cases, and connecting everything together to align business goals with customer expectations. I also liked Melissa Perri’s framing that PMs are stewards of a value exchange between business and customers, signifying the practicality and impact-driven work PMs can contribute to.
PMs are what connect the internal workings between designers and developers, package it in alignment with business strategy, and ensure smooth delivery to customers. Most importantly, the author emphasizes that a PM’s job doesn’t stop once a problem is defined, the work extends far beyond that point, into execution, delivery, and iteration.
Questions for the Author
- I’m curious to know if there are specific frameworks that can act as a launchpad when ambiguity gets really murky.
- There were some discussions around differentiating the role/responsibilities of project managers and product owners: where does a product marketer fit into all of this? At what point in the product lifecycle does a PM “hand off” to a PMM, and how can the two roles collaborate without overlap?
