What is a design sprint — and when should you actually run one?
Short answer
A design sprint is a 5-day structured process for answering critical business questions through design, prototyping, and testing with real users. Created by Jake Knapp at Google Ventures, it compresses months of back-and-forth into a single week: Map (Monday), Sketch (Tuesday), Decide (Wednesday), Prototype (Thursday), Test (Friday). The output is a validated answer — not a shipped product.
The design sprint was created by Jake Knapp while working at Google, refined at Google Ventures, and documented in the 2016 book Sprint. It has since been adopted by thousands of teams and spawned several variants.
The core insight. Most product decisions take months of meetings, prototypes, and internal debates before anyone talks to a real user. The design sprint inverts this: you test with real users on Day 5, before any code is written. If the idea fails, you know in a week rather than a quarter.
The five days.
- Monday — Map. Define the long-term goal, list sprint questions (things that could cause failure), and map the customer journey. Choose a target: one moment in the journey to focus on.
- Tuesday — Sketch. Individual sketching in silence. Lightning demos from the outside world. Each participant creates a solution sketch — detailed, anonymous, ready to be reviewed.
- Wednesday — Decide. Review all sketches silently (Art Museum). Vote. The Decider makes the final call. Storyboard the chosen solution into a 15-frame prototype script.
- Thursday — Prototype. Build a believable, testable facade in 7 hours. Keynote, Figma, or a paper mock — whatever creates a realistic enough experience to test the core assumption.
- Friday — Test. Five user interviews, 60 minutes each. The team watches from a separate room and takes notes on a 5-column observation board. Debrief at the end: what patterns appeared, is the sprint question answered?
What a design sprint is not. It's not a hackathon (no code). It's not a brainstorming session (sketching is structured and individual, not group). It's not a user research sprint (the prototype is the stimulus, not the product). It's not appropriate for all problems — it works best for well-defined, high-stakes decisions where there are multiple plausible solutions.
Design Sprint 2.0 (AJ&Smart variant). A 4-day compressed version: Days 1–2 combined, Day 3 slightly extended. Faster and now more common than the original 5-day version for teams familiar with the process.
When to run a design sprint. When you're deciding between two plausible directions. When a new product concept needs validation before investment. When a major redesign is being considered. When stakeholders disagree on direction and need external user data to break the deadlock.
When not to. When the problem is purely technical. When the solution is already decided and needs execution, not exploration. When the team can test a live experiment faster than they can run a sprint.
Each day of a design sprint fills multiple whiteboards. Snap them with BoardSnap to keep a clean record of decisions and sketches — so Day 2 starts from the right context, not a memory of the previous day.
Frequently asked
Who created the design sprint?
Jake Knapp created the design sprint process while at Google, refined it during his time at Google Ventures with John Zeratsky and Braden Kowitz, and documented it in the 2016 book *Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days*.
Do you need a designer to run a design sprint?
No — design sprints are cross-functional by design. The Decider is typically a founder or senior leader. Participants include engineers, marketers, and customer-facing roles. Design skills help on Prototype day but aren't required — Keynote or Figma mockups created by non-designers have been used successfully in hundreds of sprints.
How is a design sprint different from a hackathon?
A hackathon produces a working prototype or demo. A design sprint produces a testable facade that is deliberately not real — built fast enough to test assumptions, not built to ship. Design sprints focus on learning from users; hackathons focus on building. Both are time-boxed, but their outputs and goals are different.
See it work in ten seconds.
BoardSnap is free on the App Store. Snap a board — get a summary and action plan.