Design Sprint Framework
Unverified●30/40Claude Code◐PartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
Cursor◐PartialPlain prose you can paste in — but no Cursor rules file
Codex◐PartialPlain prose you can paste in — but no AGENTS.md
Gemini CLI◐PartialPlain prose you can paste in
Copilot◐PartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add design-sprintWho is stuck, and on what
You keep going in circles on a big decision and nobody can agree, so months pass and nothing gets tested with actual customers. You want a way to get a real answer fast, before you sink money and time into building the wrong thing.
What it gives you
A complete Monday-to-Friday plan — who to invite, what to do each hour, how to build a quick fake version, and how to test it with five real customers by Friday.
When NOT to use it
It will not run the week for you or recruit the customers — it gives you the plan and scripts to run it yourself.
The whole source
Frontmatter — 4 properties
| name | design-sprint |
|---|---|
| description | Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate before we build", "rapid prototype", "test with users", or "should we build this". Also trigger when a team is stuck in endless debate over a high-stakes product decision, or wants to de-risk a costly idea before investing in development. Covers mapping, sketching, deciding, prototyping, and testing across Monday-Friday. For ongoing experimentation and MVPs, see lean-startup. For customer job analysis, see jobs-to-be-done. For non-leading user interviews, see mom-test. |
| license | MIT |
| metadata | author: wondelai version: "1.4.0 |
| 1 | --- |
| 2 | name: design-sprint |
| 3 | description: 'Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate before we build", "rapid prototype", "test with users", or "should we build this". Also trigger when a team is stuck in endless debate over a high-stakes product decision, or wants to de-risk a costly idea before investing in development. Covers mapping, sketching, deciding, prototyping, and testing across Monday-Friday. For ongoing experimentation and MVPs, see lean-startup. For customer job analysis, see jobs-to-be-done. For non-leading user interviews, see mom-test.'B1 — Line is 637 characters — unreadable by eye |
| 4 | license: MIT |
| 5 | metadata: |
| 6 | author: wondelai |
| 7 | version: "1.4.0" |
| 8 | ---A5 — No allowed-tools declared — no way to tell what this skill may touch |
| 9 | |
| 10 | # Design Sprint Framework |
| 11 | |
| 12 | A five-day process for answering critical business questions through design, prototyping, and testing ideas with customers. Developed at Google Ventures and used by Google, Slack, Airbnb, and hundreds of startups. |
| 13 | |
| 14 | ## Core Principle |
| 15 | |
| 16 | **Compress months of debate, design, and testing into one week — and test with real users before writing any production code.** The sprint replaces endless discussion with a fixed Monday-to-Friday spine, hard time-boxes, and a single Decider, so a high-stakes product question gets a real answer in five days instead of five months. |
| 17 | |
| 18 | ## Scoring |
| 19 | |
| 20 | **Goal: 10/10.** Score a sprint plan or execution by awarding 1 point for each item present and correct (10 total). Report the score and the missing items needed to reach 10/10. |
| 21 | |
| 22 | 1. Decider committed for the full week; one Sprint Master facilitating. |
| 23 | 2. Monday produces a target customer and moment (not a vague "test the product"). |
| 24 | 3. Hard time-boxes used (Crazy 8s in 8 min, 10am-5pm days, no open-ended sessions). |
| 25 | 4. Solution sketches done alone and anonymous — no group brainstorming. |
| 26 | 5. Wednesday ends with a single Decider Supervote, not consensus. |
| 27 | 6. Storyboard specified before any prototype is built. |
| 28 | 7. Prototype is a Goldilocks-fidelity facade, testable in 5-15 min, with a trial run done. |
| 29 | 8. Exactly 5 target users recruited via screener (6 scheduled to absorb a no-show). |
| 30 | 9. Friday uses the Five-Act Interview; users interpret the prototype unexplained. |
| 31 | 10. End-of-sprint debrief converts the +/-/~ pattern grid into a decision on next steps. |
| 32 | |
| 33 | A plan missing the Decider, real users, or a same-day prototype caps at 6 — those are the failure modes the sprint exists to prevent. |
| 34 | |
| 35 | ## The 5-Day Sprint Process |
| 36 | |
| 37 | ``` |
| 38 | Monday → Tuesday → Wednesday → Thursday → Friday |
| 39 | Map Sketch Decide Prototype Test |
| 40 | ``` |
| 41 | |
| 42 | **Prerequisites:** a big challenge worth a week's focus; the right team (Decider plus 4-7 people with diverse expertise); five full days (10am-5pm) with no interruptions; a dedicated room with whiteboards. One **Sprint Master** facilitates, keeps time, and manages energy. |
| 43 | |
| 44 | See [references/facilitation.md](references/facilitation.md) when you are the Sprint Master — it has the full facilitation guide, time-boxing tactics, and energy-management moves for keeping a stuck or low-energy room productive. |
| 45 | |
| 46 | ## Monday: Map |
| 47 | |
| 48 | **Goal:** Understand the problem and choose a target for the week. |
| 49 | |
| 50 | ### Morning: Start at the End |
| 51 | |
| 52 | - **Long-term goal:** Write the optimistic answer to "What do we want to be true in 2 years?" — e.g., "Customers use our product daily." |
| 53 | - **Sprint questions:** List obstacles and unknowns as questions on the whiteboard, whole team contributing — e.g., "Will customers trust us with payment info?" |
| 54 | |
| 55 | ### Afternoon: Map the Challenge |
| 56 | |
| 57 | - **Customer journey map:** List the actors (customer types), then draw the journey left to right in 5-15 steps: "Hears about product → Visits site → Signs up → First use → Regular user." |
| 58 | - **Ask the Experts:** Interview teammates with specialized knowledge (CEO, design, engineering, support, sales); capture notes on the whiteboard. |
| 59 | - **How Might We (HMW):** Rephrase problems as opportunities — "Customers don't understand pricing" → "HMW make pricing immediately clear?" One per sticky note; vote and organize the best on the map. |
| 60 | |
| 61 | ### End of Day: Pick a Target |
| 62 | |
| 63 | Choose which customer and moment on the map to focus on — the biggest risk or opportunity (e.g., "the first 10 minutes after signup"). The **Decider** (person with authority) makes the final call. |
| 64 | |
| 65 | **Monday output:** long-term goal, sprint questions, journey map, expert insights, organized HMW notes, target customer and moment. |
| 66 | |
| 67 | See [references/monday.md](references/monday.md) while facilitating Monday — step-by-step exercise scripts, HMW examples, and the target-selection method. |
| 68 | |
| 69 | ## Tuesday: Sketch |
| 70 | |
| 71 | **Goal:** Generate solutions — each person sketches a detailed solution. |
| 72 | |
| 73 | ### Morning: Lightning Demos |
| 74 | |
| 75 | - **Find inspiration:** 3-minute demos of competitors and analogous products ("Here's what I found, here's why it's interesting"); capture good ideas on the whiteboard. Borrow from any industry. |
| 76 | - **Divide or swarm:** Split the map between people if it has multiple parts; otherwise everyone tackles the same critical problem (most sprints swarm). |
| 77 | |
| 78 | ### Afternoon: The Four-Step Sketch |
| 79 | |
| 80 | Everyone sketches alone — **no group brainstorming**. Individual work produces better, more diverse ideas. |
| 81 | |
| 82 | 1. **Notes (20 min):** Silently walk the room reviewing the map, HMWs, and inspiration. |
| 83 | 2. **Ideas (20 min):** Rough doodles, mind maps, stick figures — quantity over quality. |
| 84 | 3. **Crazy 8s (8 min):** Fold paper into 8 panels and sketch 8 variations in 8 minutes — forces you past your first idea. |
| 85 | 4. **Solution Sketch (30-90 min):** A 3-panel storyboard of the customer experience (beginning, middle, end). Make it self-explanatory, give it a catchy title, and keep it **anonymous**. |
| 86 | |
| 87 | **Tuesday output:** one detailed, anonymous, self-explanatory solution sketch per person. |
| 88 | |
| 89 | See [references/tuesday.md](references/tuesday.md) before the Four-Step Sketch — Crazy 8s and solution-sketch templates plus worked examples to show the team. |
| 90 | |
| 91 | ## Wednesday: Decide |
| 92 | |
| 93 | **Goal:** Critique solutions and choose the best one to prototype and test. |
| 94 | |
| 95 | ### Morning: Sticky Decision |
| 96 | |
| 97 | - **Art museum:** Tape sketches to the wall; review silently (no talking) and mark interesting parts with dot stickers. |
| 98 | - **Heat map review:** Discuss each sketch for 3 minutes — the facilitator narrates while the anonymous sketcher stays silent; a scribe captures standout ideas on the whiteboard. |
| 99 | - **Straw poll:** Each person votes for one solution with one sentence of rationale (non-binding). |
| 100 | - **Supervote:** The Decider gets three large dots; their decision wins. |
| 101 | |
| 102 | ### Afternoon: Rumble or All-in-One |
| 103 | |
| 104 | If multiple sketches win, choose: **Rumble** (competing prototypes testing different approaches) or **All-in-One** (combine the best ideas into one prototype — simpler, and what most sprints do). |
| 105 | |
| 106 | - **Storyboard:** Draw a 10-15 panel comic of the test experience: opening scene (how the customer discovers you) → your solution in action → successful outcome. Keep it simple — stick figures, words, arrows — but get specific about the UI. Include just enough detail for Thursday's prototype. |
| 107 | |
| 108 | **Wednesday output:** winning solution(s) and a detailed storyboard ready to prototype. |
| 109 | |
| 110 | See [references/wednesday.md](references/wednesday.md) when running the Sticky Decision and storyboard — facilitation steps for the vote and a panel-by-panel storyboard template. |
| 111 | |
| 112 | ## Thursday: Prototype |
| 113 | |
| 114 | **Goal:** Build a realistic facade in one day — you need something to test on Friday. |
| 115 | |
| 116 | **Mindset:** Fake it; prototype only what you'll test. Aim for Goldilocks fidelity — sketches are too low for honest reactions, working code wastes time. It should look real without working for real (facades, click-throughs, video). |
| 117 | |
| 118 | ### Assign Roles |
| 119 | |
| 120 | | Role | Responsibility | |
| 121 | |------|----------------| |
| 122 | | **Makers** (2+) | Build the prototype pieces (design, assets) | |
| 123 | | **Stitcher** (1) | Combines pieces into the final prototype (Keynote, Figma) | |
| 124 | | **Writer** (1) | All copy: headlines, button labels, descriptions | |
| 125 | | **Collector** (1-2) | Gathers photos, icons, competitor screenshots | |
| 126 | | **Interviewer** (1) | Writes and rehearses Friday's interview script | |
| 127 | | **Sprint Master** | Helps where needed, keeps energy up | |
| 128 | |
| 129 | ### Build the Prototype |
| 130 | |
| 131 | **Tools:** Figma, Keynote, or PowerPoint linked slides for web/apps; video walkthrough or 3D-printed mockup for physical products; role-play video or scripted interaction for services. |
| 132 | |
| 133 | Morning: divide the storyboard into scenes and assign them to makers. Afternoon: stitch together, review against the storyboard, rehearse the full flow, and run a trial with someone outside the sprint team. |
| 134 | |
| 135 | **Prototype checklist:** |
| 136 | - [ ] Follows storyboard exactly |
| 137 | - [ ] Looks real enough to get honest reactions |
| 138 | - [ ] Can walk through in 5-15 minutes |
| 139 | - [ ] Interviewer knows how to present it |
| 140 | - [ ] Trial run completed |
| 141 | |
| 142 | **Thursday output:** realistic prototype, interview script, prepared interview room. |
| 143 | |
| 144 | See [references/thursday.md](references/thursday.md) while building the prototype — tool-by-tool techniques (Keynote/Figma facades, video, mockups) for hitting Goldilocks fidelity in a day. |
| 145 | |
| 146 | ## Friday: Test |
| 147 | |
| 148 | **Goal:** Interview 5 customers; learn what works and what doesn't. |
| 149 | |
| 150 | ### Setup |
| 151 | |
| 152 | Interview room: quiet space, laptop with the prototype, camera recording screen and customer's face. Observation room: live video feed where the whole team watches and takes notes on a whiteboard. One **Interviewer** conducts all five interviews. |
| 153 | |
| 154 | ### The Five-Act Interview |
| 155 | |
| 156 | About 45 minutes per customer (the five acts run ~35 min plus setup and transitions), with 30-minute breaks between to discuss observations and adjust questions. See references/friday.md for the full 9am-5pm schedule. |
| 157 | |
| 158 | | Act | Time | What to Do | |
| 159 | |-----|------|------------| |
| 160 | | **1. Friendly welcome** | 5 min | Greet warmly; explain you're testing the prototype, not them; get recording permission; encourage thinking aloud | |
| 161 | | **2. Context questions** | 5 min | "Tell me about how you currently handle [problem]" — understand mindset and current behavior | |
| 162 | | **3. Introduce prototype** | 5 min | "What's this? What do you think it's for?" Don't explain — let them interpret | |
| 163 | | **4. Tasks and nudges** | 15 min | Open-ended exploration, then storyboard tasks. When stuck: "What would you do next?", "What's going through your mind?" Don't help — watch them struggle | |
| 164 | | **5. Debrief** | 5 min | "What did you think overall?", "Who is this for?", "What worked? What was confusing?" | |
| 165 | |
| 166 | ### Five Is the Magic Number |
| 167 | |
| 168 | Patterns emerge after 3-5 people and returns diminish after 5 — and five interview-plus-break slots fit one day (see references/friday.md). Recruit target customers via a screener survey and offer an incentive ($100-$200 B2B, $50-$100 B2C). |
| 169 | |
| 170 | See [references/recruiting.md](references/recruiting.md) two weeks before the sprint — it has screener-survey questions, recruiting channels, scheduling logistics, and incentive guidance for locking in five on-target users. |
| 171 | |
| 172 | ### Take Notes: Pattern Recognition |
| 173 | |
| 174 | Capture observations in a grid, one column per customer: |
| 175 | |
| 176 | | Customer 1 | Customer 2 | Customer 3 | Customer 4 | Customer 5 | |
| 177 | |------------|------------|------------|------------|------------| |
| 178 | | notes | notes | notes | notes | notes | |
| 179 | |
| 180 | Mark each observation **✓** (positive, success), **✗** (negative, failure), or **~** (neutral/mixed). After all five interviews, count marks per row and look for patterns — did all 5 struggle with the same thing? |
| 181 | |
| 182 | ### End-of-Sprint Debrief |
| 183 | |
| 184 | Organize findings: **✓ what worked** (flows everyone understood, messaging that resonated), **✗ what failed** (confusing terminology, missing steps, wrong assumptions), **~ mixed** (some got it, some didn't). Then decide next steps: |
| 185 | |
| 186 | - **Core concept validated:** build it, or run the next sprint on details |
| 187 | - **Major issues:** pivot, or sprint again on the problems |
| 188 | - **Total failure:** back to the drawing board — you just saved months |
| 189 | |
| 190 | **Friday output:** interview recordings, pattern notes, a clear list of what works and what doesn't, decision on next steps. |
| 191 | |
| 192 | See [references/friday.md](references/friday.md) before interviewing — verbatim Five-Act scripts, note-taking templates, the fuller next-steps decision table, and the common Friday mistakes to avoid. |
| 193 | |
| 194 | ## When to Run a Design Sprint |
| 195 | |
| 196 | **Run when:** the decision is high-stakes, there's no time to build and test normally, the team is stuck in endless debate, multiple solutions compete, it's a new product/feature/major redesign, or you need to de-risk before investing. |
| 197 | |
| 198 | **Don't run when:** the problem and solution are obvious and you just need to execute, the team isn't bought in, or you can't get the Decider for the full week. |
| 199 | |
| 200 | See [references/case-studies.md](references/case-studies.md) for worked sprint walk-throughs (Slack, Blue Bottle Coffee, Savioke and more) when you need a concrete precedent for how a sprint played out in a domain like yours. |
| 201 | |
| 202 | ## Variations |
| 203 | |
| 204 | - **4-Day Sprint:** Day 1 Map + Sketch (compressed), Day 2 Decide, Day 3 Prototype, Day 4 Test. |
| 205 | - **Remote Sprint:** Same schedule with Miro/FigJam whiteboards and Zoom. See [references/remote-sprints.md](references/remote-sprints.md) when the team is distributed — it adapts each exercise to digital whiteboards, sets remote time-boxes, and handles video-based prototype testing. |
| 206 | - **Multi-Sprint:** Sprint 1 chooses direction on a broad problem, Sprint 2 deep-dives the chosen solution, Sprint 3 refines details. |
| 207 | |
| 208 | ## Common Mistakes |
| 209 | |
| 210 | | Mistake | Why It Fails | Fix | |
| 211 | |---------|-------------|------| |
| 212 | | **Skip prototyping** | Nothing to test | Always prototype, even if simple | |
| 213 | | **Over-engineer prototype** | Waste time on details that don't matter | Facade only, not working code | |
| 214 | | **Test with wrong users** | Invalid feedback | Screen for target customers | |
| 215 | | **Explain prototype to users** | Defeats the test; confusion is the data | Run Acts 3-4 as written — they interpret and struggle unaided | |
| 216 | | **No decision maker** | Can't commit to decision | Get Decider for full week or don't sprint | |
| 217 | | **Interruptions** | Breaks focus | Protect the week, no meetings/emails | |
| 218 | |
| 219 | ## Quick Diagnostic |
| 220 | |
| 221 | Audit any sprint plan: |
| 222 | |
| 223 | | Question | If No | Action | |
| 224 | |----------|-------|--------| |
| 225 | | Do we have a Decider for full week? | Sprint will fail | Get commitment or postpone | |
| 226 | | Is the problem important enough? | Waste of time | Only sprint on big challenges | |
| 227 | | Can we prototype in 1 day? | Wrong problem for sprint | Choose more concrete problem | |
| 228 | | Can we recruit 5 target users? | Can't test properly | Start recruiting now (2 weeks ahead) | |
| 229 | | Will team commit to no interruptions? | Won't maintain focus | Get buy-in from leadership | |
| 230 | |
| 231 | ## Further Reading |
| 232 | |
| 233 | For the complete methodology, exercises, and case studies: |
| 234 | |
| 235 | - [*"Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days"*](https://www.amazon.com/Sprint-Solve-Problems-Test-Ideas/dp/150112174X?tag=wondelai00-20) by Jake Knapp, John Zeratsky, Braden Kowitz |
| 236 | |
| 237 | ## About the Author |
| 238 | |
| 239 | **Jake Knapp** created the Design Sprint at Google, where he ran sprints on Gmail, Chrome, and Google X, then refined the process across 100+ startup sprints as a design partner at Google Ventures. The sprint is now used at Google, Slack, Airbnb, LEGO, and thousands of companies worldwide. He is also the author of *Make Time*. |
| 240 |
Reviews
Installed this one?Write the first review and take the Trailblazer badge.
Alternatives
Task Coordination StrategiesDecompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.◐◐◐◐◐●35/40Ebay Seller Tools·····●34/40Tough Decision Advisor: Every Angle ConsideredHand in a decision you're stuck on. Get back a clear breakdown of every angle — the trade-offs, the risks, the blind spot, and a recommended path.●····●32/40DHDNA Profiler — Cognitive Pattern ExtractionPaste any email, proposal, or note someone wrote, and get back a plain-language read on how they think, what drives their decisions, and how they communicate.●····●32/40