By Marty Cagan · svpg.com · LinkedIn
Marty Cagan argues that a product succeeds only when it is solved simultaneously for the customer, the business, and the technology, which he frames as a multiplicative equation: if any one factor is zero, the product fails. He explains that these three concerns are deeply interdependent, so decisions in one area constantly reshape the others. He observes that many founders, designers, and engineers each over-index on just one dimension, and that leaders who don't grasp the full equation lose credibility and influence. For product managers, the takeaway is that real understanding of how the business works is non-negotiable, and that cross-functional collaboration is the core of the job rather than a buzzword.
01Key takeaways
- Evaluate every product idea against customer, business, and technology; weakness in any one can sink the whole.
- Map your work to the usability, feasibility, and viability risks and track which ones are still unaddressed.
- Learn how the business actually makes money, including costs, pricing, and go-to-market, before asking for trust and influence.
- Treat technical and design decisions as business decisions too, since each one constrains the others.
- Coach engineers and designers to think beyond their own discipline and collaborate on discovering solutions.
- Expect executives to judge your business fluency, and close gaps quickly if they exist.
02Key sections
- The core equation
- Cagan recounts being taught that Product equals Customer times Business times Technology, meaning a product must succeed on all three. Any zero collapses the whole.
- Mapping the risks
- The three factors line up with usability, business viability, and feasibility risks, with value risk emerging from all three together.
- Interdependence of the three areas
- Technology choices shape design options, design shapes business outcomes, and business constraints limit both, so the disciplines must collaborate.
- Common blind spots
- Founders fixate on business models, designers on user experience, and engineers sometimes dismiss product and design altogether.
- Why leaders must understand this
- Executives judge product managers on business fluency, and leaders who miss part of the equation lose their seat at key decisions.
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.