Design sprint
Definition
A design sprint is a five-day collaborative workshop process developed at Google Ventures (GV) for rapidly solving a critical design or product problem — moving from problem framing to a realistic prototype tested with real users, all within a single week.
Jake Knapp developed the Design Sprint at Google and refined it at Google Ventures, publishing the process in "Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days" (2016). The core promise: compress months of product debate into five days of focused work, and validate a solution with real users before committing engineering time.
The five-day structure:
- Monday (Map): Define the challenge, map the customer journey, identify the most important area to focus on. The sprint team — typically five to seven people — agrees on a long-term goal and a specific sprint question.
- Tuesday (Sketch): Individual ideation. Each person sketches competing solutions independently (crazy eights, solution sketches). No group brainstorming — silence and individual work produce better ideas.
- Wednesday (Decide): Review all sketches, critique, and vote on the best approach. Create a storyboard — the step-by-step blueprint for the prototype.
- Thursday (Prototype): Build a realistic-looking (but non-functional) prototype good enough to fool a real user into believing it's a finished product. Typically done in Figma, Keynote, or assembled from existing interfaces.
- Friday (Test): Five one-on-one user interviews with a real prototype. Watch users attempt the critical tasks. By Friday afternoon, the team knows whether their core idea works.
Why it works: The design sprint avoids the most expensive failure mode in product development: building the wrong thing. Testing a prototype on Friday costs a fraction of building the real thing and finding out six months later that users don't want it.
Design sprints are heavily whiteboard-intensive — the map, sketches, storyboard, and voting all happen on physical surfaces. BoardSnap AI is ideal for capturing the Monday map and Wednesday storyboard before they evolve or get erased.
Examples
- GV-style design sprint helps a startup decide between two competing product directions — prototype testing validates one approach conclusively in five days
- Sprint team of 6 (PM, designer, 2 engineers, CEO, and a customer success lead) runs Monday through Friday
- Thursday prototype built in Figma — users on Friday believe it's a real app, generating authentic reactions
- Sprint question: 'Will enterprise users complete account setup without support?' — answered definitively by Friday's user tests
- Modified two-day sprint for a lower-stakes decision — compresses the five days into focused two-day session with async preparation
Snap a design sprint. Ship its actions.
BoardSnap turns any whiteboard — including this one — into a summary and action plan.