Outcome-based Product Planning
summary
Argues that traditional roadmaps are brittle and replaces feature lists with measurable outcome-based planning tied to OKR-like key results, showing how to write hypothesis statements (we believe X will change user behavior) and design minimal experiments or MVPs to test risks. Uses concrete examples: an online learning product for lawyers with specific retention and referral metrics, Rotterdam’s mobile bike-rack experiment, and Amazon’s deployment cadence to justify quarterly commitments and visible discovery work that drives real behavior change.
AI-written summary · about
chapters (15)
- 0:00Start
- 0:58Planning Our Work towards Outcomes
- 1:17Outcome-Based Product Planning
- 3:28Linear Product Planning
- 12:32What an Outcome-Based Product Plan Look like
- 13:31What Will People Be Doing Differently
- 16:23A High Level Outcome Based Product Plan
- 16:33What Can Replace Your Feature Based Road Map
- 17:03Key Results
- 17:55Hypothesis Statements
- 24:06Success Criteria
- 25:27Solution Hypotheses
- 27:46Assess the Risks
- 33:39Challenges
- 37:07Radical Transparency
related talks
32mLearning from industry: Product Management practices for the win
40mStrategy Testing
42mBuilding Powerful Roadmaps
19mThe Why, How & What of an Outcome centric team
49mDesigning Business Outcomes (#noprojects)
29mReaching Success Through Product Engineering
31mRoadmap Revolution: Turn Friction into a Business Accelerator
48mWhy Product Thinking is so Hard (and what you can do about it)