tool-design-sprint-brief

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Design Sprint Brief

Design Sprint 简报

Produce the brief that aligns the team on challenge, sprint questions, participants, customer recruiting, prototype medium, interview format, logistics, and success criteria before Monday begins. A well-built brief prevents Monday morning from opening with re-litigation of "what are we testing this week?"; a missing or vague brief almost guarantees it.

Family contract:

docs/reference/skill-families/design-sprint-skills-contract.md

. This skill is a member of

design-sprint-skills

在周一启动前制作这份简报，让团队在挑战、冲刺问题、参与者、用户招募、原型载体、访谈形式、后勤安排和成功标准上达成共识。一份完善的简报能避免周一早上还在争论“我们这周要测试什么？”；而缺失或模糊的简报几乎必然会导致这种情况。

技能族协议：

docs/reference/skill-families/design-sprint-skills-contract.md

。本技能属于

design-sprint-skills

技能族。

When to Use

使用时机

The readiness verdict from
```
tool-design-sprint-readiness
```
is Go (or Conditional Go with preconditions cleared).
The sprint has dates blocked on calendars and you need the artifact that names what the sprint is for.
The team has customer recruiting active and you need to commit a recruiting plan, honorarium budget, and Friday schedule before recruiting closes.
A skeptical exec wants to know "what is the team doing for five days plus customer cost?" and you need an answer that fits on two pages.

```
tool-design-sprint-readiness
```
的就绪判定为“通过（Go）”（或“有条件通过（Conditional Go）”且前置条件已满足）。
冲刺日程已在日历中锁定，你需要一份明确冲刺目标的成果文件。
团队已启动用户招募，你需要在招募结束前确定招募计划、酬金预算和周五日程。
持怀疑态度的高管询问“团队花五天时间加上用户成本要做什么？”，你需要一份两页以内的答复。

When NOT to Use

不适用时机

The sprint has already started. The brief is a prep artifact, not an in-sprint deliverable. If Monday is happening, run
```
tool-design-sprint-map-and-target
```
instead.
The readiness verdict is Wait. The brief cannot fix an unready team; close the preconditions first, then re-run readiness, then invoke this skill.
The team wants a stakeholder strategy document. The brief is internal prep, not an external deliverable. If a stakeholder document is needed, that is a downstream artifact (the Friday scorecard or the next-step memo).
Customer recruiting has not started. The brief locks the recruiting plan but cannot replace the recruiter. If no recruiter is named, go back to readiness Wait verdict.

冲刺已启动。本简报是准备阶段的成果，而非冲刺中的交付物。如果周一已到来，请运行
```
tool-design-sprint-map-and-target
```
。
就绪判定为“等待（Wait）”。简报无法解决团队未就绪的问题；先完成前置条件，重新进行就绪判定，再调用本技能。
团队需要一份面向利益相关者的战略文档。本简报是内部准备文件，而非对外交付物。若需要面向利益相关者的文档，应使用下游成果（周五评分卡或下一步备忘录）。
用户招募尚未启动。简报可锁定招募计划，但无法替代招募人员。若未确定招募人员，请回到“等待（Wait）”的就绪判定状态。

What This Skill Produces

本技能产出

A single bundled artifact with nine sections:

Challenge statement and why-now: one paragraph naming the testable challenge and the urgency that justifies a sprint this week vs. later.
Sprint questions: 2-4 specific questions the Friday testing answers. The highest-risk assumption from any prior Foundation Sprint becomes the lead question.
Decider attendance windows: the load-bearing moments (Mon AM, Wed AM, Fri PM at minimum); fully blocked if available.
Team roster with role assignments: who is in the room each day and what role each person plays through the week.
Customer recruiting plan: target profile, source, count, incentive, recruiter owner, recruiting deadline, Friday schedule.
Prototype medium decision: clickable, slideware, service role-play, paper, physical mock, or other; with rationale.
Interview format: live or remote; moderated or unmoderated; recording and consent posture; observer-room setup.
Logistics plan: dates, hours, location, format (in-person, remote, hybrid), tools, daily rhythm.
Success criteria: observable outcomes that mark the sprint successful or not.

See

references/TEMPLATE.md

for the canonical structure and

references/EXAMPLE.md

for the Brainshelf book-catalog brief.

一份包含九个部分的整合成果文件：

挑战声明与紧迫性：一段文字，明确可测试的挑战，以及为何本周而非稍后开展冲刺的紧迫性。
冲刺问题：2-4个具体问题，将由周五的测试给出答案。此前基础冲刺（Foundation Sprint）中风险最高的假设将成为核心问题。
决策者参与时段：关键节点（至少包括周一上午、周三上午、周五下午）；若时间允许需完全预留。
带角色分配的团队名单：每天参与的人员及其在本周承担的角色。
用户招募计划：目标用户画像、招募渠道、人数、激励措施、负责人、招募截止日期、周五日程。
原型载体决策：可点击原型、幻灯片、服务角色扮演、纸质原型、实体模型或其他形式；并说明理由。
访谈形式：线下或远程；有主持人或无主持人；录制与知情同意规则；观察室设置。
后勤安排：日期、时长、地点、形式（线下、远程、混合）、工具、每日节奏。
成功标准：可观测的成果，用于判定冲刺是否成功。

