💡 What Is a Design Sprint and When to Use One
The Design Sprint is a structured process for 5 days created by Jake Knapp while he was working as a Design Partner at Google Ventures (GV). Described in the book Sprint (2016, with John Zeratsky and Braden Kowitz), the method was tested at more than 150 startups in GV’s portfolio before becoming public. The premise is radical: instead of months of development, you answer a critical business question with a prototype tested by real users in one week.
Knapp designed the Sprint for companies that need shorten the feedback loop between idea and validation. Instead of scheduling meetings for weeks, assembling a dedicated squad for 5 full-time days is enough to go from an open question to real user data. The book describes cases at Slack, Flatiron Health, and Nest — all with critical decisions answered before a single line of code was written.
✓ When to USE the Sprint
- ✓Large, complex, or high-risk problem
- ✓Team stuck in debate without reaching consensus
- ✓Launch of a new product or critical feature
- ✓Need to validate the hypothesis before investing
- ✓Stakeholders with conflicting views
× When NOT to use it
- ×Problem already well defined, solution known
- ×The team can’t get 5 full dedicated days
- ×Decision already made (the Sprint would become theater)
- ×Routine bug or operational issue
- ×No access to real users for day 5
🗺 Day 1 — Map the Challenge and Choose the Target
Monday of the Sprint is dedicated to align the team about the problem to be solved and to choose a specific target. Jake Knapp calls this process "start at the end": before thinking about solutions, the team defines what success would look like in 2-5 years and what risks could prevent it. Without this alignment, the Sprint generates sketches based on different assumptions.
Day 1 Agenda
Long-term goal + Sprint questions
The Facilitator asks the Decider (the mandatory “Decider” role in the Sprint) to articulate the 2-5 year goal. The team generates questions: “What could prevent us from reaching this goal?” These questions become hypotheses to falsify.
Journey map (user flow)
The team creates a simple map (actor + steps + end goal) of the user journey. It is not a detailed diagram—just the main steps. Typically 5-15 steps. Built together on a whiteboard.
Interviews with experts (“Ask the Experts”)
Each team member with specialized knowledge (strategy, technology, user research, sales) shares what they know in 15-20-minute sessions. The team writes insights on sticky notes using the format "How might we..." (HMW).
Choose the target
The Decider chooses a specific moment on the map and a target user. This defines the scope of the Sprint. Without a defined target, the team tries to solve everything at once and solves nothing.
💡 Knapp Tip
The Decider's role is critical. In sprints without a clear decision-maker, the team returns to democratic debate and loses momentum. The Decider doesn't have to be the CEO — it can be anyone with real authority over the decision at hand. Knapp recommends that the Decider participate at least when choosing the target at the end of Day 1.
✏ Day 2 — Sketch solutions (diverge)
Tuesday is the day for individual divergence. Instead of group brainstorming (which tends to be dominated by louder voices), the Sprint uses a process called 4-Step Sketch: each participant works alone to generate and refine ideas. The result is a rich set of independent solutions, without one idea stifling another.
Notes (20 min)
Each person walks around the space, reviews the Day 1 map, interview notes, and any reference materials. They write free-form notes—with no required structure.
Ideas (20 min)
Turns the notes into diagrams, lists, or rough sketches. Nothing needs to look good—the goal is to externalize the thinking, not create art.
Crazy 8s (8 min)
Fold an A4 sheet into 8 sections and draw 8 variations of your most promising idea in 8 minutes. It drives rapid generation of alternatives and breaks perfectionism.
Solution sketch (30–90 min)
Each person creates a detailed sketch in 3 panels (like a basic storyboard). It should be self-explanatory, with no verbal presentation. Include a title and notes for the Day 3 jury.
The fundamental principle of Day 2 is quiet, individual work. Knapp is explicit: group brainstorming favors those who speak the loudest, not those with the best ideas. The individual process ensures that even the team's most introverted member contributes their own solutions. The sketches are anonymous during the Day 3 vote.
💡 Lightning Demos
Before the 4-Step Sketch, the team does “Lightning Demos”: each person presents, in 3 minutes, a product, app, or service (it can be from a completely different field) with an inspiring solution to the problem. It’s not plagiarism—it’s gathering creative raw material. Knapp calls it “remixing existing ideas into something new.”
✅ Day 3 — Decide and build the storyboard
Wednesday is the Sprint's most critical day: the team needs to converge from multiple sketches to a single solution to prototype. Knapp developed a structured voting process that avoids the classic problem of committee decision-making — where the average solution (pleases everyone, delights no one) wins.
Structured Decision Process
The sketches are posted on the wall. Everyone walks around silently, reads them, and places dot stickers on the parts they find most interesting. No discussion—just marking.
The Facilitator identifies areas with lots of stickers (the “heat map”). For each interesting area, there’s a 3-minute discussion — the sketch’s creator remains anonymous at this point.
Each person gets 1 large vote (the "super vote") for the most compelling complete sketch. The Decider gets 3 super votes. The result is a clear hierarchy of preferences.
Once the decision is made, the team creates a storyboard of ~15 panels on the whiteboard. It’s the prototype script—each panel represents a screen or interaction. Day 4 follows this script.
Rumble: when two ideas tie
When two sketches are equally strong and the team can’t rule either out, Knapp recommends the "Rumble": prototype both and test them on Day 5 with different users. It takes more work, but eliminates weeks of debate. The condition is that both prototypes fit within the time available on Day 4.
🔧 Day 4 — Facade Prototype
Thursday is dedicated to building a facade prototype (facade prototype): something realistic enough to prompt genuine reactions from users, but disposable enough to make in a day. Knapp uses the movie-set metaphor — it looks real from the front, but it's just wood in the back. The goal isn't a functional MVP, but a convincing simulation.
App / Software
Figma, Keynote, Marvel. Clickable screens without code. Navigation works; data is simulated (screenshots or fixed text).
Site / Landing Page
Squarespace, Webflow, Carrd. A real page with simulated content. It can include a working form to capture interest.
Physical Product / Service
Basic 3D printing, paper, role-playing ("Wizard of Oz"—a human simulating an automatic system behind the screen).
✓ Do on Day 4
- ✓Split the team: 2 makers, 1 writer, 1 stitcher (puts everything together) + 1 person responsible for internal testing
- ✓Use ready-made templates and libraries (Figma UI kits)
- ✓Simulate real data: plausible names, values, and dates
- ✓Test the prototype internally at the end of the day
× Avoid on Day 4
- ×Writing code—any code is a waste at this point
- ×Visual perfectionism: users test the concept, not the final design
- ×Add features beyond the approved storyboard
- ×Working in isolation—the stitcher needs constant updates
💡 The “Goldilocks” Mindset
Knapp describes the right level of prototype as “Goldilocks quality”: not so rough that users don’t take it seriously, and not so polished that they aren’t honest with their criticism. The perfect Sprint prototype makes users say “this feels real” while still freely pointing out problems.
👥 Day 5 — Test with 5 Users + Common Mistakes
Friday is the day of truth. The team tests the prototype with 5 real users in individual 60-minute interviews. Why 5? Knapp and Zeratsky cite research by Jakob Nielsen (Nielsen Norman Group): with 5 users, you identify approximately 85% of usability problems. Starting with the 6th user, patterns repeat and the marginal return drops sharply. Five interviews fit into one day and provide enough data to make a decision.
Interview Structure (60 min)
The team (except for the interviewer) watches the interviews live from a separate room. Each member records observations on sticky notes using 4 categories: positive quote, negative quote, question, idea. At the end of the day, the team maps the patterns on the whiteboard and reaches a verdict: continue, pivot, or discard.
⚠ Common Mistakes That Destroy the Sprint
Detailed content
Module 2.3 Summary
Next Module:
2.4 - SCAMPER and Brainstorming: structured techniques for generating and expanding ideas