How to facilitate a design sprint that ships a real answer.
Short answer
A design sprint is a 5-day structured process, Map, Sketch, Decide, Prototype, Test, created by Google Ventures. The facilitator owns the clock, not the content. Each day has a defined output: a problem map, individual sketches, a single voted solution, a testable prototype, and real user feedback. The whole thing produces a validated (or invalidated) concept in one week.
The GV Design Sprint (documented in Jake Knapp's Sprint book) is the canonical format. Here is the day-by-day structure a facilitator should execute.
Day 1, Map (Monday). Start with a long-term goal: "In two years, where do we want to be?" Then list sprint questions, the things that could cause failure. Map the customer journey end-to-end on a whiteboard. Bring in 3 to 5 expert interviews (15 to 30 min each) from different departments: engineering, sales, customer support. End the day by picking a target: one customer type and one moment on the map to solve for. The facilitator's job is to keep the group on pace and ensure the Decider (a named decision-maker) has the final say.
Day 2, Sketch (Tuesday). Start with Lightning Demos: each participant shares an inspiring product example (not your own product) in 3 minutes. Then run a 4-step sketch process: notes (20 min), ideas (20 min), crazy 8s (8 minutes, 8 sketches), and a final 3-panel solution sketch. All sketches are done individually and in silence. The facilitator sets every timer and enforces it.
Day 3, Decide (Wednesday). Post all solution sketches on the wall. Run the Art Museum, everyone silently reviews and places dot stickers on interesting parts. Each presenter explains their sketch in 1 minute. The group heatmaps the board and votes; the Decider makes the final call. The facilitator then leads a storyboard session (15 frames) to plan the prototype.
Day 4, Prototype (Thursday). Build a believable facade in 7 hours. Typical tools: Keynote, Figma, a paper mockup, or a Webflow page. The facilitator divides the team into roles: Maker (builds screens), Writer (handles copy), Asset Collector (finds images/icons), Stitcher (assembles), and Interviewer (writes the test script). Nobody builds the real thing, believable is sufficient.
Day 5, Test (Friday). Run 5 structured user interviews, 60 minutes each. The interviewer follows a consistent script. The rest of the team watches in a separate room and takes notes on a board: a 5-column grid, one column per participant. After all 5 interviews, cluster the notes and look for patterns. The facilitator runs a group debrief: What did we learn? Is our sprint question answered?
Facilitator rules: Never share your own opinions on the solution. Never let the conversation run past the timer. If the Decider isn't in the room, the sprint is at risk, reschedule. Keep phones in a box during working sessions. Capture every whiteboard before it gets erased.
After each day, snap the whiteboard with BoardSnap AI and get a clean summary of the day's decisions and open questions, so Day 2 starts with a tight brief, not a memory contest.
Frequently asked
Can you run a design sprint in fewer than 5 days?
Yes. A 4-day sprint combines Monday and Tuesday into a single compressed day. A 1-day sprint (Design Sprint 2.0) is used for smaller, well-understood problems, but you lose the depth of individual sketching and real user testing.
What team size works best for a design sprint?
4 to 7 people. Fewer than 4 and you lose diverse perspective; more than 7 and consensus slows to a crawl. Include one Decider with real authority, without them the sprint often collapses into debate on Day 3.
What if the prototype fails in testing?
That's a win. You learned in 5 days what would have taken 5 months to discover after shipping. Failure data from Day 5 is the most valuable output of the sprint, it directly informs what to try next.
See it work in ten seconds.
BoardSnap is free on the App Store. Snap a board, get a summary and action plan.