By Marty Cagan · svpg.com · LinkedIn
Marty Cagan argues that product teams relying on long, pre-negotiated roadmaps repeatedly fail to deliver business results because of two unavoidable realities. First, at least half of ideas won't work, whether customers aren't excited, the solution is too complicated, or it costs more than expected to build. Second, even good ideas usually need several iterations before they produce the intended value. Strong teams accept these truths and invest in product discovery to separate good ideas from bad quickly, while weaker teams keep pushing through the roadmap. The piece matters because it reframes discovery as the core competency of a product organization.
01Key takeaways
- Expect that roughly half of your ideas will not work for customers, usability, or feasibility reasons.
- Plan for multiple iterations before a good idea reaches its expected business value.
- Replace long, fixed roadmap commitments with rapid prototyping and validation.
- Judge ideas by evidence from customers and engineers, regardless of who proposed them.
- Build discovery as a core team competency, aiming to validate ideas in days rather than months.
02Key sections
- Why roadmaps underdeliver
- Long, stakeholder-negotiated roadmaps keep being used despite seldom producing the business impact organizations hope for. The author attributes this to deeper underlying realities.
- The first inconvenient truth
- Most ideas fail for reasons including weak customer interest, excessive complexity, and build costs beyond what the team can afford.
- The second inconvenient truth
- Even validated, usable, feasible ideas typically need several iterations before they actually deliver expected business value.
- Weak versus strong teams
- Weak teams blame stakeholders and keep adding roadmap iterations, while strong teams quickly separate good ideas from bad and iterate toward effective solutions.
- Product discovery as the core competency
- Prototyping and validating ideas in days rather than months changes both the dynamics and outcomes, making discovery the most important capability of a product organization.
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.