规范结构请参考

references/TEMPLATE.md

，Brainshelf图书目录简报示例请参考

references/EXAMPLE.md

。

Inference Inputs

推理输入

Input	What the skill does with it
Readiness verdict and recommendations (from `tool-design-sprint-readiness` )	Pulls the recommended attendees, customer recruiting plan, pre-sprint activities, and prototype medium proposal; flags any precondition that has not been closed
Challenge description	Compresses into the Challenge Statement and derives 2-4 sprint questions
Founding Hypothesis (optional; from a prior Foundation Sprint)	The highest-risk assumption from the FS scorecard becomes the lead sprint question; the top bet becomes the design direction; the backup becomes the fallback decision if Friday invalidates
Team roster	Maps people to the required Design Sprint roles (Decider, Facilitator, PM, Design, Engineering, Researcher or Customer Expert); confirms 4-7 person band
Customer recruiting source and plan	Locks recruiter owner, target profile, source channel, honorarium budget, deadline, and Friday schedule
Format (in-person, remote, hybrid; per Ratified Decision 6)	Branches the brief body where format affects authoring: recruiting plan (in-person requires geo-local cohort; remote allows cross-timezone), prototype medium (some media work better in-person; e.g., physical mock), interview format (live vs remote moderated), observer setup (in-room vs Zoom breakout room)
Logistics constraints	Produces the dates/hours/location/tools matrix; flags any constraint that would force the sprint to extend beyond 5 days or split across calendar weeks

输入	技能处理方式
就绪判定与建议（来自 `tool-design-sprint-readiness` ）	提取推荐参会人员、用户招募计划、冲刺前活动和原型载体提案；标记未完成的前置条件
挑战描述	压缩为挑战声明，并推导2-4个冲刺问题
初始假设（可选；来自此前的基础冲刺）	基础冲刺评分卡中风险最高的假设成为核心冲刺问题；最优方案成为设计方向；备用方案作为周五验证失败后的 fallback 决策
团队名单	将人员分配到Design Sprint所需角色（决策者、主持人、产品经理、设计师、工程师、研究员或用户专家）；确认团队规模为4-7人
用户招募渠道与计划	锁定招募负责人、目标用户画像、渠道、酬金预算、截止日期和周五日程
形式（线下、远程、混合；依据已批准的决策6）	根据形式调整简报内容：招募计划（线下需本地用户组；远程支持跨时区）、原型载体（部分载体更适合线下，如实体模型）、访谈形式（线下/远程带主持人）、观察室设置（现场/Zoom breakout room）
后勤限制	生成日期/时长/地点/工具矩阵；标记可能导致冲刺超过5天或跨周的限制条件

Brief Length Discipline

简报篇幅规范

The brief MUST fit on two pages (or two screens). The DS brief is intentionally longer than the FS brief because the customer-recruiting, prototype-medium, and interview-format sections have no FS equivalent and must be committed to before Monday.

Challenge Statement: one paragraph, four sentences maximum.
Sprint Questions: 2-4 numbered questions, each one sentence.
Team Roster: table with one row per person.
Customer Recruiting: table.
Prototype Medium: one paragraph including rationale.
Interview Format: one paragraph.
Logistics: table.
Success Criteria: 3-5 bulleted outcomes.

If the brief expands beyond two pages, the sprint is being over-engineered before it starts. The fix is not a longer brief; the fix is sharper sprint questions and a clearer prototype medium decision.

简报必须控制在两页（或两个屏幕）以内。Design Sprint简报特意比基础冲刺（FS）简报更长，因为用户招募、原型载体和访谈形式部分在基础冲刺中没有对应内容，且必须在周一前确定。

挑战声明：一段文字，最多四句话。
冲刺问题：2-4个编号问题，每个问题一句话。
团队名单：每人一行的表格。
用户招募：表格形式。
原型载体：一段文字，包含理由。
访谈形式：一段文字。
后勤安排：表格形式。
成功标准：3-5条 bullet 形式的成果。

如果简报超过两页，说明冲刺在启动前被过度设计。解决方法不是延长简报，而是优化冲刺问题、明确原型载体决策。

Common Pitfalls

常见误区

Vague sprint questions. "Will users like it?" is not a sprint question. "Will 25+/year readers complete sub-3-second camera capture without abandoning?" is. Sprint questions must be answerable from Friday's 5-customer interviews.
Recruiting plan that does not match target customer. Recruiting from a panel that skews younger or different demographics than the named target produces Friday data that does not test the actual assumption. Cross-check recruiting source against the readiness customer profile.
Skipping prototype medium decision. Leaving prototype medium to Thursday morning forces the team into ad-hoc choice and risks the prototype not being testable Friday. Lock it in the brief; if needed, change it after Wednesday's storyboard but commit a default upfront.
Treating the brief as a stakeholder deliverable. Stakeholders read the Friday scorecard and the Decider's next-step memo, not the brief. Sharing the brief publicly invites pre-sprint debate, which the sprint is supposed to resolve.
Logistics drift. "We'll figure out remote vs in-person sometimes" telegraphs that the team has not committed. Either format is locked, or the readiness verdict was wrong.
No interview format decision. Friday interview moderator, observation-room setup, and recording/consent posture should be in the brief. Forgetting these is the most common cause of Friday running long.

