By Marty Cagan · svpg.com · LinkedIn
Marty Cagan argues that deep experience in a specific product domain is usually less important for product managers than people assume. He recounts two cases where a strong PM was doubted for lacking domain experience, and notes that excessive domain expertise can breed false confidence about speaking for customers. He estimates that a capable PM can get up to speed on a new domain in roughly 1-3 months, while acknowledging that some domains (enterprise, infrastructure, consumer services, hardware) do demand specific know-how in sales channels, requirements gathering, or scale. He concludes that roughly 80% of PM skills transfer across product types, and that the most valuable experience is about the product creation process and self-improvement, not obsolete technical details.
01Key takeaways
- Judge PMs by how fast they learn new domains and technologies, not by their past industry labels.
- Deep domain expertise can cause overconfidence about customer needs, so keep testing assumptions.
- Plan for roughly 1-3 months of aggressive learning before confidently setting strategy in a new domain.
- Learn the domain-specific mechanics that matter for your product, such as sales cycles, distribution, hardware timelines, or community scale.
- Treat most PM skills as transferable; about 80% apply across product types.
- Value experience most for what it taught you about building products, leading teams, and improving yourself.
02Key sections
- Anecdote about a PM hire
- A hiring manager questioned whether a strong PM with enterprise and infrastructure experience could handle consumer work, echoing a similar doubt raised years earlier. Cagan uses this to show that the candidate's adaptability mattered more than his past domain.
- Domain expertise as a trap
- Deep domain experts can overestimate how well they represent their customers and resist revisiting assumptions. Cagan argues this risk makes too much domain expertise potentially dangerous.
- Learning new domains quickly
- Cagan says he typically needs 1-3 months to gain enough understanding to chart product strategy in an unfamiliar domain. Understanding the domain deeply, not superficially, is still essential.
- Domain-specific differences
- Enterprise, infrastructure, consumer services, and hardware products each require particular skills, such as how requirements are gathered, how sales channels work, or how to manage scale and community. These differences matter.
- Technology expertise and what to value
- Technology knowledge changes fast, so the ability to learn new technologies and apply them to problems matters more than current know-how. Interviewers should ask what a candidate learned, how long it took, and how they applied it.
03From the post
“A partnership dedicated to teaching best practices to product teams and product leaders”
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.