Faster feature discovery with Google Design Sprints
summary
Google Ventures’ Design Sprint compresses discovery into a five-day Sprint that maps Monday to Friday: Monday defines target, Tuesday produces sketches and crazy 8s, Wednesday votes and the decider picks a concept, Thursday builds a clickable prototype (Keynote, Sketch, Keynotopia, role of stitcher and copywriter), Friday runs live user testing streamed to the team. The claim is rapid validation not finished product: teams get a tangible prototype, direct user feedback and shared alignment within one week.
AI-written summary · about
chapters (38)
- 0:00Introduction
- 1:58Product Pilot
- 2:17Product Discovery
- 3:28The Problem
- 5:10Slippery Ball Syndrome
- 6:05Acknowledge
- 7:12Whats needed
- 7:30What are Design Sprints
- 8:16Usercentered design
- 8:39Teamwork
- 9:00Management
- 9:38How does it work
- 9:56Crossfunctional teams
- 10:21Understanding the problem
- 11:53Idea generation
- 13:45Silent review
- 16:24Thursday
- 17:04Friday
- 18:59Outcomes
- 22:07Dual Track Agile
- 23:05Why Sprints
- 23:43Clarity
- 26:40Resources
- 27:18Questions
- 27:30Keeping people refreshed
- 28:13Not with us
- 28:38Do the reset
- 29:17Engage with stakeholders
- 29:49We havent found them
- 30:53Cryptanalysis
- 31:50Athlete collector
- 32:33Its fun
- 33:59What are your stakeholders
- 35:13What is the ROI
- 36:10I was done
- 37:24Alignment
- 40:39Finding users
- 41:32Feedback
related talks
27mGoogle Design Sprint: what it's for and why you should try it
19mGoogle Design Sprint for Devs
25mHow to run a design sprint without a panic attack
27mRunning a Design Sprint on Android
44mFaster from Problem to Prototype with Design Sprints: Are MvPs Dead?
50mLean Design in Practice
43mHow to cut off development times & get feedback from real users
36mMixing Lean UX & Agile Development