| 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 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'.
|
| allowed-tools | Read, Glob, Grep |
| license | MIT |
| author | Wondelai <hello@wondelai.com> |
| version | 1.0.1 |
| compatible-with | claude-code, codex, openclaw |
| tags | ["productivity","testing","design-sprint"] |
Design Sprint Framework
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.
Core Principle
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.
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.
Scoring
Goal: 10/10. When planning or executing a Design Sprint, rate it 0-10 based on adherence to the principles below. A 10/10 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/10.
The 5-Day Sprint Process
Monday → Tuesday → Wednesday → Thursday → Friday
Map Sketch Decide Prototype Test
Prerequisites:
- Big challenge: Important problem worth a week's focus
- Right team: Decision maker + 4-7 people with diverse expertise
- Time commitment: 5 full days (10am-5pm), no interruptions
- Space: Dedicated room with whiteboards
Sprint Master: One person facilitates, keeps time, manages energy.
Monday: Map
Goal: Understand the problem and choose a target for the week.
Morning: Start at the End
Exercise: Long-term goal
- Write the sprint question: "What do we want to be true in 2 years?"
- Example: "Customers use our product daily" or "We've captured 20% market share"
Exercise: Sprint questions
- List obstacles and unknowns as questions
- Example: "Will customers trust us with payment info?" or "Can first-time users figure out the interface?"
Format: Write on whiteboard, entire team contributes
Afternoon: Map the Challenge
Exercise: Map the customer journey
- List actors (different types of customers/users)
- Draw the journey from start to finish (left to right on whiteboard)
- Keep it simple: 5-15 steps max
