Outcome-based product planning
summary
Argues for planning toward behavior change not features, presents a one-page outcome roadmap with quarterly key results and a backlog of hypotheses, and uses experiments to validate ideas before scaling. Gives concrete metrics: an online learning example targets each user taking three courses per year (a 300% increase), 25% referral growth and 50% staff registration per firm. Recommends lightweight discovery (interviews, prototypes, A/B experiments like movable bike racks) and regular quarterly evidence reviews.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:27Traditional metrics fail customers
- 8:51Limitations of linear planning
- 11:41Outcome-based planning
- 17:56Outcome-based plan template
- 22:33Fog metaphor for agile planning
- 25:39Building outcome-based plan
- 33:47Challenges in adoption
- 39:49Q&A on trust and teams
- 50:57Q&A on communication
related talks
48mOrienting for Outcomes
31mBuilding a Product Users Want
40mDesigned to Learn
18mEffective backlog prioritisation for company happiness
45mHypothesis → Experiment → Verify → Learn... Learning and Practicing Mobius Outcome Delivery to Move Product Development Forward
38mAwesome Products : Inspiration or Iteration?
19mEncounters and Solutions While Facing Outcomes
56mAdaptive Planning Beyond User Stories
