Why Product Thinking is so Hard (and what you can do about it)
summary
Minimum viable product is widely misunderstood and causes teams to focus on time, cost and scope instead of customer outcomes. The concrete prescription is to name your endpoint and supporting products, map personas and journeys, ship many small features, and measure whether people see try use keep using them. Outcomes typically take weeks to months to appear (about 1–3 months or 2–6 sprints), and feature size or on-time delivery correlates poorly with whether a change becomes “awesome.”
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:33Product Thinking
- 3:17What makes a product great
- 10:35My backyard
- 22:30Where things go wrong
- 25:00You are the product
- 29:12Identify your products
- 34:20Evaluate your products
- 36:32Measure outcomes
- 37:20Continuously reflect
- 40:25Conclusion
related talks
29mReaching Success Through Product Engineering
44mOutcome-based Product Planning
01h 02mMinimal Viable Process - how to find flow in your ways of working
31mNavigating the Platform Revolution: From Bottom-Up Innovation To Product Thinking
22mOptimizing Product Development: Balancing Speed, Quality, and Process
01h 05mTransformed: Moving to the Product Operating Model
12mKeynote - Building Products at Scale
24mForging the path: Product Thinking as the golden thread