Design Sprint
A time-boxed process to solve a problem and test a prototype fast.
A design sprint is a structured, time-boxed process (classically five days) for going from problem to tested prototype quickly — understand, sketch, decide, prototype, and test. It compresses months of debate into a week of focused progress.
Sprints are ideal for validating a big idea, aligning stakeholders, or breaking a stalemate before committing significant build resources.
Key characteristics
- A time-boxed process — classically five days — to solve a problem and test a solution.
- Created at Google Ventures; phases: understand, sketch, decide, prototype, test.
- Compresses months of debate into a week by prototyping and testing fast.
- Ends with real user feedback on a realistic prototype.
Example
A team unsure about a new onboarding idea runs a sprint: by Friday they've tested a clickable prototype with five users and know whether to build it.
Frequently asked questions
How long is a design sprint?
The classic Google Ventures format is five days, though many teams now run condensed three- or four-day versions. The key is the time-box and the build-test-decide rhythm.
When should you run a design sprint?
When facing a high-stakes, ambiguous problem where alignment is hard and you want validated direction quickly before committing engineering resources.
Need this done, not just defined?
I design and build it — Framer sites, product UI/UX, and more.