By Marty Cagan · svpg.com · LinkedIn
Marty Cagan responds to a CTO's question about whether a strong product designer and technical lead still need a product manager, arguing the PM's contribution is often invisible or poorly done. He frames the discussion around empowered product teams, where the PM is an individual contributor and the product owner responsible for the backlog. He argues the backlog only reflects good decisions when the PM is accountable for value and viability. He then outlines four areas of deep knowledge a competent PM must have: customers, data, the business, and the industry. These matter because designers and engineers cannot supply this knowledge, and without it the team is effectively guessing.
01Key takeaways
- Treat the PM as the accountable owner of value and viability, not just the keeper of a backlog.
- Build deep, firsthand knowledge of customers, combining quantitative usage data with qualitative understanding of why they behave as they do.
- Own the analytics: know how the product is used, how sales trend, and how these change over time, rather than delegating it entirely.
- Understand the business model, go-to-market approach, stakeholder needs, and economics, including costs, privacy, and ethics.
- Track the industry's technology and customer expectations so you build for where the market will be tomorrow.
02Key sections
- Why the PM contribution is unclear
- Teams often can't see what a product manager adds, either because the work isn't happening or because its significance isn't understood. The essay sets out to make that contribution explicit.
- Caveats on the empowered team model
- The role differs on feature teams, where it becomes project management. The PM is an individual contributor in a flat structure, and the role may be played by the CEO or a founder at an early-stage startup.
- The backlog and why it's hard
- The PM is the product owner responsible for the backlog, which can look like a simple list of stories. The hard part is deciding what to build, and a backlog built by an ill-equipped person undermines strong design and engineering.
- Four critical areas of knowledge
- PMs need deep knowledge of customers (qualitative and quantitative), data on product usage and sales, the business model and economics, and the industry and its trends. These cannot be delegated to designers or engineers.
- Domain experts as an exception
- In domains like tax software or medical devices, subject matter experts may supplement the PM, but this is rare. Usually the PM must have the necessary domain expertise.
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.