How to cut off development times & get feedback from real users
summary
Shows how a two-week back-to-back sprint replaces months of debate by moving from idea to tested prototype in days: day 3 prototyping, day 4 at least five user interviews. Prototype is built in React (developers in a ~10‑person team) and designers use Figma for clickable mocks. Results: 9.5/10 ease score, 9.3/10 disappointment-if-not-built, and the prototype becomes ~95% the production feature within four months. Fits ahead of Scrum execution sprints to get real user feedback first.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 2:05Challenges
- 3:45Design Sprint
- 5:04Operational Risk Case Study
- 6:05Sprint Overview
- 7:55Idea to Prototype
- 8:39Map
- 9:55Vision
- 11:03Spring Questions
- 11:56Concept Creation
- 13:10Storyboard
- 14:20Prototype
- 16:01User testing
- 17:25User testing results
- 19:46Quiz
- 20:45Biggest benefit
- 22:24How to use design sprints
- 26:13QA session
- 26:46Is it enough
- 28:06Skill sets backgrounds
- 29:31Business case
- 33:07Biggest challenge
- 34:12Support
- 34:28The book
- 37:20Design Spring Boot Camp
- 40:41Figma
related talks
50mLean Design in Practice
43mDesigning the Right Product
24mPanel Talk: Integrating UX for Improved Product Development
26mIdeation and Prototyping: Think Bigger, Fail Quicker
09mAccelerate Innovation
43mFaster feature discovery with Google Design Sprints
25mHow to run a design sprint without a panic attack
36mMixing Lean UX & Agile Development