# Design Sprint

A time-boxed workshop that aligns a team on a critical challenge, selects a concept, prototypes it, and tests it with target users.

- Type: method
- Domain: Strategy & discovery
- Level: Intermediate
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/design-sprint/>)

## What it means

The design sprint is a structured process developed at Google Ventures for answering important product questions through design, prototyping, and customer testing. The classic format compresses focused work into five days, moving from understanding and sketching to deciding, prototyping, and testing.

## Why it matters

A sprint creates protected time for a cross-functional group to make decisions and confront customer evidence before building a production solution. It can replace weeks of circular discussion with a tangible concept and a clearer view of the risks that need further discovery.

## When to use it

Use it for a consequential, bounded question when relevant decision-makers and a small team can participate, target users can be recruited, and a realistic prototype can test the central uncertainty. Do not use it for routine execution or problems that first require substantial field research.

## How it works

1. Set the challenge, long-term goal, sprint questions, and map of the problem.
2. Invite expert input and choose a focused target in the journey.
3. Sketch competing solutions individually before group evaluation.
4. Select and storyboard one coherent testable concept.
5. Build a realistic facade that tests the critical experience without production engineering.
6. Run structured sessions with relevant users and synthesize patterns into next decisions.

## A practical example

An insurance team must learn whether customers will understand a new claims triage flow. During a sprint it maps the claim journey, sketches alternatives, prototypes a realistic mobile sequence, and tests it with recent claimants. Confusion around urgency labels redirects the project before development.

## Where it breaks

A sprint tests a prototype and selected assumptions, not market demand or the entire service. Five days cannot repair weak strategy, inaccessible recruiting, or missing domain expertise. Group dynamics and decider authority can also bias which concept reaches the test.

## Common mistakes

- Entering with a challenge too broad to prototype meaningfully.
- Treating positive usability sessions as proof of product-market fit.
- Inviting stakeholders only for kickoff and ignoring implementation owners.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/design-sprint/#visualization-design-sprint>)

## Sources

1. [The Design Sprint](<https://www.gv.com/sprint/>) — GV · Official method overview
2. [Design Sprints](<https://design.google/library/design-sprints>) — Google Design · Institutional method guide

## Related topics

- [Design Thinking](<https://wiki.soroush.uk/topic/design-thinking/>)
- [Product Discovery](<https://wiki.soroush.uk/topic/product-discovery/>)
- [User Interviews](<https://wiki.soroush.uk/topic/user-interviews/>)
