Product Management – Start Here

Marty Cagan offers a curated starting path for aspiring product managers who are overwhelmed by contradictory online advice. He argues that the product manager role is about ensuring what gets built is both valuable and viable, which is far broader than the product owner duties taught in Scrum courses. He distinguishes feature teams and delivery teams from empowered product teams, where PMs are given problems rather than features and must discover solutions through product discovery. He stresses that design and user research belong to the product designer, and that newcomers need roughly three months of real work with coaching to reach basic competence. The piece matters because it reframes the PM job away from project management and toward outcomes.

01Key takeaways

• Your core job is ensuring what gets built is both valuable and viable, not just executing a backlog.
• Check whether your team is a feature team, delivery team, or empowered product team, since that determines how much real PM work you can do.
• Teams given problems rather than features must invest in discovery to find solutions that work for customers and the business.
• Don't absorb the designer's job; wireframing and user research are full-time skills that need a dedicated owner.
• Start with a self-assessment of your skill gaps and a development plan, ideally built with a manager who can coach you weekly.
• Build a solid foundation of product principles so you can judge the quality of other PM content yourself.

02Key sections

Why the noise is a problem

The author notes that interest in product management is high but so is conflicting advice, leaving newcomers without a coach confused. He sees his role as helping people unlearn misconceptions before learning how strong PMs work.

The core responsibility: value and viability

The PM is accountable for ensuring what gets built is valuable and viable, which is what makes the job hard. The product owner role from Agile is only a small subset of the PM's responsibilities.

Feature teams versus empowered product teams

Companies still organized around feature or delivery teams leave little room for discovery and often reduce PMs to project managers. Real PM work requires an empowered team that is handed problems and is accountable for outcomes, not output.

Product discovery and division of labor

Discovery is the process of finding a solution that is valuable, usable, feasible and viable. Wireframing, prototyping and user research belong to the product designer, and the two roles are full-time jobs each.

Getting up to speed

New PMs should run a skills self-assessment with their manager, build a development plan, and expect about three months of real work with weekly coaching to reach basic competence. Further learning includes training and a curated set of thinkers.

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.