By Marty Cagan · svpg.com · LinkedIn
Marty Cagan argues that weak products are those that fail to meet their objectives or create new revenue and growth for the company. He lists ten root causes, centered on the absence of a real product vision, stakeholder-driven roadmaps, and missing rapid test-and-learn culture. Other causes include weak design, little direct customer expertise, no genuine discovery process, and siloed rather than collaborative teams. He also flags focusing on dates and features over business results, a lack of corporate courage, and weak product leadership. The piece matters because it gives teams a diagnostic checklist for finding where their product practices are breaking down.
01Key takeaways
- Set a genuine product vision and think strategically rather than chasing features one after another.
- Measure success by business results, not by how consistently you ship releases.
- Run rapid test-and-learn cycles to converge quickly on solutions that work.
- Bring engineers and designers into problem framing early so they can shape better solutions.
- Build a real product discovery process instead of converting stakeholder requests straight into builds.
- Get regular face-to-face customer contact so the product team becomes the company's customer expert.
02Key sections
- Product vision and strategy
- Cagan identifies feature chasing without a strategic vision as the biggest source of weak product. He urges teams to think in leaps and iterate in steps.
- Stakeholder influence and learning culture
- Stakeholder-driven roadmaps and the absence of rapid test-and-learn practices keep teams from converging on effective solutions. Product organizations should help stakeholders succeed rather than simply take orders.
- Design and customer understanding
- Weak UX design competency and infrequent face-to-face customer interaction undermine product quality. The product organization should become the company's recognized expert on customers.
- Discovery and collaboration
- Many teams turn feature requests directly into engineering work without discovery, and they bring engineers in too late. Genuine three-way collaboration between product, design, and engineering produces stronger solutions.
- Results, courage, and leadership
- Focusing on release dates instead of business outcomes, fear of taking risks, and weak product leaders all prevent strong products. Cagan notes these causes sit on a spectrum rather than being black and white.
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.