模糊的冲刺问题：“用户会喜欢吗？”不是合格的冲刺问题。“年阅读量25+的用户能否在3秒内完成相机拍摄而不放弃？”才是。冲刺问题必须能通过周五的5位用户访谈得到答案。
招募计划与目标用户不匹配：从偏向年轻或与目标用户画像不同的群体招募，会导致周五的数据无法验证实际假设。需交叉核对招募渠道与就绪阶段确定的用户画像。
跳过原型载体决策：留到周四上午再确定原型载体，会让团队陷入临时选择，且可能导致原型无法在周五测试。在简报中锁定载体；若需调整，可在周三故事板完成后更改，但需提前确定默认方案。
将简报作为面向利益相关者的交付物：利益相关者应阅读周五评分卡和决策者的下一步备忘录，而非简报。公开分享简报会引发冲刺前的争论，而冲刺正是为了解决这些争论。
后勤安排不确定：“我们之后再决定线下还是远程”表明团队未做出承诺。要么锁定形式，要么说明就绪判定有误。
未确定访谈形式：周五访谈的主持人、观察室设置、录制/知情同意规则应在简报中明确。遗漏这些是导致周五流程超时的最常见原因。

Canonical Sources

权威来源

Knapp, J., Zeratsky, J., and Kowitz, B. Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days. Simon and Schuster, 2016. Chapter 3 "Set the Stage" on sprint brief composition.
Character Capital. "Design Sprint pre-sprint guide." https://www.character.vc
Google Design Sprint Kit. "Sprint brief template." https://designsprintkit.withgoogle.com/
AJ and Smart "Remote Design Sprint" template. Adapted for the remote and hybrid format sections.

Knapp, J., Zeratsky, J., and Kowitz, B. Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days. Simon and Schuster, 2016. 第3章“搭建舞台”关于冲刺简报的撰写。
Character Capital. "Design Sprint pre-sprint guide." https://www.character.vc
Google Design Sprint Kit. "Sprint brief template." https://designsprintkit.withgoogle.com/
AJ and Smart "Remote Design Sprint" template. 适配了远程和混合形式的内容。

Cross-Skill Usage

跨技能使用

Prerequisites:

tool-design-sprint-readiness

. The brief expects the readiness output as its primary input. When

prerequisites

is honored, the brief inherits the readiness verdict, customer recruiting plan draft, attendee recommendations, and pre-sprint activities; the skill then refines and locks them.

If the team has done equivalent prep without running the readiness skill explicitly (e.g., experienced sprint facilitator who knows the readiness criteria), the brief skill can be invoked directly. In that case, the skill body prompts the team to confirm the readiness criteria are met before generating the brief.

A team coming from a Foundation Sprint should bring the Founding Hypothesis and assumption scorecard as inputs. The brief's Sprint Questions section pulls the highest-risk assumption verbatim as the lead question. No bridge skill is required; the narrative handoff is documented in

_workflows/foundation-to-design.md

Next invocation in the sprint:

tool-design-sprint-map-and-target

on Monday morning.

前置技能：

tool-design-sprint-readiness

。本简报将就绪输出作为主要输入。若遵循前置要求，简报将继承就绪判定、用户招募计划草案、参会人员建议和冲刺前活动；随后技能会对这些内容进行优化并锁定。

如果团队未明确运行就绪技能但已完成等效准备（如熟悉就绪标准的资深冲刺主持人），可直接调用本简报技能。此时技能会提示团队先确认就绪标准已满足，再生成简报。

来自基础冲刺的团队应提供初始假设和假设评分卡作为输入。简报的冲刺问题部分会直接将风险最高的假设作为核心问题。无需过渡技能；流程衔接记录在

_workflows/foundation-to-design.md

中。

冲刺中的下一个调用：周一上午运行

tool-design-sprint-map-and-target

。

Decider Checkpoint

决策者 checkpoint

This skill ends with a Decider Checkpoint in

references/TEMPLATE.md

. The Decider signs off on scope (the challenge and sprint questions), team (the roster and attendance windows), recruiting plan (target profile, source, honorarium budget), prototype medium, interview format, and the explicit success criteria. Without sign-off, the brief is advisory; with sign-off, it is the contract for the next five days and the authorization for customer-recruiting spend.

本技能在

references/TEMPLATE.md

中包含一个决策者checkpoint。决策者需对范围（挑战和冲刺问题）、团队（名单和参与时段）、招募计划（目标用户画像、渠道、酬金预算）、原型载体、访谈形式和明确的成功标准签字确认。未签字时，简报仅为参考；签字后，它将成为接下来五天的执行协议，同时也是用户招募支出的授权文件。