Designing the Right Product
summary
Argues teams must validate assumptions with observable evidence: industry data shows 20% of features get used, so cut scope; run quick experiments like garage-style research at a conference, using paper prototypes and a Bootstrap HTML prototype to iterate from idea to working demo in about 2.5 days, and set explicit signals (the example uses a 70% interest threshold to commit to build). Recommends usability tests, A/B, analytics, shared walls of Post‑its and continuous team involvement.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:52Micheles story
- 1:57Making assumptions
- 6:12Different methodologies
- 11:12Lean UX
- 14:33Nordstrom Case Study
- 22:00User Research
- 28:53Questions to Avoid
- 31:18Research
- 33:27Prototyping
- 37:10Testing
- 38:27Top tips
- 40:28Market testing
related talks
24mPanel Talk: Integrating UX for Improved Product Development
26mIdeation and Prototyping: Think Bigger, Fail Quicker
21mDesign at the speed of startups
42mDesign Thinking for teams who want to create their own products
38mEnough Design
50mLean Design in Practice
46mDesigning for impact
23mHolistic Product Thinking