By Marty Cagan · svpg.com · LinkedIn
Marty Cagan, drawing on a conversation with venture capitalist Josh Kopelman, argues that business plans are wrong almost as soon as they are written. Competition, technology, and market dynamics constantly shift, and successful companies often pivot, as PayPal and YouTube did. Good VCs expect this and plan for it, while many product companies treat plans and ROI projections as fixed commitments and make changing course costly. Cagan concludes that product portfolio planning should weight the team, the opportunity, and the discovery process more than specific numbers, and that pivoting is the purpose of product discovery rather than a failure of it.
01Key takeaways
- Treat business plans as hypotheses that will change, not as commitments to defend.
- Expect and plan for pivots as new data arrives, since many successful ventures started elsewhere.
- Hold off on writing detailed specifications until discovery has revealed something worth specifying.
- In portfolio planning, weight the team, opportunity, and discovery process more heavily than projected numbers.
- Be explicit about what you know versus what you cannot know, and manage the resulting risk deliberately.
- Recognize that pivoting is central to product discovery and build processes that make course correction cheap.
02Key sections
- The VC perspective on plans
- Kopelman notes that venture capitalists review thousands of business plans and see that all of them become outdated quickly. Successful entrepreneurs expect to pivot as they learn.
- Why product companies resist change
- Product companies often rely on detailed ROI, market projections, and cost estimates for senior investment decisions, and then make pivots painful. Cagan links this rigidity to a lack of innovation.
- Discovery versus requirements specification
- Cagan favors broad product discovery over narrow requirements specs, since more written specification makes teams less open to new ideas. He also distinguishes market discovery from product discovery.
- Implications for portfolio planning
- Because early models cannot predict real demand, feasibility, or cost, planning should focus on acknowledging what can and cannot be known and managing risk intelligently rather than trusting the numbers.
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.