A design sprint is a fixed, 4- to 5-day process for answering one high-stakes product question before the team builds the product. A small cross-functional team ends the week by testing a realistic prototype with target users.
Each day has a fixed job, from mapping the problem to testing the prototype. The output is a decision informed by user reactions, with no production code written. It's separate from an Agile development sprint, which is a cycle for shipping code.
Use cases
Sprints work best when the team has a specific decision to make and the right people are involved.
Vague question: A team runs a sprint to "improve onboarding," but the broad goal produces opinions rather than a testable decision.
Missing Decider: The person with authority to make the final call skips the sprint and rejects the direction afterward.
Friendly testers: The team tests with colleagues who already know the product, missing problems that new customers would encounter.
How it's used in practice
Define one testable question. Focus the sprint on a risky decision, such as "Will first-time buyers trust a subscription at checkout?"
Staff the team. Keep it to 7 or fewer people, including a Decider and a neutral facilitator.
Follow the sequence. Map and target (day 1), sketch (day 2), decide and storyboard (day 3), prototype (day 4), test (day 5).
Prototype only what matters. Build the customer-facing screens needed to test the chosen idea rather than a complete product.
🪄
Pro-tip: Write the sprint question as a "Will users…?" sentence before day 1. If it can't be answered through the sprint's user tests, narrow the question.
Challenges & limitations
Calendar cost: Clearing 4 to 5 days for senior people can be difficult, which contributed to shorter sprint formats.
Needs a defined problem: A sprint is designed to answer a focused question, not discover an unknown problem. Broader discovery research may need to happen first.
Limited evidence: A handful of user tests can reveal usability problems and reactions, but cannot establish market demand or validate pricing.
Free resources
GV: The Design Sprint — the official day-by-day guide and videos from Jake Knapp and John Zeratsky
