tool-design-sprint-prototype-plan
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinese<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
Design Sprint Prototype Plan (Thursday morning)
Design Sprint 原型规划（周四上午）
Thursday is the prototype build day. This skill produces the morning planning artifact that makes the build run; it does NOT build the prototype itself. The skill assigns roles, locks the fidelity bar, drafts the Five-Act interview script, defines the trial-run gate, and confirms Friday participants. The actual building (Figma frames, slideware decks, role-play scripts, paper assemblies) is craft work the team owns through the rest of Thursday.
Family contract: . This skill is a member of .
docs/reference/skill-families/design-sprint-skills-contract.mddesign-sprint-skills周四是原型构建日。本技能用于生成当日上午的规划工件，保障构建工作顺利推进；不负责原型本身的构建。技能会完成角色分配、确定保真度标准、起草五幕式访谈脚本、定义试运行关卡，并确认周五的参与者。实际构建工作（Figma 帧、演示文稿、角色扮演脚本、纸质组件组装）由团队在周四剩余时间内自主完成。
家族协议：。本技能属于 家族。
docs/reference/skill-families/design-sprint-skills-contract.mddesign-sprint-skillsWhen to Use
使用场景
- It is Thursday morning of the Design Sprint and Wednesday's storyboard is signed off.
- The Friday participant tracker needs a Thursday-morning confirmation check; cancellations now trigger buffer activation.
- The interview script needs to be drafted (or refined from a prior sprint's template) before the interviewer can mock-run it Thursday afternoon.
- The team needs role assignments before parallel build work begins; ad-hoc assignment Thursday afternoon wastes 1-2 hours.
- 处于设计冲刺的周四上午，且周三的故事板已获批。
- 需要在周四上午确认周五的参与者追踪表；此时出现取消情况需触发备用参与者机制。
- 访谈脚本需在周四下午面试官进行模拟演练前完成起草（或基于之前冲刺的模板优化）。
- 团队需在并行构建工作开始前完成角色分配；周四下午临时分配会浪费1-2小时。
When NOT to Use
不适用场景
- Wednesday is not closed. Return to ; without a locked storyboard, the prototype has no spec.
tool-design-sprint-decide-and-storyboard - The team is trying to use this skill to build the prototype. The prototype is craft work (per Ratified Decision 1 in the DS integration plan). This skill plans Thursday; the build happens in Figma, Keynote, paper, or whatever the medium is.
- The team has decided to skip Friday's trial run. Trial run is the gate that catches "prototype is unreachable" or "interview script confuses customer" before live interviews start. Skipping it converts Friday into a debugging session.
- Friday participant cancellations have triggered cohort-shrinks-to-fewer-than-4. Pause the sprint and decide whether to postpone Friday or accept a reduced-evidence test.
- 周三的工作未收尾。请返回 ；没有锁定的故事板，原型就没有明确的规格。
tool-design-sprint-decide-and-storyboard - 团队试图用本技能构建原型。根据设计冲刺集成计划中的已批准决策1，原型构建属于手工工作。本技能仅负责周四的规划，构建需在Figma、Keynote、纸质媒介或其他指定工具中完成。
- 团队决定跳过周五的试运行。试运行是正式访谈前排查「原型无法访问」或「访谈脚本令客户困惑」等问题的关卡。跳过试运行会让周五变成调试环节。
- 周五参与者取消导致人数少于4人。暂停冲刺，决定是推迟周五的访谈还是接受证据不足的测试。
What This Skill Produces
本技能产出
A single bundled artifact with five sections:
- Prototype role plan: assigns 5 canonical roles (Maker, Stitcher, Writer, Asset Collector, Interviewer) across the team. Roles can double up on small teams; cannot triple up except for Asset Collector.
- Prototype brief: one-page spec covering what to build (storyboard panels in scope), fidelity bar (what "real enough" means for the medium), time allocation per role, and what's explicitly NOT being built.
- Interview script (Five-Act): canonical Five-Act structure (Welcome, Context, Intro, Tasks, Debrief) with team-supplied task wording derived from the storyboard. The act sequence is fixed; only Tasks is heavily customized.
- Trial-run checklist: the gates the prototype must pass Thursday afternoon (canonically 16:00-17:00) before Friday begins. Each gate is a yes/no item the interviewer or Maker confirms.
- Participant confirmation tracker: Thursday morning re-confirmation of all 5 Friday slots; cancellations trigger buffer-slot activation; failures cascade to a cohort-decision moment.
See for the canonical structure and for the Brainshelf book-catalog Thursday morning artifact.
references/TEMPLATE.mdreferences/EXAMPLE.md包含五个部分的整合工件：
- 原型角色分配计划：为团队分配5个标准角色（Maker、Stitcher、Writer、Asset Collector、Interviewer）。小团队可一人兼任两个角色；除Asset Collector外，不可一人兼任三个角色。
- 原型 brief：单页规格说明，涵盖需构建内容（纳入范围的故事板面板）、保真度标准（对应媒介下「足够真实」的定义）、各角色时间分配，以及明确不需构建的内容。
- 五幕式访谈脚本：采用标准五幕结构（Welcome、Context、Intro、Tasks、Debrief），其中任务表述由团队根据故事板定制。幕次顺序固定，仅Tasks部分需大量定制。
- 试运行检查清单：周四下午（通常为16:00-17:00）原型需通过的关卡，每项为面试官或Maker确认的是/否项。
- 参与者确认追踪表：周四上午再次确认所有5个周五的参与名额；取消情况触发备用名额机制；若失败则需进入 cohort 决策环节。
标准结构可参考 ，Brainshelf 图书目录的周四上午工件示例可参考 。
references/TEMPLATE.mdreferences/EXAMPLE.mdFive Canonical Roles
五个标准角色
Sprint book Chapter 16 defines these 5 roles. The skill assigns them; the humans fill them.
| Role | What they do | Typical owner |
|---|---|---|
| Maker | Builds the prototype surface (Figma frames, Keynote slides, role-play props). Owns visual and interaction work. | Design lead |
| Stitcher | Connects the Maker's surfaces into a coherent end-to-end flow (Figma interactions, Keynote transitions, role-play sequence). | Design lead OR engineering lead |
| Writer | Writes prototype copy (button labels, body text, error states, microcopy). Critical for credibility; bad copy breaks trust. | PM OR researcher |
| Asset Collector | Sources images, icons, sample data (book covers, names, dates, fake-but-believable data). | Anyone with free hands; often whoever isn't on the critical path. |
| Interviewer | Runs Friday's interviews. Spends Thursday afternoon drafting and mock-running the Five-Act script. | Researcher OR PM with interview experience. |
On a 4-person team, Maker and Stitcher typically merge (one design owner); Writer and Asset Collector can merge; Interviewer is always a dedicated role.
冲刺书籍第16章定义了这5个角色。本技能负责分配角色，由人员实际承担。
| 角色 | 职责 | 典型负责人 |
|---|---|---|
| Maker | 构建原型界面（Figma 帧、Keynote 幻灯片、角色扮演道具），负责视觉与交互工作。 | 设计负责人 |
| Stitcher | 将Maker制作的界面连接成连贯的端到端流程（Figma 交互、Keynote 转场、角色扮演序列）。 | 设计负责人或工程负责人 |
| Writer | 撰写原型文案（按钮标签、正文文本、错误状态、微文案）。文案对可信度至关重要，劣质文案会破坏信任。 | 产品经理或研究员 |
| Asset Collector | 收集图片、图标、样本数据（书籍封面、姓名、日期、看似真实的虚构数据）。 | 空闲人员；通常为非关键路径上的成员 |
| Interviewer | 主持周五的访谈。周四下午需起草并模拟演练五幕式脚本。 | 研究员或具备访谈经验的产品经理 |
4人团队中，Maker和Stitcher通常合并（由一名设计负责人兼任）；Writer和Asset Collector可合并；Interviewer始终为专属角色。
Five-Act Interview Structure
五幕式访谈结构
Canonical structure from Sprint book Chapter 17. The act sequence is fixed; the Tasks act is heavily customized; the other acts are mostly canonical wording.
| Act | Time | Purpose | Canonicality |
|---|---|---|---|
| Welcome | 5 min | Friendly intro; consent confirmation; explain not testing the customer | Canonical wording with team-name swap |
| Context | 5-10 min | Learn the customer's current behavior and context related to the challenge | Canonical questions; team adapts to challenge |
| Intro | 5 min | Introduce the prototype; explain it's a prototype (some things won't work) and ask the customer to think aloud | Canonical wording |
| Tasks | 20-30 min | Customer attempts the storyboard tasks; interviewer observes and probes; team observes silently from breakout room | Team-supplied wording derived from storyboard |
| Debrief | 5-10 min | Open-ended reactions; pricing questions if relevant; thank-you | Canonical structure; team adapts pricing question |
冲刺书籍第17章的标准结构。幕次顺序固定，Tasks部分需大量定制，其他幕次多采用标准表述。
| 幕次 | 时长 | 目的 | 标准化程度 |
|---|---|---|---|
| Welcome | 5分钟 | 友好开场；确认知情同意；说明不是测试客户 | 标准表述，仅需替换团队名称 |
| Context | 5-10分钟 | 了解客户当前与挑战相关的行为和场景 | 标准问题，团队可根据挑战调整 |
| Intro | 5分钟 | 介绍原型；说明这是原型（部分功能无法使用），并要求客户边操作边思考 | 标准表述 |
| Tasks | 20-30分钟 | 客户尝试完成故事板中的任务；面试官观察并提问；团队在 breakout room 中静默观察 | 团队根据故事板定制表述 |
| Debrief | 5-10分钟 | 开放式反馈；若相关则询问定价问题；致谢 | 标准结构，团队可调整定价问题 |
Common Pitfalls
常见误区
- Treating the prototype as a deliverable instead of a learning tool. The prototype dies Friday at 17:00 PT regardless of how Friday goes. Investing engineering time in polishing it past the fidelity bar wastes Thursday.
- Polishing instead of building enough realism. Fidelity bar question: "Will a customer believe this is real for the 30-minute interview?" If yes, the prototype is done. Polishing past that point steals time from trial run and recovery.
- Interview script with leading questions. "Did you find the camera flow easy?" leads; "Walk me through what you just did" doesn't. Writer (or Interviewer) reviews script for leading questions before trial run.
- Skipping trial run. Trial run catches dead Figma links, missing assets, confusing copy, and interviewer-script-too-long failures. Always run with a fake customer (a teammate playing a target-profile customer) Thursday afternoon.
- Asset Collector role left unassigned because "it's not important." Asset Collector is the role that prevents "lorem ipsum on the demo screen" and "stock photo of a person who clearly isn't the target customer." Always assign.
- Five-Act Tasks act over-scripted. Tasks should be open-ended ("Try to capture this book and find it later in your library"); over-scripted tasks become a tutorial, not a test.
- Cancellations Thursday morning not surfaced because "we'll figure it out." Thursday morning is the last clean window to activate buffer participants. By Thursday afternoon, recruiter has lower confidence in confirmation.
- 将原型视为交付物而非学习工具。无论周五结果如何，原型都会在周五17:00（太平洋时间）停用。投入工程时间超出保真度标准打磨原型是在浪费周四的时间。
- 过度打磨而非构建足够真实的原型。保真度标准问题：「客户在30分钟访谈中会认为这是真实的吗？」如果是，原型就完成了。超出该标准的打磨会占用试运行和补救的时间。
- 访谈脚本包含诱导性问题。「你觉得相机流程容易吗？」属于诱导性问题；「请告诉我你刚才做了什么」则不是。Writer（或Interviewer）需在试运行前检查脚本是否存在诱导性问题。
- 跳过试运行。试运行可排查Figma链接失效、资源缺失、文案混淆、访谈脚本过长等问题。周四下午务必安排一名队友扮演目标客户进行模拟演练。
- 因「不重要」而未分配Asset Collector角色。Asset Collector角色可避免「演示屏幕上的占位文本」和「明显不符合目标客户的库存图片」等问题。务必分配该角色。
- 五幕式Tasks部分过度脚本化。任务应开放式表述（「尝试收藏这本书并稍后在你的图书馆中找到它」）；过度脚本化的任务会变成教程而非测试。
- 周四上午的取消情况未及时处理，认为「之后再解决」。周四上午是激活备用参与者的最后窗口期。到周四下午，招聘人员确认备用参与者的成功率会降低。
Cross-Skill Usage
跨技能使用
Prerequisites: . Prototype-plan consumes Wednesday's storyboard as the build spec. Without a storyboard, this skill has no panels to map roles against.
tool-design-sprint-decide-and-storyboardThis skill does NOT invoke . Thursday morning planning has no voting moment; the role plan and script decisions are Facilitator-led with Decider sign-off.
tool-note-and-voteNext invocation in the sprint: Friday morning.
tool-design-sprint-test-and-score前置技能：。原型规划技能会将周三的故事板作为构建规格。没有故事板，本技能就没有可映射角色的面板。
tool-design-sprint-decide-and-storyboard本技能不调用 。周四上午的规划无需投票环节；角色分配和脚本决策由主持人主导，需经决策者批准。
tool-note-and-vote冲刺中的下一个调用技能：周五上午的 。
tool-design-sprint-test-and-scoreCanonical Sources
标准来源
- Knapp, J., Zeratsky, J., and Kowitz, B. Sprint. Simon and Schuster, 2016. Thursday chapter (Chapters 14-16) and Five-Act Interview (Chapter 17).
- GV Design Sprint Guide. "Sprint Week Thursday." https://www.gv.com/sprint/
- Character Capital. "Design Sprint Day 4." https://www.character.vc
- Google Design Sprint Kit. "Thursday agenda template + Five-Act Interview script template." https://designsprintkit.withgoogle.com/
- Knapp, J., Zeratsky, J., and Kowitz, B. Sprint. Simon and Schuster, 2016. 周四章节（第14-16章）和五幕式访谈（第17章）。
- GV Design Sprint Guide. "Sprint Week Thursday." https://www.gv.com/sprint/
- Character Capital. "Design Sprint Day 4." https://www.character.vc
- Google Design Sprint Kit. "Thursday agenda template + Five-Act Interview script template." https://designsprintkit.withgoogle.com/
Decider Checkpoint
决策者检查点
This skill ends with a Decider Checkpoint in . The Decider approves the role plan, the fidelity bar in the prototype brief, the interview script's Tasks act, and the trial-run gate criteria. Once signed, the team disperses into parallel build work; the Decider returns Friday PM for the post-interview Decider review.
references/TEMPLATE.md本技能结束时，需在 中完成决策者检查点。决策者需批准角色分配计划、原型brief中的保真度标准、访谈脚本的Tasks部分，以及试运行关卡标准。获批后，团队分散进行并行构建工作；决策者需在周五下午返回，参与访谈后的决策者评审。
references/TEMPLATE.md