Product Discovery hacks
summary
Advocates doing a short six to eight week upfront discovery to cut wasted delivery time, using an inception with hopes and fears, mapping top 5–7 assumptions into desirability/feasibility/viability, then prioritizing by impact versus existing evidence. Run lightweight user interviews as a team, keep an evidence wall in Miro, build journey maps, story maps and an opportunity solution tree (Teresa Torres). Case notes: a rushed mobile app under-delivers; Monzo’s research-led features succeed. Discovery surfaces bad news early so decisions are evidence driven.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:13What is Pilotworks
- 0:52What is Product Discovery
- 2:44Failure
- 7:22Hacks
- 14:47Assumption Mapping
- 16:43User Research
- 17:50Start Small
- 18:25Team Research
- 19:32Asking Good Questions
- 21:32Evidence Wall
- 22:46Share frequently
- 23:23Map journeys
- 24:15Opportunity mapping
- 26:02Story map
- 27:07Recap
related talks
41mLearning faster
43mDesigning the Right Product
47mExperience Maps—Empowering Designers in Agile Teams to Navigate and Address UX Debt
39mDesign your thinking
24mEvolution of Continuous Product Discovery
26mIdeation and Prototyping: Think Bigger, Fail Quicker
46mStarting Up Research
33mA Scrappy UXer's Tale of Effective Low-Tech, Low-Prep, Quick Turnaround UX Research