The Design Sprint is a five-day process for answering critical questions through design, prototyping, and testing with real customers. It compresses months of work into one week by focusing on the riskiest question first.
High-uncertainty problems where you need fast validation before committing to a full build. Especially valuable for new product concepts or major redesigns.
- MONDAY — Map & Target: Understand the problem, map the journey, pick the most important moment
- TUESDAY — Sketch: Generate ideas individually — Crazy 8s then detailed solution sketches
- WEDNESDAY — Decide: Review sketches, vote, create a storyboard for the prototype
- THURSDAY — Prototype: Build a realistic prototype in Figma, Keynote, or paper
- FRIDAY — Test: Interview 5 real users with the prototype. Observe silently. Learn.
- At end of Friday: you know whether the core idea works or needs rethinking
Sprint question: 'Will users trust a fully AI-curated daily playlist with no manual control?' Monday: map the discovery journey. Thursday: build a Figma prototype of 'Daily Drive' — a single auto-playing feed. Friday: test with 5 commuters. Finding: users love it if they can see *why* a song was chosen — the explanation is as important as the song itself.
Please contact the author for more information on these examples at linkedin.com/in/kshitijrege
- Too many participants — 5-7 is optimal; more people slow the process significantly
- Testing with the wrong people — they must be genuine target users, not colleagues
- Treating the prototype as an MVP — it is a learning tool, not a product
- Sprint — Jake Knapp, John Zeratsky & Braden Kowitz