By Marty Cagan · svpg.com · LinkedIn
Marty Cagan contrasts the traditional project model, where IT builds specific features by fixed dates, with the product model, where durable teams own business outcomes. He argues projects are slow, costly, and produce little ownership, learning, innovation, or long-term care for the technology, so value is usually lost after launch. Product teams, by contrast, keep monitoring and improving results and can optimize for time-to-money rather than time-to-market, often reaching outcomes faster because they already have context and skills. Cagan acknowledges that fixed dates sometimes matter, but treats them as the exception. The piece matters because many organizations claim to value outcomes while their culture still rewards predictability over results.
01Key takeaways
- Shift team accountability from shipping features to achieving measurable business outcomes.
- Build durable product teams rather than assigning people to projects for a limited duration.
- Fund multiple iterations based on learning instead of a single up-front project attempt.
- Track time-to-money, not just time-to-market, when judging how fast value reaches the business.
- Reserve fixed-date commitments for the rare cases where the date truly matters more than the outcome.
- Watch for organizations that say they value outcomes but still reward predictability over results.
02Key sections
- The problem with the project model
- Large, fixed-date projects demand upfront estimates and funding, and teams rush to ship rather than deliver value. Once shipped, people scatter and no one owns the results or the lessons learned.
- Why projects fail to create lasting value
- Projects rarely get funding for the multiple iterations needed, lack ownership, focus on stakeholder requests instead of new possibilities, and let technical debt accumulate. Accountability for results ends up diffused and blamed on the project team.
- The product model: outcomes over features
- Durable product teams are accountable for business metrics such as churn or growth and keep working to improve them. This requires a cultural shift from shipping features to owning outcomes.
- Time-to-money beats time-to-market
- A standing product team is already productive and knows the problem, data, and technology, so it often reaches a business result faster than a newly staffed project team would ship.
- When dates still matter
- Speed matters and deadlines are sometimes the true priority, but Cagan argues these cases are the exception. The key question is whether the date or the outcome matters more.
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.