[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F9WC8682Y3F4KV5KFP8EN6":3,"skill-same:01M6F9WC8682Y3F4KV5KFP8EN6":86},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":31,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":63,"commitSha":64,"skillDirectory":65,"forksCount":66,"repositoryHtmlUrl":67,"repositoryHomepageUrl":68,"ownerHtmlUrl":69,"ownerBlogUrl":6,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M6F9WC8682Y3F4KV5KFP8EN6","design-sprint",null,"Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions \"design sprint\", \"validate in a week\", \"rapid prototype\", \"test with users\", or \"de-risk before building\". Covers mapping, sketching, deciding, prototyping, and testing. For ongoing experimentation, see lean-startup. For customer job analysis, see jobs-to-be-done. Trigger with 'design', 'sprint'.","ComeOnOliver\u002Fskillshub","ComeOnOliver","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43215937?v=4","01M6E5JNFECJAAVFE0W7SMWWD2","Haoran Shu","01M6E5JNNDQS7AJZDYFQ8TPZCK",67,"MIT","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fjeremylongshore\u002Fclaude-code-plugins-plus-skills\u002Fdesign-sprint\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[32,33,34,35,36,5,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"design","design sprint","sprint","lean","testing","prototyping","experimentation","de","mapping","openclaw","done","customer","read","analysis","risk","product","code","run","hello","2026-11-10 10:12:30",false,"---\nname: design-sprint\ndescription: |\n  Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions \"design sprint\", \"validate in a week\", \"rapid prototype\", \"test with users\", or \"de-risk before building\". Covers mapping, sketching, deciding, prototyping, and testing. For ongoing experimentation, see lean-startup. For customer job analysis, see jobs-to-be-done. Trigger with 'design', 'sprint'.\nallowed-tools: Read, Glob, Grep\nlicense: MIT\nauthor: Wondelai \u003Chello@wondelai.com>\nversion: 1.0.1\ncompatible-with: claude-code, codex, openclaw\ntags: [productivity, testing, design-sprint]\n\n---\n# Design Sprint Framework\n\nA 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.\n\n## Core Principle\n\n**Great solutions require both deep work and fast iteration.** The Design Sprint compresses months of debate, design, and testing into a single week, creating focus and urgency that eliminates endless discussion.\n\n**The foundation:** Traditional product development wastes months building the wrong thing. Design Sprints de-risk product decisions by testing with real users before writing production code.\n\n## Scoring\n\n**Goal: 10\u002F10.** When planning or executing a Design Sprint, rate it 0-10 based on adherence to the principles below. A 10\u002F10 means proper structure, time-boxing, prototyping, and user testing; lower scores indicate skipping steps or insufficient testing. Always provide the current score and specific improvements needed to reach 10\u002F10.\n\n## The 5-Day Sprint Process\n\n```\nMonday → Tuesday → Wednesday → Thursday → Friday\n  Map      Sketch     Decide      Prototype    Test\n```\n\n**Prerequisites:**\n- **Big challenge:** Important problem worth a week's focus\n- **Right team:** Decision maker + 4-7 people with diverse expertise\n- **Time commitment:** 5 full days (10am-5pm), no interruptions\n- **Space:** Dedicated room with whiteboards\n\n**Sprint Master:** One person facilitates, keeps time, manages energy.\n\n## Monday: Map\n\n**Goal:** Understand the problem and choose a target for the week.\n\n### Morning: Start at the End\n\n**Exercise: Long-term goal**\n- Write the sprint question: \"What do we want to be true in 2 years?\"\n- Example: \"Customers use our product daily\" or \"We've captured 20% market share\"\n\n**Exercise: Sprint questions**\n- List obstacles and unknowns as questions\n- Example: \"Will customers trust us with payment info?\" or \"Can first-time users figure out the interface?\"\n\n**Format:** Write on whiteboard, entire team contributes\n\n### Afternoon: Map the Challenge\n\n**Exercise: Map the customer journey**\n1. List actors (different types of customers\u002Fusers)\n2. Draw the journey from start to finish (left to right on whiteboard)\n3. Keep it simple: 5-15 steps max\n4. Example: \"Hears about product → Visits site → Signs up → First use → Becomes regular user\"\n\n**Exercise: Ask the Experts**\n- Interview team members with specialized knowledge\n- CEO, designer, engineer, customer support, sales\n- Take detailed notes on whiteboard\n- Capture \"How Might We\" notes (HMW)\n\n**Exercise: How Might We (HMW) notes**\n- Rephrase problems as opportunities\n- \"Customers don't understand pricing\" → HMW make pricing immediately clear?\n- Write each HMW on a sticky note\n- Vote on best HMWs, organize on map\n\n### End of Day: Pick a Target\n\n**Exercise: Choose the target**\n- Which part of the map (customer journey) will you focus on?\n- Where's the biggest risk or opportunity?\n- Example: \"We'll focus on the first 10 minutes after signup\"\n\n**Decider:** The person with authority makes the final call.\n\n**Monday output:**\n- Long-term goal\n- Sprint questions\n- Customer journey map\n- Expert insights\n- HMW notes organized\n- Target customer and moment\n\nSee: [references\u002Fmonday.md](references\u002Fmonday.md) for detailed Monday exercises and facilitation.\n\n## Tuesday: Sketch\n\n**Goal:** Generate solutions. Each person sketches a detailed solution.\n\n### Morning: Lightning Demos\n\n**Exercise: Find inspiration**\n- Look at competitors and analogous products\n- 3-minute demos: \"Here's what I found, here's why it's interesting\"\n- Capture good ideas on whiteboard\n- Don't limit to your industry—borrow from anywhere\n\n**Exercise: Divide or swarm**\n- Divide: If map has multiple parts, different people tackle different sections\n- Swarm: If one critical problem, everyone tackles the same thing\n- Most sprints = swarm\n\n### Afternoon: The Four-Step Sketch\n\n**Goal:** Everyone individually sketches a detailed solution (not as a group!)\n\n**Step 1: Notes (20 minutes)**\n- Walk around room, review map, HMWs, inspiration\n- Take notes silently\n\n**Step 2: Ideas (20 minutes)**\n- Rough doodles, mind maps, stick figures\n- Quantity over quality\n- Still working alone\n\n**Step 3: Crazy 8s (8 minutes)**\n- Fold paper into 8 sections\n- Sketch 8 variations in 8 minutes (1 minute each)\n- Forces you past first idea\n- Can be 8 variations on one idea or 8 different ideas\n\n**Step 4: Solution Sketch (30-90 minutes)**\n- 3-panel storyboard showing customer experience\n- Step 1 → Step 2 → Step 3 (beginning, middle, end)\n- Make it self-explanatory (someone should understand without you explaining)\n- Use text, arrows, simple drawings\n- Give it a catchy title\n- **Anonymous:** Don't put your name on it\n\n**Critical:** No group brainstorming. Individual work produces better, more diverse ideas.\n\n**Tuesday output:**\n- Each person has a detailed solution sketch\n- Sketches are anonymous and self-explanatory\n\nSee: [references\u002Ftuesday.md](references\u002Ftuesday.md) for sketching templates and examples.\n\n## Wednesday: Decide\n\n**Goal:** Critique solutions and choose the best one to prototype and test.\n\n### Morning: Sticky Decision\n\n**Exercise: Art museum**\n- Tape solution sketches to wall\n- Give everyone dot stickers\n- Silently review sketches (no talking!)\n- Put dots next to interesting parts\n\n**Exercise: Heat map review**\n- Discuss each sketch for 3 minutes\n- Facilitator narrates: \"Here they see X, then click Y...\"\n- Sketcher stays silent (don't reveal yourself yet)\n- Team calls out interesting parts\n- Scribe captures standout ideas on whiteboard\n\n**Exercise: Straw poll**\n- Each person votes for one solution (put one large dot)\n- Explain your vote in 1 sentence\n- This is non-binding, just to see preferences\n\n**Decider:** Person with authority gets three large dots (supervote). Their decision wins.\n\n### Afternoon: Rumble or All-in-One\n\n**If multiple winners:**\n- **Rumble:** Competing prototypes (test different approaches)\n- **All-in-One:** Combine best ideas into one prototype\n\n**Most sprints:** All-in-one (simpler to prototype and test)\n\n**Exercise: Storyboard**\n- Draw 10-15 panel storyboard (comic book style)\n- Each panel = one screen or step\n- Opening scene: How customer discovers you\n- Middle: Your solution in action\n- Ending: Successful outcome\n- Include just enough detail for Friday's prototype\n\n**Storyboard rules:**\n- Keep it simple\n- Use stick figures\n- Words and arrows okay\n- Get specific about UI\n- 10-15 panels max\n\n**Wednesday output:**\n- Winning solution(s) chosen\n- Detailed storyboard ready to prototype\n\nSee: [references\u002Fwednesday.md](references\u002Fwednesday.md) for decision exercises and storyboard templates.\n\n## Thursday: Prototype\n\n**Goal:** Build a realistic facade. You need something to test on Friday.\n\n**Prototype mindset:**\n- Fake it\n- Prototype only what you'll test\n- Goldilocks quality: not too high, not too low (realistic enough to get honest reactions)\n- One day only\n\n**Prototype fidelity:**\n- **Too low:** Sketches, wireframes (customers can't react realistically)\n- **Too high:** Working code, pixel-perfect design (wastes time)\n- **Just right:** Looks real, doesn't work real (facades, click-through, video)\n\n### Assign Roles\n\n**Makers** (2+ people):\n- Designer, writer, asset collector (images, icons)\n- Build the prototype\n\n**Stitcher** (1 person):\n- Combines pieces into final prototype\n- Usually in Keynote, Figma, or prototyping tool\n\n**Writer** (1 person):\n- Writes all copy\n- Headlines, button labels, descriptions\n\n**Collector** (1-2 people):\n- Gathers assets (photos, icons, competitor screenshots)\n- Provides raw materials\n\n**Interviewer** (1 person):\n- Writes interview script for Friday\n- Practices interviewing\n\n**Sprint Master:**\n- Helps where needed\n- Keeps energy up\n\n### Build the Prototype\n\n**Tools:**\n- **Web\u002FApp:** Figma, Keynote, PowerPoint (linked slides)\n- **Physical Product:** Video walkthrough, 3D-printed mockup\n- **Service:** Role-play video, scripted interaction\n\n**Thursday morning:**\n- Divide storyboard into scenes\n- Assign scenes to makers\n- Start building\n\n**Thursday afternoon:**\n- Stitch together\n- Review as team (does it match storyboard?)\n- Rehearse for Friday (run through entire flow)\n- Trial run (test with someone not on sprint team)\n\n**Prototype checklist:**\n- [ ] Follows storyboard exactly\n- [ ] Looks real enough to get honest reactions\n- [ ] Can walk through in 5-15 minutes\n- [ ] Interviewer knows how to present it\n- [ ] Trial run completed\n\n**Thursday output:**\n- Realistic prototype ready to test\n- Interview script written\n- Interview room prepared\n\nSee: [references\u002Fthursday.md](references\u002Fthursday.md) for prototyping tools and techniques.\n\n## Friday: Test\n\n**Goal:** Interview 5 customers, learn what works and what doesn't.\n\n### Setup\n\n**Interview room:**\n- Quiet space with table, 2 chairs\n- Laptop with prototype\n- Camera recording screen and customer face\n\n**Observation room:**\n- Separate room with live video feed\n- Team watches together\n- Whiteboard for notes\n\n**Roles:**\n- **Interviewer:** Conducts all 5 interviews\n- **Team:** Watches, takes notes\n\n### The Five-Act Interview\n\n**Act 1: Friendly Welcome (5 min)**\n- Greet warmly\n- Explain you're testing prototype, not them\n- Ask permission to record\n- Encourage thinking aloud\n\n**Act 2: Context Questions (5 min)**\n- Ask about their background\n- Example: \"Tell me about how you currently handle [problem]\"\n- Goal: Understand their mindset and current behavior\n\n**Act 3: Introduce the Prototype (5 min)**\n- Show landing page or entry point\n- \"What's this? What do you think it's for?\"\n- Don't explain—let them interpret\n- Note: Do they get it?\n\n**Act 4: Tasks and Nudges (15 min)**\n- Give open-ended task: \"Go ahead and explore\"\n- Follow with specific tasks from storyboard: \"Try to [complete action]\"\n- Use nudges when stuck: \"What would you do next?\" or \"What's going through your mind?\"\n- Don't help—watch them struggle\n- Encourage thinking aloud\n\n**Act 5: Debrief (5 min)**\n- \"What did you think overall?\"\n- \"Who is this for?\"\n- \"What worked? What was confusing?\"\n- Ask about specific parts you're uncertain about\n\n**Interview length:** ~30 minutes per customer\n\n**Between interviews:**\n- 30-minute break\n- Team discusses observations\n- Update questions if needed\n\n### Five Is the Magic Number\n\n**Why 5 customers?**\n- Patterns emerge after 3-5 people\n- Diminishing returns after 5\n- Doable in one day (5 × 1 hour = 5 hours with breaks)\n\n**Who to recruit:**\n- Target customers (match your personas)\n- Screener survey to qualify\n- Incentive ($100-$200 for B2B, $50-$100 for B2C)\n- Schedule 6 (expect 1 no-show)\n\n### Take Notes: Pattern Recognition\n\n**While watching interviews, team captures:**\n\n| Column 1 | Column 2 | Column 3 | Column 4 | Column 5 |\n|----------|----------|----------|----------|----------|\n| Customer 1 notes | Customer 2 notes | Customer 3 notes | Customer 4 notes | Customer 5 notes |\n\n**Mark with ✓, ✗, or ~:**\n- ✓ Positive reaction, success\n- ✗ Negative reaction, failure\n- ~ Neutral or mixed\n\n**After all 5 interviews:**\n- Look for patterns (did all 5 struggle with the same thing?)\n- Count ✓ ✗ ~ per row\n- Identify what worked and what failed\n\n### End-of-Sprint Debrief\n\n**Organize findings:**\n\n**✓ What worked:**\n- Features\u002Fflows that all customers understood\n- Messaging that resonated\n- Design that felt intuitive\n\n**✗ What failed:**\n- Confusing terminology\n- Missing steps\n- Wrong assumptions\n\n**~ Mixed results:**\n- Some got it, some didn't\n- Unclear if it matters\n\n**Next steps:**\n- **If core concept validated:** Build it (or next sprint on details)\n- **If major issues:** Pivot or next sprint to solve problems\n- **If totally failed:** Back to drawing board (but you saved months!)\n\n**Friday output:**\n- Interview videos\n- Pattern notes\n- Clear list of what works, what doesn't\n- Decision on next steps\n\nSee: [references\u002Ffriday.md](references\u002Ffriday.md) for interview scripts and note-taking templates.\n\n## When to Run a Design Sprint\n\n**Run a sprint when:**\n- High-stakes decision\n- Not enough time to build and test normally\n- Team is stuck in endless debate\n- Multiple solutions possible\n- New product, feature, or major redesign\n- Need to de-risk before investing\n\n**Don't run a sprint when:**\n- Problem is clear and solution is obvious\n- You just need to execute\n- Team isn't bought in\n- Can't get decision maker for full week\n\n## Variations\n\n**4-Day Sprint:**\n- Day 1: Map + Sketch (compressed)\n- Day 2: Decide\n- Day 3: Prototype\n- Day 4: Test\n\n**Remote Sprint:**\n- Use Miro\u002FFigJam for whiteboarding\n- Zoom for meetings\n- Same schedule, digital tools\n\n**Multi-Sprint:**\n- Sprint 1: Broad problem, choose direction\n- Sprint 2: Deep dive on chosen solution\n- Sprint 3: Refine details\n\n## Common Mistakes\n\n| Mistake | Why It Fails | Fix |\n|---------|-------------|------|\n| **Skip prototyping** | Nothing to test | Always prototype, even if simple |\n| **Over-engineer prototype** | Waste time on details that don't matter | Facade only, not working code |\n| **Test with wrong users** | Invalid feedback | Screen for target customers |\n| **Explain prototype to users** | Defeats the test | Let them struggle, observe confusion |\n| **No decision maker** | Can't commit to decision | Get Decider for full week or don't sprint |\n| **Interruptions** | Breaks focus | Protect the week, no meetings\u002Femails |\n\n## Quick Diagnostic\n\nAudit any sprint plan:\n\n| Question | If No | Action |\n|----------|-------|--------|\n| Do we have a Decider for full week? | Sprint will fail | Get commitment or postpone |\n| Is the problem important enough? | Waste of time | Only sprint on big challenges |\n| Can we prototype in 1 day? | Wrong problem for sprint | Choose more concrete problem |\n| Can we recruit 5 target users? | Can't test properly | Start recruiting now (2 weeks ahead) |\n| Will team commit to no interruptions? | Won't maintain focus | Get buy-in from leadership |\n\n## Overview\n\nA five-day process for answering critical business questions through design, prototyping, and testing with real customers, developed at Google Ventures.\n\n## Prerequisites\n\n- A clearly defined challenge worth a week of focused effort\n- A decision maker plus 4-7 team members committed for the full 5 days\n- Dedicated room with whiteboards and a way to recruit 5 target customers for Friday testing\n\n## Instructions\n\n1. Follow the 5-day structure: Map (Monday), Sketch (Tuesday), Decide (Wednesday), Prototype (Thursday), Test (Friday)\n2. Use the Quick Diagnostic table to verify readiness before starting\n3. Refer to the day-specific reference files for detailed exercises and facilitation guides\n\n## Output\n\n- **Monday**: Long-term goal, sprint questions, customer journey map, target selection\n- **Wednesday**: Winning solution chosen, detailed storyboard ready to prototype\n- **Friday**: Interview recordings, pattern notes, validated\u002Finvalidated hypotheses, next steps decision\n\n## Error Handling\n\n| Error | Cause | Resolution |\n|-------|-------|------------|\n| No decision maker available | Key stakeholder absent | Postpone sprint until Decider can commit the full week |\n| Cannot recruit 5 users | Insufficient lead time or wrong audience | Start recruiting 2 weeks ahead; broaden screener criteria |\n| Prototype too complex for one day | Storyboard scope too large | Cut to the single riskiest assumption and prototype only that flow |\n\n## Examples\n\n- **New product validation**: A SaaS startup runs a sprint to test onboarding flow with 5 target users before writing production code.\n- **Feature prioritization**: A product team with 3 competing feature proposals uses Wednesday's decision process to choose one, prototypes Thursday, and tests Friday.\n\n## Resources\n\n- [references\u002Fmonday.md](references\u002Fmonday.md) through [references\u002Ffriday.md](references\u002Ffriday.md) — daily exercises and facilitation\n- [references\u002Fcase-studies.md](references\u002Fcase-studies.md) — Slack, Blue Bottle Coffee, Savioke, and more\n- [references\u002Fremote-sprints.md](references\u002Fremote-sprints.md) — adapting sprints for distributed teams\n- [*\"Sprint\"*](https:\u002F\u002Fwww.amazon.com\u002FSprint-Solve-Problems-Test-Ideas\u002Fdp\u002F150112174X?tag=wondelai00-20) by Jake Knapp — the complete methodology\n\n\n","# Design Sprint Framework\n\nA 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.\n\n## Core Principle\n\n**Great solutions require both deep work and fast iteration.** The Design Sprint compresses months of debate, design, and testing into a single week, creating focus and urgency that eliminates endless discussion.\n\n**The foundation:** Traditional product development wastes months building the wrong thing. Design Sprints de-risk product decisions by testing with real users before writing production code.\n\n## Scoring\n\n**Goal: 10\u002F10.** When planning or executing a Design Sprint, rate it 0-10 based on adherence to the principles below. A 10\u002F10 means proper structure, time-boxing, prototyping, and user testing; lower scores indicate skipping steps or insufficient testing. Always provide the current score and specific improvements needed to reach 10\u002F10.\n\n## The 5-Day Sprint Process\n\n```\nMonday → Tuesday → Wednesday → Thursday → Friday\n  Map      Sketch     Decide      Prototype    Test\n```\n\n**Prerequisites:**\n- **Big challenge:** Important problem worth a week's focus\n- **Right team:** Decision maker + 4-7 people with diverse expertise\n- **Time commitment:** 5 full days (10am-5pm), no interruptions\n- **Space:** Dedicated room with whiteboards\n\n**Sprint Master:** One person facilitates, keeps time, manages energy.\n\n## Monday: Map\n\n**Goal:** Understand the problem and choose a target for the week.\n\n### Morning: Start at the End\n\n**Exercise: Long-term goal**\n- Write the sprint question: \"What do we want to be true in 2 years?\"\n- Example: \"Customers use our product daily\" or \"We've captured 20% market share\"\n\n**Exercise: Sprint questions**\n- List obstacles and unknowns as questions\n- Example: \"Will customers trust us with payment info?\" or \"Can first-time users figure out the interface?\"\n\n**Format:** Write on whiteboard, entire team contributes\n\n### Afternoon: Map the Challenge\n\n**Exercise: Map the customer journey**\n1. List actors (different types of customers\u002Fusers)\n2. Draw the journey from start to finish (left to right on whiteboard)\n3. Keep it simple: 5-15 steps max\n4. Example: \"Hears about product → Visits site → Signs up → First use → Becomes regular user\"\n\n**Exercise: Ask the Experts**\n- Interview team members with specialized knowledge\n- CEO, designer, engineer, customer support, sales\n- Take detailed notes on whiteboard\n- Capture \"How Might We\" notes (HMW)\n\n**Exercise: How Might We (HMW) notes**\n- Rephrase problems as opportunities\n- \"Customers don't understand pricing\" → HMW make pricing immediately clear?\n- Write each HMW on a sticky note\n- Vote on best HMWs, organize on map\n\n### End of Day: Pick a Target\n\n**Exercise: Choose the target**\n- Which part of the map (customer journey) will you focus on?\n- Where's the biggest risk or opportunity?\n- Example: \"We'll focus on the first 10 minutes after signup\"\n\n**Decider:** The person with authority makes the final call.\n\n**Monday output:**\n- Long-term goal\n- Sprint questions\n- Customer journey map\n- Expert insights\n- HMW notes organized\n- Target customer and moment\n\nSee: [references\u002Fmonday.md](references\u002Fmonday.md) for detailed Monday exercises and facilitation.\n\n## Tuesday: Sketch\n\n**Goal:** Generate solutions. Each person sketches a detailed solution.\n\n### Morning: Lightning Demos\n\n**Exercise: Find inspiration**\n- Look at competitors and analogous products\n- 3-minute demos: \"Here's what I found, here's why it's interesting\"\n- Capture good ideas on whiteboard\n- Don't limit to your industry—borrow from anywhere\n\n**Exercise: Divide or swarm**\n- Divide: If map has multiple parts, different people tackle different sections\n- Swarm: If one critical problem, everyone tackles the same thing\n- Most sprints = swarm\n\n### Afternoon: The Four-Step Sketch\n\n**Goal:** Everyone individually sketches a detailed solution (not as a group!)\n\n**Step 1: Notes (20 minutes)**\n- Walk around room, review map, HMWs, inspiration\n- Take notes silently\n\n**Step 2: Ideas (20 minutes)**\n- Rough doodles, mind maps, stick figures\n- Quantity over quality\n- Still working alone\n\n**Step 3: Crazy 8s (8 minutes)**\n- Fold paper into 8 sections\n- Sketch 8 variations in 8 minutes (1 minute each)\n- Forces you past first idea\n- Can be 8 variations on one idea or 8 different ideas\n\n**Step 4: Solution Sketch (30-90 minutes)**\n- 3-panel storyboard showing customer experience\n- Step 1 → Step 2 → Step 3 (beginning, middle, end)\n- Make it self-explanatory (someone should understand without you explaining)\n- Use text, arrows, simple drawings\n- Give it a catchy title\n- **Anonymous:** Don't put your name on it\n\n**Critical:** No group brainstorming. Individual work produces better, more diverse ideas.\n\n**Tuesday output:**\n- Each person has a detailed solution sketch\n- Sketches are anonymous and self-explanatory\n\nSee: [references\u002Ftuesday.md](references\u002Ftuesday.md) for sketching templates and examples.\n\n## Wednesday: Decide\n\n**Goal:** Critique solutions and choose the best one to prototype and test.\n\n### Morning: Sticky Decision\n\n**Exercise: Art museum**\n- Tape solution sketches to wall\n- Give everyone dot stickers\n- Silently review sketches (no talking!)\n- Put dots next to interesting parts\n\n**Exercise: Heat map review**\n- Discuss each sketch for 3 minutes\n- Facilitator narrates: \"Here they see X, then click Y...\"\n- Sketcher stays silent (don't reveal yourself yet)\n- Team calls out interesting parts\n- Scribe captures standout ideas on whiteboard\n\n**Exercise: Straw poll**\n- Each person votes for one solution (put one large dot)\n- Explain your vote in 1 sentence\n- This is non-binding, just to see preferences\n\n**Decider:** Person with authority gets three large dots (supervote). Their decision wins.\n\n### Afternoon: Rumble or All-in-One\n\n**If multiple winners:**\n- **Rumble:** Competing prototypes (test different approaches)\n- **All-in-One:** Combine best ideas into one prototype\n\n**Most sprints:** All-in-one (simpler to prototype and test)\n\n**Exercise: Storyboard**\n- Draw 10-15 panel storyboard (comic book style)\n- Each panel = one screen or step\n- Opening scene: How customer discovers you\n- Middle: Your solution in action\n- Ending: Successful outcome\n- Include just enough detail for Friday's prototype\n\n**Storyboard rules:**\n- Keep it simple\n- Use stick figures\n- Words and arrows okay\n- Get specific about UI\n- 10-15 panels max\n\n**Wednesday output:**\n- Winning solution(s) chosen\n- Detailed storyboard ready to prototype\n\nSee: [references\u002Fwednesday.md](references\u002Fwednesday.md) for decision exercises and storyboard templates.\n\n## Thursday: Prototype\n\n**Goal:** Build a realistic facade. You need something to test on Friday.\n\n**Prototype mindset:**\n- Fake it\n- Prototype only what you'll test\n- Goldilocks quality: not too high, not too low (realistic enough to get honest reactions)\n- One day only\n\n**Prototype fidelity:**\n- **Too low:** Sketches, wireframes (customers can't react realistically)\n- **Too high:** Working code, pixel-perfect design (wastes time)\n- **Just right:** Looks real, doesn't work real (facades, click-through, video)\n\n### Assign Roles\n\n**Makers** (2+ people):\n- Designer, writer, asset collector (images, icons)\n- Build the prototype\n\n**Stitcher** (1 person):\n- Combines pieces into final prototype\n- Usually in Keynote, Figma, or prototyping tool\n\n**Writer** (1 person):\n- Writes all copy\n- Headlines, button labels, descriptions\n\n**Collector** (1-2 people):\n- Gathers assets (photos, icons, competitor screenshots)\n- Provides raw materials\n\n**Interviewer** (1 person):\n- Writes interview script for Friday\n- Practices interviewing\n\n**Sprint Master:**\n- Helps where needed\n- Keeps energy up\n\n### Build the Prototype\n\n**Tools:**\n- **Web\u002FApp:** Figma, Keynote, PowerPoint (linked slides)\n- **Physical Product:** Video walkthrough, 3D-printed mockup\n- **Service:** Role-play video, scripted interaction\n\n**Thursday morning:**\n- Divide storyboard into scenes\n- Assign scenes to makers\n- Start building\n\n**Thursday afternoon:**\n- Stitch together\n- Review as team (does it match storyboard?)\n- Rehearse for Friday (run through entire flow)\n- Trial run (test with someone not on sprint team)\n\n**Prototype checklist:**\n- [ ] Follows storyboard exactly\n- [ ] Looks real enough to get honest reactions\n- [ ] Can walk through in 5-15 minutes\n- [ ] Interviewer knows how to present it\n- [ ] Trial run completed\n\n**Thursday output:**\n- Realistic prototype ready to test\n- Interview script written\n- Interview room prepared\n\nSee: [references\u002Fthursday.md](references\u002Fthursday.md) for prototyping tools and techniques.\n\n## Friday: Test\n\n**Goal:** Interview 5 customers, learn what works and what doesn't.\n\n### Setup\n\n**Interview room:**\n- Quiet space with table, 2 chairs\n- Laptop with prototype\n- Camera recording screen and customer face\n\n**Observation room:**\n- Separate room with live video feed\n- Team watches together\n- Whiteboard for notes\n\n**Roles:**\n- **Interviewer:** Conducts all 5 interviews\n- **Team:** Watches, takes notes\n\n### The Five-Act Interview\n\n**Act 1: Friendly Welcome (5 min)**\n- Greet warmly\n- Explain you're testing prototype, not them\n- Ask permission to record\n- Encourage thinking aloud\n\n**Act 2: Context Questions (5 min)**\n- Ask about their background\n- Example: \"Tell me about how you currently handle [problem]\"\n- Goal: Understand their mindset and current behavior\n\n**Act 3: Introduce the Prototype (5 min)**\n- Show landing page or entry point\n- \"What's this? What do you think it's for?\"\n- Don't explain—let them interpret\n- Note: Do they get it?\n\n**Act 4: Tasks and Nudges (15 min)**\n- Give open-ended task: \"Go ahead and explore\"\n- Follow with specific tasks from storyboard: \"Try to [complete action]\"\n- Use nudges when stuck: \"What would you do next?\" or \"What's going through your mind?\"\n- Don't help—watch them struggle\n- Encourage thinking aloud\n\n**Act 5: Debrief (5 min)**\n- \"What did you think overall?\"\n- \"Who is this for?\"\n- \"What worked? What was confusing?\"\n- Ask about specific parts you're uncertain about\n\n**Interview length:** ~30 minutes per customer\n\n**Between interviews:**\n- 30-minute break\n- Team discusses observations\n- Update questions if needed\n\n### Five Is the Magic Number\n\n**Why 5 customers?**\n- Patterns emerge after 3-5 people\n- Diminishing returns after 5\n- Doable in one day (5 × 1 hour = 5 hours with breaks)\n\n**Who to recruit:**\n- Target customers (match your personas)\n- Screener survey to qualify\n- Incentive ($100-$200 for B2B, $50-$100 for B2C)\n- Schedule 6 (expect 1 no-show)\n\n### Take Notes: Pattern Recognition\n\n**While watching interviews, team captures:**\n\n| Column 1 | Column 2 | Column 3 | Column 4 | Column 5 |\n|----------|----------|----------|----------|----------|\n| Customer 1 notes | Customer 2 notes | Customer 3 notes | Customer 4 notes | Customer 5 notes |\n\n**Mark with ✓, ✗, or ~:**\n- ✓ Positive reaction, success\n- ✗ Negative reaction, failure\n- ~ Neutral or mixed\n\n**After all 5 interviews:**\n- Look for patterns (did all 5 struggle with the same thing?)\n- Count ✓ ✗ ~ per row\n- Identify what worked and what failed\n\n### End-of-Sprint Debrief\n\n**Organize findings:**\n\n**✓ What worked:**\n- Features\u002Fflows that all customers understood\n- Messaging that resonated\n- Design that felt intuitive\n\n**✗ What failed:**\n- Confusing terminology\n- Missing steps\n- Wrong assumptions\n\n**~ Mixed results:**\n- Some got it, some didn't\n- Unclear if it matters\n\n**Next steps:**\n- **If core concept validated:** Build it (or next sprint on details)\n- **If major issues:** Pivot or next sprint to solve problems\n- **If totally failed:** Back to drawing board (but you saved months!)\n\n**Friday output:**\n- Interview videos\n- Pattern notes\n- Clear list of what works, what doesn't\n- Decision on next steps\n\nSee: [references\u002Ffriday.md](references\u002Ffriday.md) for interview scripts and note-taking templates.\n\n## When to Run a Design Sprint\n\n**Run a sprint when:**\n- High-stakes decision\n- Not enough time to build and test normally\n- Team is stuck in endless debate\n- Multiple solutions possible\n- New product, feature, or major redesign\n- Need to de-risk before investing\n\n**Don't run a sprint when:**\n- Problem is clear and solution is obvious\n- You just need to execute\n- Team isn't bought in\n- Can't get decision maker for full week\n\n## Variations\n\n**4-Day Sprint:**\n- Day 1: Map + Sketch (compressed)\n- Day 2: Decide\n- Day 3: Prototype\n- Day 4: Test\n\n**Remote Sprint:**\n- Use Miro\u002FFigJam for whiteboarding\n- Zoom for meetings\n- Same schedule, digital tools\n\n**Multi-Sprint:**\n- Sprint 1: Broad problem, choose direction\n- Sprint 2: Deep dive on chosen solution\n- Sprint 3: Refine details\n\n## Common Mistakes\n\n| Mistake | Why It Fails | Fix |\n|---------|-------------|------|\n| **Skip prototyping** | Nothing to test | Always prototype, even if simple |\n| **Over-engineer prototype** | Waste time on details that don't matter | Facade only, not working code |\n| **Test with wrong users** | Invalid feedback | Screen for target customers |\n| **Explain prototype to users** | Defeats the test | Let them struggle, observe confusion |\n| **No decision maker** | Can't commit to decision | Get Decider for full week or don't sprint |\n| **Interruptions** | Breaks focus | Protect the week, no meetings\u002Femails |\n\n## Quick Diagnostic\n\nAudit any sprint plan:\n\n| Question | If No | Action |\n|----------|-------|--------|\n| Do we have a Decider for full week? | Sprint will fail | Get commitment or postpone |\n| Is the problem important enough? | Waste of time | Only sprint on big challenges |\n| Can we prototype in 1 day? | Wrong problem for sprint | Choose more concrete problem |\n| Can we recruit 5 target users? | Can't test properly | Start recruiting now (2 weeks ahead) |\n| Will team commit to no interruptions? | Won't maintain focus | Get buy-in from leadership |\n\n## Overview\n\nA five-day process for answering critical business questions through design, prototyping, and testing with real customers, developed at Google Ventures.\n\n## Prerequisites\n\n- A clearly defined challenge worth a week of focused effort\n- A decision maker plus 4-7 team members committed for the full 5 days\n- Dedicated room with whiteboards and a way to recruit 5 target customers for Friday testing\n\n## Instructions\n\n1. Follow the 5-day structure: Map (Monday), Sketch (Tuesday), Decide (Wednesday), Prototype (Thursday), Test (Friday)\n2. Use the Quick Diagnostic table to verify readiness before starting\n3. Refer to the day-specific reference files for detailed exercises and facilitation guides\n\n## Output\n\n- **Monday**: Long-term goal, sprint questions, customer journey map, target selection\n- **Wednesday**: Winning solution chosen, detailed storyboard ready to prototype\n- **Friday**: Interview recordings, pattern notes, validated\u002Finvalidated hypotheses, next steps decision\n\n## Error Handling\n\n| Error | Cause | Resolution |\n|-------|-------|------------|\n| No decision maker available | Key stakeholder absent | Postpone sprint until Decider can commit the full week |\n| Cannot recruit 5 users | Insufficient lead time or wrong audience | Start recruiting 2 weeks ahead; broaden screener criteria |\n| Prototype too complex for one day | Storyboard scope too large | Cut to the single riskiest assumption and prototype only that flow |\n\n## Examples\n\n- **New product validation**: A SaaS startup runs a sprint to test onboarding flow with 5 target users before writing production code.\n- **Feature prioritization**: A product team with 3 competing feature proposals uses Wednesday's decision process to choose one, prototypes Thursday, and tests Friday.\n\n## Resources\n\n- [references\u002Fmonday.md](references\u002Fmonday.md) through [references\u002Ffriday.md](references\u002Ffriday.md) — daily exercises and facilitation\n- [references\u002Fcase-studies.md](references\u002Fcase-studies.md) — Slack, Blue Bottle Coffee, Savioke, and more\n- [references\u002Fremote-sprints.md](references\u002Fremote-sprints.md) — adapting sprints for distributed teams\n- [*\"Sprint\"*](https:\u002F\u002Fwww.amazon.com\u002FSprint-Solve-Problems-Test-Ideas\u002Fdp\u002F150112174X?tag=wondelai00-20) by Jake Knapp — the complete methodology\n\n\n",{"name":5,"tags":56,"author":58,"license":15,"version":59,"description":60,"allowed-tools":61,"compatible-with":62},[57,36,5],"productivity","Wondelai \u003Chello@wondelai.com>","1.0.1","Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions \"design sprint\", \"validate in a week\", \"rapid prototype\", \"test with users\", or \"de-risk before building\". Covers mapping, sketching, deciding, prototyping, and testing. For ongoing experimentation, see lean-startup. For customer job analysis, see jobs-to-be-done. Trigger with 'design', 'sprint'.\n","Read, Glob, Grep","claude-code, codex, openclaw","main","def8531e65114c0fca8fb8551c1871ee0eed705c","skills\u002Fjeremylongshore\u002Fclaude-code-plugins-plus-skills\u002Fdesign-sprint",24,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub","https:\u002F\u002Fskillshub.wtf","https:\u002F\u002Fgithub.com\u002FComeOnOliver","AI & Blockchain Engineer\r\n","2026-06-24 22:07:19",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add ComeOnOliver\u002Fskillshub --skill design-sprint",{"tool":78,"command":79},"bunx","bunx skills add ComeOnOliver\u002Fskillshub --skill design-sprint",{"tool":81,"command":82},"pnpm","pnpm dlx skills add ComeOnOliver\u002Fskillshub --skill design-sprint","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fjeremylongshore\u002Fclaude-code-plugins-plus-skills\u002Fdesign-sprint\u002FSKILL.md",true,[],[87,99,109,118,124,131],{"skillNo":88,"name":89,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":95,"publishedAt":51},"01M6FKJN13GMG4KY57J3QD8GY5","model-hierarchy-skill","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzscole\u002Fmodel-hierarchy-skill\u002Fmodel-hierarchy-skill\u002FSKILL.md",[92],{"categoryNo":93,"categoryName":94,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[96,97,98],"model","model hierarchy","model hierarchy skill",{"skillNo":100,"name":101,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":105,"publishedAt":51},"01M6FKJJJ6GCAMR4PPPRD12M5X","zoom-mcp","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-mcp\u002FSKILL.md",[104],{"categoryNo":93,"categoryName":94,"taxonomyType":21,"taxonomyTypeDesc":22},[106,107,108],"MCP","zoom","zoom mcp",{"skillNo":110,"name":111,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":51},"01M6FKJE3KYT3KPEZMEEHYKA6K","zoom-apps-sdk","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[115,116,117,107],"sdk","zoom apps sdk","apps",{"skillNo":119,"name":120,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":51},"01M6FKJ9EDH9Q5VWDF8HAJRSP0","windows","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwindows\u002FSKILL.md",[],[120],{"skillNo":125,"name":126,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":130,"publishedAt":51},"01M6FKJ666BEEFC3AE9GJ72Q93","whiteboard","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwhiteboard\u002FSKILL.md",[129],{"categoryNo":93,"categoryName":94,"taxonomyType":21,"taxonomyTypeDesc":22},[126],{"skillNo":132,"name":133,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":51},"01M6FKJ21WFCDGTJQ2Q91T9DVW","websockets","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[133]]