Back to Details

tool-design-sprint-decide-and-storyboard

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 Decide and Storyboard (Wednesday)

设计冲刺（Design Sprint）：决策与故事板（周三）

Wednesday is the most decision-heavy day of the Design Sprint. The skill runs the art museum layout (sketches posted anonymously on the wall), heat map (silent dot-vote stickers on promising parts), speed critique (3 minutes per sketch summarizing what the team sees), straw poll (each team member's top choice), and the Decider's supervote (the call that triggers the storyboard). Then the team decides whether to rumble (storyboard two sketches as competing prototypes) or all-in-one (storyboard one). The day ends with a 5-15 step storyboard that drives Thursday's build.
Family contract: 
docs/reference/skill-families/design-sprint-skills-contract.md
. This skill is a member of 
design-sprint-skills
.
周三是设计冲刺（Design Sprint）中决策最密集的一天。该流程涵盖美术馆布局（草图匿名张贴在墙上）、热力图（用无声贴点投票选出有潜力的部分）、快速评审（每张草图用3分钟总结团队看法）、意向投票（每位团队成员选出自己的首选），以及决策者（Decider）的超级投票（触发故事板制作的最终决定）。随后团队需决定是采用“二选一”（为两张草图制作故事板，作为竞争原型）还是“全合一”（为一张草图制作故事板）。当天结束时将产出5-15步的故事板，用于指导周四的原型制作。
家族协议：
docs/reference/skill-families/design-sprint-skills-contract.md
。该流程属于
design-sprint-skills
家族。

When to Use

适用场景

  • It is Day 3 of the Design Sprint and Tuesday's sketches are collected, attribution-stripped, and uploaded to the shared workspace.
  • The Decider is present for the full morning (heat map plus critique plus straw poll plus supervote happen 09:00-12:30 canonically).
  • The team has accepted that the supervote is the Decider's call, not a consensus average.
  • Thursday's prototype build needs a storyboard by Wednesday end-of-day or the build cannot start clean Thursday morning.
  • 处于设计冲刺（Design Sprint）第三天，且已收集周二的草图、去除署名并上传至共享工作区。
  • 决策者（Decider）全程参与上午的活动（标准流程中，热力图、评审、意向投票和超级投票在09:00-12:30进行）。
  • 团队已认可超级投票是决策者的最终决定，而非共识平均值。
  • 周四的原型制作需在周三下班前拿到故事板，否则周四上午无法顺利启动制作。

When NOT to Use

不适用场景

  • Tuesday is not closed. Return to 
    tool-design-sprint-sketch
    ; without independent sketches, the heat-map is meaningless.
  • Sketcher attribution leaked into Wednesday morning. The Facilitator must re-strip before the heat-map begins; voting on sketchers contaminates the day.
  • The Decider is absent. Wednesday's supervote cannot be delegated; without the Decider, the day produces a recommendation, not a decision.
  • The team is treating the supervote as advisory. The supervote is the call. Re-litigating it Thursday morning is sprint failure.
  • 周二的草图环节尚未完成。请回到
    tool-design-sprint-sketch
    流程；没有独立的草图，热力图投票毫无意义。
  • 草图作者的署名信息在周三上午泄露。主持人（Facilitator）必须在热力图投票开始前重新去除署名；针对作者的投票会影响当天的决策公正性。
  • 决策者（Decider）缺席。周三的超级投票无法委托他人；没有决策者，当天只能产出建议，而非最终决策。
  • 团队将超级投票视为参考意见。超级投票是最终决定，若周四上午重新讨论则意味着冲刺失败。

What This Skill Produces

产出成果

A single bundled artifact with seven sections:
  1. Art museum layout: how sketches are arranged for viewing (typically wall or shared Figma board); attribution stripped; sketches labeled A / B / C / D / etc. in randomized order.
  2. Heat map: silent dot-vote stickers (typically 3 small dots per voter) placed on the most compelling PARTS of any sketch; voters can stack dots on the same element.
  3. Speed critique notes: 3-minute structured walkthrough per sketch by the Facilitator (or rotated team member) summarizing what the team sees; the sketcher does NOT explain their own sketch; concerns are captured as "what would worry me" notes.
  4. Straw poll results: each team member places one larger sticker (typically 1 large dot per voter) on the sketch they would pick if it were their call. Non-binding; informs the Decider.
  5. Supervote: the Decider places their supervote sticker (typically 3 large dots or a distinctively-colored sticker). The supervote is the decision. The Decider can place multiple supervotes on different sketches if running a rumble.
  6. Rumble vs all-in-one decision: the Decider chooses to storyboard one sketch (all-in-one; default) or two sketches as competing prototypes (rumble; chosen when the supervotes split clearly across two distinct approaches).
  7. Storyboard: 5-15 step storyboard derived from the supervoted sketch(es); each panel shows what the customer sees and what they do; specific enough that Thursday's build can begin without re-debating the design.
See 
references/TEMPLATE.md
for the canonical structure and 
references/EXAMPLE.md
for the Brainshelf book-catalog Wednesday artifact.
一份包含七个部分的整合成果：
  1. 美术馆布局：草图的展示排列方式（通常是墙面或共享Figma画板）；已去除署名；草图按随机顺序标记为A/B/C/D等。
  2. 热力图：用无声贴点投票（通常每位投票者有3个小点贴纸）标记出所有草图中最具吸引力的部分；投票者可在同一元素上叠加贴纸。
  3. 快速评审记录：由主持人（Facilitator）或轮换的团队成员对每张草图进行3分钟结构化讲解，总结团队的看法；草图作者不得解释自己的作品；关注点记录为“我担心的问题”。
  4. 意向投票结果：每位团队成员将一个较大的贴纸（通常每位投票者1个大点贴纸）贴在自己会选择的草图上。该投票不具约束力，仅为决策者提供参考。
  5. 超级投票：决策者（Decider）贴上超级投票贴纸（通常是3个大点或特殊颜色的贴纸）。超级投票即为最终决策。若采用“二选一”模式，决策者可在不同草图上进行多次超级投票。
  6. 二选一或全合一决策：决策者选择为一张草图制作故事板（全合一；默认选项），或为两张草图制作故事板作为竞争原型（二选一；当超级投票明显偏向两种不同方案时选择）。
  7. 故事板：基于超级投票选中的草图制作的5-15步故事板；每个面板展示用户看到的内容和操作；内容需足够具体，确保周四的原型制作无需重新讨论设计方案。
标准结构请参考
references/TEMPLATE.md
，Brainshelf图书目录的周三成果示例请参考
references/EXAMPLE.md
。

Wednesday Time Structure

周三时间安排

The full Wednesday workshop is approximately 7 hours (09:00-12:30 + 13:30-17:00). The skill's bundled artifact emerges across the day:
  • 09:00-09:15: Welcome + Tuesday recap + Wednesday agenda
  • 09:15-09:30: Art museum setup; Facilitator confirms sketches are attribution-stripped and labeled A/B/C/D
  • 09:30-09:45: Heat map (silent; 15 minutes; team places dot stickers on compelling parts)
  • 09:45-10:45: Speed critique (3 min per sketch; sketchers silent during their own sketch's critique)
  • 10:45-11:00: Break
  • 11:00-11:15: Straw poll (silent; each person places 1 large dot on their pick)
  • 11:15-11:30: Decider's supervote and rumble vs all-in-one call
  • 11:30-12:30: Storyboard framing (which panels matter most; which map steps to cover; storyboard scope)
  • 12:30-13:30: Lunch
  • 13:30-16:30: Storyboard build (Facilitator drives; team contributes panel content; storyboard reaches 5-15 panels)
  • 16:30-17:00: Day-end review; Thursday build kickoff prep (who builds, who supports, what tools, what gets prebuilt overnight)
This skill's 210-minute timebox covers the Facilitator-led portions (heat map setup, critique, straw poll, supervote, storyboard build).
周三的完整工作坊约7小时（09:00-12:30 + 13:30-17:00）。整合成果将在当天逐步产出：
  • 09:00-09:15：开场欢迎 + 周二内容回顾 + 周三议程介绍
  • 09:15-09:30：美术馆布局搭建；主持人确认草图已去除署名并标记为A/B/C/D
  • 09:30-09:45：热力图投票（无声；15分钟；团队为有吸引力的部分贴点）
  • 09:45-10:45：快速评审（每张草图3分钟；草图作者在自己作品的评审环节保持沉默）
  • 10:45-11:00：休息
  • 11:00-11:15：意向投票（无声；每人在自己的选择上贴1个大点）
  • 11:15-11:30：决策者超级投票及二选一或全合一决策
  • 11:30-12:30：故事板框架确定（哪些面板最重要；涵盖哪些步骤；故事板范围）
  • 12:30-13:30：午餐
  • 13:30-16:30：故事板制作（主持人主导；团队贡献面板内容；故事板达到5-15个面板）
  • 16:30-17:00：当日复盘；周四原型制作启动准备（谁负责制作，谁提供支持，使用什么工具，哪些内容需提前准备）
该流程的210分钟时间框涵盖主持人主导的环节（热力图搭建、评审、意向投票、超级投票、故事板制作）。

Common Pitfalls

常见误区

  • Consensus drift instead of Decider supervote. The most common failure: the team votes, the Facilitator averages, and the Decider rubber-stamps the average. The Decider's call is the Decider's call; the straw poll is input, not result.
  • Storyboard too vague. "User captures a book" is not a storyboard panel; "user opens camera surface, points at book held at arm's length, sees recognized cover appear in bottom card within 1.5 seconds, taps the card to commit" is. Vague storyboards force Thursday's builders to re-debate design.
  • Skipping critique to save time. Critique surfaces concerns the storyboard must address. Skipping it produces a storyboard that hits Thursday and immediately re-surfaces every concern that should have been addressed Wednesday.
  • Sketcher explaining their own sketch. During critique, the sketcher is silent. The point is to test whether the sketch communicates without the artist. If the team can't read the sketch, that's data, not a bug.
  • Rumble chosen when all-in-one was right (or vice versa). Rumble is appropriate when 2 distinct supervoted approaches are both worth testing AND the team has Thursday capacity to build 2 prototypes. Default is all-in-one. Rumble is exception, not norm.
  • Storyboard scope too broad. 5-15 panels, not 50. The storyboard covers the target moment (from Monday) plus 1-2 panels of setup and 1-2 panels of outcome; it does NOT cover the full product.
  • 用共识平均值替代决策者超级投票：最常见的失误是团队投票后，主持人取平均值，决策者仅象征性批准。决策者的决定就是最终决定；意向投票只是输入，而非结果。
  • 故事板过于模糊：“用户获取一本书”不是合格的故事板面板；“用户打开相机界面，将镜头对准一臂距离外的书，1.5秒内底部卡片显示识别出的封面，点击卡片确认”才是。模糊的故事板会迫使周四的制作人员重新讨论设计。
  • 为节省时间跳过评审：评审会暴露故事板必须解决的问题。跳过评审会导致故事板在周四制作时，所有本应在周三解决的问题重新浮现。
  • 草图作者解释自己的作品：评审环节中，草图作者需保持沉默。目的是测试草图无需作者解释是否能传达信息。如果团队无法理解草图，这是有效数据，而非问题。
  • 错误选择二选一或全合一模式：只有当两种不同的超级投票方案都值得测试，且团队周四有能力制作两个原型时，才适合选择二选一模式。默认选项是全合一，二选一属于例外情况，非常规操作。
  • 故事板范围过宽：应是5-15个面板，而非50个。故事板需涵盖周一确定的目标场景，加上1-2个准备环节面板和1-2个结果面板；无需覆盖整个产品。

Cross-Skill Usage

跨流程关联

Prerequisites: 
tool-design-sprint-sketch
. Decide and Storyboard consumes Tuesday's sketches as input. Without independent sketches, this skill has no material to heat-map.
This skill invokes 
tool-note-and-vote
twice during the morning: once for the heat-map (small-dot voting) and once for the straw poll (large-dot voting). The supervote itself is the Decider's call after seeing both vote distributions; it does NOT delegate to note-and-vote.
Next invocation in the sprint: 
tool-design-sprint-prototype-plan
Thursday morning.
前置条件：
tool-design-sprint-sketch
流程。决策与故事板流程以周二的草图为输入。没有独立的草图，该流程就没有可进行热力图投票的素材。
该流程在上午会调用两次
tool-note-and-vote
：一次用于热力图投票（小点投票），一次用于意向投票（大点投票）。超级投票是决策者在查看两次投票结果后做出的决定；不委托给
tool-note-and-vote
流程。
冲刺中的下一个调用流程：周四上午的
tool-design-sprint-prototype-plan
。

Canonical Sources

权威来源

Decider Checkpoint

决策者检查点

This skill ends with a Decider Checkpoint in 
references/TEMPLATE.md
. The Decider's supervote earlier in the day is the substantive decision; the end-of-day checkpoint confirms the storyboard is build-ready (specific enough; covers the target moment plus setup plus outcome panels; no remaining hand-waving). Without sign-off, Thursday's build begins with ambiguity and Friday's test risks being a test of the wrong artifact.
该流程的结尾是
references/TEMPLATE.md
中的决策者检查点。当天早些时候的超级投票是实质性决策；当日结束时的检查点需确认故事板已准备好用于制作（内容足够具体；涵盖目标场景、准备环节和结果面板；没有模糊不清的内容）。若未获得签字确认，周四的制作将存在歧义，周五的测试可能会针对错误的成果进行。