By Marty Cagan · svpg.com · LinkedIn
Marty Cagan argues that the title "Product Manager" means very different things across companies and industries, a symptom of how young high-tech product development still is. Rather than wait for standardized titles, he proposes breaking the job into shared responsibilities: opportunity assessment, product specification, product design, project management, and product marketing. Each responsibility is described along with who commonly owns it and why. He concludes that the defining responsibility of a product manager is specifying the product, and that the other responsibilities are optional add-ons. This framing helps teams clarify expectations regardless of what the role is called.
01Key takeaways
- Define product roles by their responsibilities rather than relying on inconsistent job titles.
- Make opportunity assessment a core participation area for product managers, not an afterthought.
- Treat the product specification as the central output, describing behavior and experience rather than implementation.
- Decide deliberately who owns project scheduling, choosing based on company culture and project size.
- Recognize that product marketing and product definition require different skills and may need separate owners.
02Key sections
- The problem with titles
- The meaning of "Product Manager" varies widely by industry and company, which Cagan sees as a sign the field is still new. He suggests focusing on responsibilities instead of waiting for standard titles.
- Opportunity identification and assessment
- Ideas can come from many sources, but someone must rigorously evaluate whether they are worth pursuing. Cagan thinks product managers should at least participate in this, often captured in a broader document than a market requirements doc.
- Product specification
- Once an opportunity is chosen, the solution must be defined in terms of features, user experience, release criteria, and timing. Cagan calls this the heart of the job, focused on behavior rather than implementation.
- Design and project management
- A good spec needs designers as partners, and project scheduling and tracking can sit with a dedicated project manager, the engineering manager, or the product manager depending on culture and project size. Larger projects benefit from skilled dedicated project managers.
- Product marketing and the defining role
- Outbound messaging is a distinct marketing skill that is often combined with product management. Cagan concludes that specifying the product is what makes a role true product management, with the Microsoft program manager example illustrating the naming confusion.
03From the post
“A partnership dedicated to teaching best practices to product teams and product leaders”
04Frameworks mentioned
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.