By Marty Cagan · svpg.com · LinkedIn
Marty Cagan argues that product work has two distinct modes: the project model, focused on output from predefined roadmaps, and the product model, focused on outcomes. As delivery costs have collapsed with AI, the bottleneck has shifted from building to discovering a solution worth building. He draws on Jeff Patton's framing of building to learn in discovery versus building to earn in delivery. Each mode has different risks, tests, and tools, and discovery is where a product manager's judgment matters most. Product managers who embrace building and develop product sense are positioned well, while those who act mainly as facilitators or coordinators face growing risk.
01Key takeaways
- Treat discovery as the main source of value, since building is now cheap and fast.
- Build prototypes to test value, usability, feasibility, and viability, not to ship polish.
- Fail in discovery with cheap experiments rather than exposing bad ideas to paying customers.
- Test multiple solution approaches in parallel and refine the most promising ones sequentially.
- Develop product sense to interpret learnings and steer direction, since tooling is the easier part.
- Discovery and delivery are continuous and overlapping, not sequential phases.
02Key sections
- Two models of product work
- The project model delivers prioritized features from a roadmap, while the product model starts from a problem and has empowered teams discover a solution with evidence of outcomes.
- Delivery is no longer the bottleneck
- Falling delivery costs mean producing features is cheap, so the hard part is finding solutions that customers will switch to and that serve the company.
- Building to learn versus building to earn
- Discovery prototypes test value, usability, feasibility, and viability, while delivery builds commercial-grade products that handle scale, reliability, security, and similar demands.
- What has changed in practice
- Modern tools make live-data prototypes cheap and fast, and teams can test several approaches in parallel rather than iterating sequentially on one bet.
- Implications for product managers
- Strong PMs develop product sense and build-to-learn skills, while those who only facilitate or glue teams together face increasing career risk.
03From the post
“We have long argued that there have always been at least two major ways to develop product. The most common way, even today in the age of AI, is the project model, which is all about output. This is where stakeholders or executives come up with a prioritized roadmap of features and projects, then for... The post Build to Learn…”
04Frameworks mentioned
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.