Design Sprint
The sprint is a five-day process for answering critical business questions through design, prototyping, and testing ideas with customers.
The Design Sprint is a rigorous, time-boxed five-day framework — Map, Sketch, Decide, Prototype, Test — developed at Google Ventures by Jake Knapp and documented in the 2016 bestseller Sprint. Teams of seven or fewer compress months of ideation, debate, and development into a single structured week, producing a realistic prototype and concrete user feedback before writing a line of production code. It's built for product teams, startup founders, and innovation facilitators who need a validated answer fast — not another round of meetings.
“We're a B2B SaaS company and our trial-to-paid conversion is terrible — about 4%. We think the problem is in onboarding, but we've been debating it…”
Answer your biggest product question with a tested prototype in five days
Jake Knapp's Design Sprint structures problem-solving into five precisely scheduled days, each with named exercises, exact time boxes, and defined roles. Day 1 (Map) establishes the long-term goal, creates a journey map from customer to outcome, and selects a single 'target moment' to focus the sprint. Day 2 (Sketch) uses Lightning Demos for competitive inspiration and Crazy 8s — eight rough sketches in eight minutes — to generate divergent ideas before each person produces a 3-panel Solution Sketch. Day 3 (Decide) runs an Art Museum walk, Heat Map voting with dot stickers, a Speed Critique, and a Supervote by the designated Decider, culminating in a 15-panel Storyboard. Day 4 (Prototype) divides the team into specialized roles — Makers, Stitcher, Writer, Asset Collector, and Interviewer — to build a Goldilocks prototype: realistic enough to elicit genuine user reactions, not so polished it wastes time. Day 5 (Test) runs five structured Five-Act Interviews while the team watches a live feed, takes notes on a positive/negative/questions grid, and debrief patterns. The methodology requires a team of seven or fewer, a Decider with final authority, and a no-device policy during exercises.
Most product teams spend months debating solutions in meetings, building features customers never wanted, and discovering fatal flaws only after launch. The Design Sprint exists because the standard product development loop — argue, decide by seniority, build for six weeks, test, regret — is too slow and too expensive to use as a learning mechanism. Teams make costly decisions based on assumptions because the only way to get real evidence (shipping product) takes far too long to inform the decisions that matter.
In five structured days, your team moves from an open-ended challenge to a tested, realistic prototype with concrete user feedback — compressing what normally takes months of development cycles into a single week of focused, facilitated work.
- A specific product, service, or business challenge to sprint on
- The names and roles of your sprint team (up to 7 people, including the Decider)
- Existing user research, customer pain points, or market context you already have
- Notes or takeaways from prior expert interviews or stakeholder conversations
- A complete day-by-day sprint agenda with time-boxed facilitation instructions for every exercise
- How Might We note clusters, a journey map target, and a written long-term goal statement
- A 15-panel Storyboard ready to hand off to your Day 4 prototype team
- A Five-Act Interview script and a 3-column pattern-recognition grid for Day 5 debriefs
Watch the methodology work.
Three specimens from a single real session: the same situation, unaided and calibrated, the full transcript, and the skill answering live in the channel where the work happens.
“Your team has debated the onboarding flow for three months across fourteen Slack threads and six meetings. The CPO has strong opinions, two engineers think the problem is a missing tooltip, and the designer wants to rebuild the entire flow. You're about to start a six-week development sprint on something none of you have tested with an actual trial user.”
“It's Friday afternoon of sprint week. Five trial users just tested your Goldilocks prototype — a Figma mockup of the new onboarding flow with a sample dataset that bypasses the API key step. Three users completed setup in under four minutes. Two got confused at a different step you hadn't expected. You now have specific, observed evidence — not opinions — to bring into next week's planning meeting, and the Decider already signed off on the direction Wednesday afternoon.”
The same skill, where the work happens.
No new app to learn. The methodology runs over the WhatsApp Business API, so the answer lands as a reply in the thread you’re already in — same rigour, zero context-switch.
What it does, specifically.
Each capability is a distinct move drawn straight from the source methodology — not a generic assistant guessing.
Sprint Agenda Builder
Generates a complete, time-boxed agenda for each of the five sprint days — or a condensed 2- to 4-day version — with specific exercise names, durations, materials needed, and facilitator instructions. Accounts for your team size, available time, and domain (software, physical product, service).
How Might We Synthesizer
Transforms a challenge brief, expert interview transcript, or set of user pain points into a structured list of How Might We (HMW) questions — the affirmative, opportunity-framed prompts that power Day 1's note-taking and clustering exercise. Groups and prioritizes HMWs around the sprint target.
Storyboard Architect
Drafts a 15-panel Storyboard from a selected Solution Sketch description, filling in opening scenes (how the customer finds the product), the core experience panels, and a closing scene — ready to serve as the blueprint for Day 4 prototyping.
Five-Act Interview Scripter
Generates a structured, five-act user test script tailored to the specific prototype being tested: a friendly welcome, warm-up context questions, prototype introduction with task framing, task prompts with probing questions, and a debrief. Includes facilitator reminders on what not to say.
Sprint Pattern Analyst
Takes raw notes from five user tests and organizes them into a 3-column pattern grid (positive observations, negative observations, open questions), then surfaces recurring patterns — the specific signals that indicate which assumptions held and which need revisiting.
Condensed Sprint Adapter
Reconfigures the five-day sprint into a two-, three-, or four-day format (including Design Sprint 2.0), identifying which exercises are non-negotiable, which can be shortened, and which can be asynchronous — without breaking the core Map → Sketch → Decide → Prototype → Test logic.
Graded before it shipped.
Every skill is scored against independent scenarios for methodology fidelity before it goes live — not vibes, a rubric.
Sprint Brief
A one-page alignment document covering the sprint challenge, long-term goal, sprint questions, team roster (including the Decider), and schedule — created before Day 1 to ensure stakeholder buy-in and prevent the Decider from going AWOL mid-sprint.
15-Panel Storyboard
The panel-by-panel visual blueprint for Day 4 prototyping, including opening scenes, core interaction steps, and a closing scene. Each panel maps to a specific screen, moment, or touchpoint the prototype team needs to build.
Five-Act Interview Script
A structured facilitator guide for Day 5 user tests, with scripted language for each act, task prompts matched to the prototype's storyboard, and probing questions designed to surface genuine reactions without leading the participant.
Pattern Recognition Grid
A 3-column synthesis table (positive observations / negative observations / open questions) populated from five user test sessions, with recurring patterns flagged and a 'next steps' recommendation based on what the team learned.
Grounded in the original work.
Every answer traces back to a real source and the practitioner who wrote it — not a secondhand summary. Here is the source of record.
Jake Knapp
Jake Knapp created the Design Sprint methodology while working as a Design Partner at Google Ventures (GV), where he ran sprints with more than 150 companies including Slack, Blue Bottle Coffee, and Nest. He is the co-author of the 2016 global bestseller Sprint (with John Zeratsky and Braden Kowitz) and Make Time (2018). Previously he designed products at Google and Microsoft, and he has since partnered with AJ&Smart to release the condensed Design Sprint 2.0.
Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days
Former Google Ventures Design Partner; Sprint (2016) is required reading at IDEO, Stanford d.school, and major tech product organizations worldwide.
Be first to run it.
Design Sprint is being built right now. Leave your email and we’ll tell you the moment it goes live.