By Marty Cagan · svpg.com · LinkedIn
Marty Cagan revisits his earlier framing of product success as valuable, usable, and feasible, arguing that the single word 'valuable' hid serious business risk and let product managers overweight customer value. He splits product risk into four explicit categories: value, usability, feasibility, and business viability. Business viability covers whether a product fits go-to-market channels, partner and legal constraints, customer acquisition costs, monetization, and brand promise. Each risk is assigned an owner, with the product manager accountable for value and viability. The piece matters because it pushes product teams to surface and tackle business risks early, not just ask whether customers will love the product.
01Key takeaways
- Evaluate every product idea against four distinct risks: value, usability, feasibility, and business viability.
- Do not assume a product customers love will automatically work for the business; check monetization, channels, and cost of acquisition.
- Check constraints from contracts, partners, legal compliance, and brand promise before committing to a solution.
- Assign clear ownership: product managers for value and viability, designers for usability, lead engineers for feasibility.
- Tackle the biggest risks, especially value and business risk, early rather than after building.
- Work on solutions side by side across product, design, and engineering, and measure success by results rather than shipped features.
02Key sections
- From three attributes to four risks
- Cagan explains that the original model's bundling of 'valuable' concealed business risks. He separates value, usability, feasibility, and business viability as distinct risks to be examined.
- What business viability covers
- He lists concrete business concerns such as go-to-market fit, contract and compliance constraints, affordable acquisition, monetization, and brand consistency.
- Who owns each risk
- Product managers own value and viability, designers own usability and the overall experience, and lead engineers own feasibility and delivery.
- Beyond Lean and Agile
- Cagan argues strong teams tackle big risks early, solve problems collaboratively across disciplines, and focus on results rather than features or roadmaps.
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.