design-sprint
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseDesign Sprint
Design Sprint
What It Is
什么是Design Sprint
A Design Sprint is a five-day process for answering critical business questions through design, prototyping, and testing with customers. Developed by Jake Knapp at Google Ventures (now GV), it has been used by teams at Slack, Uber, Airbnb, LEGO, the New York Times, and hundreds of startups.
The core insight: Instead of debating ideas for months then building for months, compress everything into one week. By Friday, you'll have tested a realistic prototype with real customers and know whether you're on the right track.
A Design Sprint changes the defaults of how teams work:
- Instead of endless brainstorming: structured individual sketching
- Instead of design by committee: one Decider with authority
- Instead of building real products: realistic "fake" prototypes
- Instead of launching and hoping: testing with 5 target customers
Design Sprint是一个为期五天的流程，通过设计、原型制作和用户测试来解答关键业务问题。它由Google Ventures（现名为GV）的Jake Knapp开发，已被Slack、Uber、Airbnb、乐高、《纽约时报》以及数百家创业公司的团队采用。
核心洞见：**与其花费数月时间争论想法再花费数月开发，不如将所有环节压缩至一周内完成。**到周五，你就可以用真实原型完成目标用户测试，明确自己是否走在正确的轨道上。
Design Sprint改变了团队的默认工作模式：
- 取代无休无止的头脑风暴：结构化的个人草图创作
- 取代集体决策式设计：指定一位拥有决策权的Decider（决策者）
- 取代开发真实产品：制作高度逼真的「模拟」原型
- 取代上线后碰运气：针对5位目标用户开展测试
When to Use It
何时使用Design Sprint
Use a Design Sprint when:
- You're starting something new and need to validate direction before committing engineering resources
- Stakes are high — the project will require significant investment and you need confidence before building
- You're stuck — the team has been debating the same ideas for weeks or months without progress
- There's a big behavioral risk — the product requires customers to change how they work or think
- You need alignment — stakeholders have different visions and you need a forcing function
- Time pressure exists — you have a deadline, a launch window, or limited runway
使用Design Sprint的场景：
- 启动新项目时：在投入工程资源前验证方向
- 项目风险高时：项目需要大量投入，需在开发前建立信心
- 团队陷入僵局时：团队为同一问题争论数周甚至数月却毫无进展
- 存在行为风险时：产品需要用户改变现有工作或思考方式
- 需要对齐共识时：利益相关者有不同愿景，需要一个强制推进的机制
- 时间紧迫时：有截止日期、上线窗口期或资金储备有限
When Not to Use It
何时不使用Design Sprint
Don't use a Design Sprint when:
- You already have strong signal from existing customers (iterate instead)
- The solution is obvious and low-risk (just build it)
- Key stakeholders can't commit to the full week
- You don't have access to target customers for testing
- The team wants to use it as "innovation theater" without intent to act on findings
- The problem is purely technical with no user-facing component
请勿在以下场景使用Design Sprint：
- 已从现有用户处获得明确反馈（此时应选择迭代优化）
- 解决方案明确且风险低（直接开发即可）
- 关键利益相关者无法全程参与整周的冲刺
- 无法接触到目标用户开展测试
- 团队将其作为「创新表演」，无意根据测试结果采取行动
- 问题纯技术性，无用户交互环节
Patterns
实践模式
Detailed examples showing how to apply Design Sprints correctly. Each pattern shows a common mistake and the correct approach.
以下是正确应用Design Sprint的详细示例，每个模式都会展示常见错误及正确做法。
Critical (get these wrong and you've wasted your week)
关键原则（一旦出错，整周工作将前功尽弃）
| Pattern | What It Teaches |
|---|---|
| wrong-problem-for-sprint | Not every problem benefits from a sprint — pick the right challenge |
| missing-decider | Without a Decider present, the sprint stalls or gets overturned |
| prototype-too-polished | Goldilocks quality — realistic enough to test, rough enough to throw away |
| testing-wrong-users | Five target customers beats fifty random people |
| skipping-the-map | Jumping to solutions without mapping the problem guarantees misalignment |
| 模式 | 核心要点 |
|---|---|
| wrong-problem-for-sprint | 并非所有问题都适合用冲刺解决——要选对挑战 |
| missing-decider | 若没有Decider参与，冲刺会陷入停滞或结果被推翻 |
| prototype-too-polished | 原型质量要恰到好处——足够逼真可用于测试，同时足够粗糙可随时舍弃 |
| testing-wrong-users | 5位目标用户的测试价值远胜于50位随机用户 |
| skipping-the-map | 不梳理问题直接跳到解决方案，必然导致团队共识错位 |
High Impact
高影响原则
| Pattern | What It Teaches |
|---|---|
| group-brainstorming | Work alone together — individual sketching beats group ideation |
| too-many-ideas | Commit to one prototype, not a choose-your-own-adventure |
| expert-interviews-skipped | Monday interviews surface constraints you'd otherwise discover Friday |
| storyboard-too-vague | The storyboard is the blueprint — vague boards create confused prototypes |
| prototype-scope-creep | Prototype the critical path, not the whole product |
| testing-for-validation | You're testing to learn, not to prove you were right |
| 模式 | 核心要点 |
|---|---|
| group-brainstorming | 独立协作——个人草图创作优于集体头脑风暴 |
| too-many-ideas | 专注于一个原型，而非提供多个选项 |
| expert-interviews-skipped | 周一的专家访谈可提前发现约束条件，避免周五才踩坑 |
| storyboard-too-vague | 故事板是蓝图——模糊的故事板会导致原型混乱 |
| prototype-scope-creep | 原型只需覆盖核心路径，无需还原整个产品 |
| testing-for-validation | 测试的目的是学习，而非证明自己正确 |
Medium Impact
中影响原则
| Pattern | What It Teaches |
|---|---|
| ignoring-sprint-questions | Write sprint questions Monday, answer them Friday |
| facilitator-participates | Facilitators facilitate — they don't pitch their own ideas |
| no-debrief | Friday's patterns need synthesis before Monday's decisions |
| 模式 | 核心要点 |
|---|---|
| ignoring-sprint-questions | 周一提出冲刺问题，周五给出答案 |
| facilitator-participates | 引导者只需负责引导——不要提出自己的想法 |
| no-debrief | 周五的测试结果需要先进行总结，再用于周一的决策 |
Deep Dives
深度解析
Read only when you need extra detail.
- : Expanded framework detail, checklists, and examples.
references/design-sprint-playbook.md
仅在需要额外细节时阅读。
- : 扩展的框架细节、清单及示例。
references/design-sprint-playbook.md
Resources
资源
Books:
- Sprint by Jake Knapp with John Zeratsky and Braden Kowitz — the complete guide
- Make Time by Jake Knapp and John Zeratsky — tactics for focus and energy that power productive sprints
Online:
- The Sprint Book — free resources, Miro template, video walkthroughs
- GV Library — essays and case studies from Google Ventures
- Character Labs — Jake and John's accelerator program using sprint sequences
Origins:
The Design Sprint was developed by Jake Knapp at Google, refined through hundreds of sprints at Google Ventures, and documented in the 2016 book Sprint. It draws on design thinking, IDEO methods, and psychological research on decision-making and creativity.
书籍：
- Sprint by Jake Knapp with John Zeratsky and Braden Kowitz — 完整指南
- Make Time by Jake Knapp and John Zeratsky — 助力高效冲刺的专注力与精力管理策略
线上资源：
- The Sprint Book — 免费资源、Miro模板、视频教程
- GV Library — Google Ventures的文章与案例研究
- Character Labs — Jake和John的加速器项目，采用冲刺序列法
起源：
Design Sprint由Jake Knapp在Google开发，经过Google Ventures数百次冲刺实践打磨，并在2016年出版的《Sprint》一书中正式记录。它融合了设计思维、IDEO方法以及关于决策与创造力的心理学研究。