// description
A Design Sprint is a five-day structured process for solving critical business questions through design, prototyping, and customer testing. Monday is for mapping the problem and choosing a target. Tuesday is for sketching competing solutions. Wednesday is for deciding on the strongest idea. Thursday is for building a realistic prototype. Friday is for testing the prototype with five target users. The compressed timeframe forces decisions and prevents endless deliberation.
// history
Jake Knapp developed the sprint process while working at Google, where he ran over 100 sprints across products including Gmail, Chrome, and Google X. When he joined Google Ventures as a design partner, he adapted the format for startups. His 2016 book Sprint became a bestseller and the method has since been used by organisations ranging from the United Nations to LEGO.
// example
A digital product creator wondering whether to launch a new course format runs a compressed solo sprint over three days. Day 1: maps the core problem (students are completing modules but not implementing anything) and identifies the target: the gap between watching and doing. Day 2: sketches three different course structures — project-based, accountability-partner, implementation day format. Day 3: creates a rough "implementation day" version and sends it to five existing students as an optional upgrade. Four out of five complete the implementation day and report it as the most valuable part of the course. She builds the full version based on this validated prototype.
// katharyne's take
I run a version of the Design Sprint whenever I'm launching a new course module or digital product format, and the "test with five users" step is non-negotiable. You only need five people — Jakob Nielsen's research shows you find 85% of usability problems with five testers. For course creators, this means: build a rough version of your new format, give it to five students for free in exchange for detailed feedback, and watch what they do (not just what they say). You will find the problems in day one that would have taken months to discover after a full launch.
// creative uses
- Run a three-day solo sprint before launching any new KDP interior format. Day 1: map the buyer's journey from Amazon search to purchase decision and identify the single moment where your product loses potential buyers. Day 2: sketch three different cover or interior approaches that address that moment. Day 3: create mockups of the best one and show them to five people in your target audience for gut-reaction feedback before investing in full production.
- Use the Design Sprint format to test a Midjourney-based digital product line before committing to 50+ assets: generate 20 images representing your concept, build a minimal Etsy listing with mockups and a clear price, and send the link to your email list or a relevant Facebook group before you create the full product. Pre-orders or interest signals are your test result.
- Apply the sprint's "decision on Wednesday" discipline to your own overthinking: if you've been deliberating over a business decision (new niche, new platform, new product format) for more than two weeks, declare a sprint deadline — you will decide by Thursday and act by Friday, regardless of perfect information.
// quick actions
- Identify the one new product or format you've been "thinking about" for more than a month. Set a five-day sprint: by Friday, you will have a rough prototype in the hands of five target customers. Not a finished product — a prototype good enough to generate real feedback. Start today with the map step: write down the problem your product solves in one sentence.
- For your next course module, build a one-page outline (prototype) and share it with five existing students before you record a single video. Ask them: "Does this address your biggest frustration with [topic]?" Their response reshapes the module before you've invested 10 hours of recording and editing.
- Use the sprint's "Crazy 8s" sketching technique for KDP cover design: fold a piece of paper into eight panels and sketch eight completely different cover concepts in eight minutes. No refining — just rapid ideation. The best three concepts go into Midjourney or Canva. Constraints and time pressure produce better initial directions than open-ended exploration.
// prompt ideas
Plan a 3-day solo design sprint for me around this challenge: [describe your product or business challenge]. Give me a specific daily schedule with activities, time blocks, and clear deliverables for each day — ending with a prototype I can test with real users by Friday. Keep it achievable for one person working independently.
I want to run a design sprint to test whether [new product concept] will actually work before I build it fully. Help me design a minimum viable prototype I could create in a day and show to 5 target buyers this week. What exactly should the prototype include, what questions should I ask testers, and what responses would tell me to proceed versus pivot?
The Map stage of a design sprint requires identifying the biggest risk in a product or business decision. Here's what I'm trying to build: [describe your product or course]. What are the 3 riskiest assumptions baked into this plan — the ones that, if wrong, would make the whole thing fail? Prioritise them and tell me how to test the most critical one this week.