"How to build the best thing you can with what you know today"
summary
Argues prioritization is an art not a formula and recommends selecting frameworks by the data you actually have, using Kano model for time-based feature evolution and user story mapping to align work to jobs‑to‑be‑done; shows a real 0→1 build — a data sync at Pendo that ships a minimal unblocker first then iterates — and a Vimeo case where story mapping prevents onboarding meltdowns at 100x scale. Advises lightweight pilots, shared roadmaps, and explicitly avoid MoSCoW RICE WSJF unless definitions are rigid and organization‑wide.
AI-written summary · about
chapters (18)
- 0:00Introduction and speaker intro
- 1:51Prioritization as art and science
- 3:56Rigor before prioritization
- 6:26Choosing the right frameworks
- 7:07Data types and framework selection
- 9:13Frameworks I regularly use
- 12:43User story mapping in practice
- 14:27Cono model in practice
- 16:13Frameworks I don't recommend
- 18:20Creating effective roadmaps
- 19:01Key takeaways for prioritization
- 20:29Q&A session begins
- 20:50Balancing effort and value
- 21:53RICE framework downsides
- 24:00Cono light model explained
- 25:23Advice for startup product managers
- 27:12When to start development
- 29:00Closing remarks