Build Agility with Design Sprints
summary
Design sprints compress discovery into a five-day sprint that maps the problem (Mon), sketches and remixes solutions (Tue), decides and storyboards (Wed), builds a high‑fidelity prototype with tools like InVision/Sketch/Unsplash (Thu) and tests with 5–7 users (Fri). Prototypes take hours, not months; physical mockups are feasible via 3D Hubs prototype and local 3D printing. When paired with rules — continuous customer feedback, six‑week release cycles, daily deploys — the process yields quick, actionable learning and can push viable ideas toward production.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:57Arnold Rothstein
- 3:24Design Sprint
- 5:04First Design Sprint
- 7:43Rothstein Set the Scene
- 9:02Key Assumptions
- 10:40Problem Space Mapping
- 14:11Sketching
- 16:18Storyboarding
- 17:51Prototyping
- 22:37Mapping
- 27:07Testing Day
- 28:20Design Sprint 3
- 35:27Working Solutions
- 38:09Experimentation
- 40:55Boundaries
- 43:37Delivery
related talks
48mBuild Agility with Design Sprints
25mHow to run a design sprint without a panic attack
40mThink Like a Designer
01h 29mSolving real-world problems with a (mini) Design Sprint
50mLean Design in Practice
44mFaster from Problem to Prototype with Design Sprints: Are MvPs Dead?
36mMixing Lean UX & Agile Development
27mRunning a Design Sprint on Android