Back to Details

tool-design-sprint-sketch

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 Sketch (Tuesday)

设计冲刺草图绘制（周二）

Structure Tuesday's solo-but-together work. Each team member, working independently and silently, produces lightning demos in the morning and a four-step solution sketch in the afternoon. The skill structures the activity; the humans produce the sketches. Wednesday's heat-map orientation depends on having a cohort of independent sketches that did NOT contaminate each other through group brainstorming.
Family contract: 
docs/reference/skill-families/design-sprint-skills-contract.md
. This skill is a member of 
design-sprint-skills
.
统筹周二“独自协作”的工作内容。每位团队成员独立、安静地完成上午的闪电演示（lightning demos）和下午的四步方案草图绘制。该Skill负责规划活动流程，草图由团队成员完成。周三的热图评审依赖于一组未受头脑风暴干扰的独立草图。
家族协议：
docs/reference/skill-families/design-sprint-skills-contract.md
。本Skill属于
design-sprint-skills
家族。

When to Use

使用时机

  • It is Day 2 of the Design Sprint and Monday's Map and Target artifact is signed off.
  • Each team member brings at least 3 lightning demo sources (existing products, references, analogies that bear on the challenge).
  • The team has accepted the silent-independent-sketching constraint and will NOT lapse into group brainstorming.
  • Sketches are due Tuesday end-of-day for Wednesday morning heat-map.
  • 处于Design Sprint的第二天，且周一的“地图与目标”工件已签字确认。
  • 每位团队成员至少准备3个闪电演示素材（与当前挑战相关的现有产品、参考案例、类比方案）。
  • 团队已接受“安静独立绘制草图”的约束，不会陷入集体头脑风暴。
  • 草图需在周二结束前完成，用于周三上午的热图评审。

When NOT to Use

不适用场景

  • Monday is not closed. Return to 
    tool-design-sprint-map-and-target
    .
  • The team's instinct is to brainstorm as a group. Sprint method explicitly avoids this; if the team will not commit to independent work, the sprint will not produce diverse sketches and the heat-map becomes a popularity contest.
  • The sketch step is being treated as the prototype. Sketches are concept exploration on paper or Figma frames, not Thursday's working prototype.
  • Sketches are due Tuesday morning. Tuesday is the full day; rushing to lunch produces sketches the team cannot read Wednesday.
  • 周一的流程未收尾。请返回
    tool-design-sprint-map-and-target
    环节。
  • 团队倾向于集体头脑风暴。Design Sprint方法明确禁止这种做法；如果团队无法承诺独立工作，冲刺将无法产出多样化的草图，热图评审会沦为人气比拼。
  • 将草图环节当作原型制作。草图是在纸上或Figma框架中进行的概念探索，而非周四要制作的可工作原型。
  • 要求草图在周二上午完成。周二是完整的一天，仓促赶工到午餐时间会导致周三团队无法读懂草图。

What This Skill Produces

本Skill产出内容

A single bundled artifact with four sections:
  1. Lightning demo board: each team member presents 3 demos (3 minutes each); the Facilitator extracts the reusable pattern from each demo into a one-line note. Result is a board with 12-21 patterns (4-7 team members x 3 demos).
  2. Sketch assignment plan: divide (each person sketches a different part of the target moment) or swarm (everyone sketches the same target). Default is swarm for v0.1 Design Sprints; divide is for teams running their second sprint with the same target who want to broaden coverage.
  3. Four-step sketches from each team member: Notes (20 min reviewing Monday output + lightning demos), Ideas (20 min rough doodles), Crazy 8s (8 minutes, 8 variations of the strongest Idea), Solution Sketch (30-90 min final 3-panel storyboard-style sketch).
  4. Recruiting tracker update: Riley (or the recruiter) confirms Friday slots; surfaces any cancellations and triggers buffer-slot activation if needed.
See 
references/TEMPLATE.md
for the canonical structure and 
references/EXAMPLE.md
for the Brainshelf book-catalog Tuesday artifact.
包含四个部分的整合工件：
  1. 闪电演示看板：每位团队成员展示3个演示（每个3分钟）；主持人从每个演示中提炼出可复用的模式，写成一行笔记。最终看板包含12-21个模式（4-7名团队成员 × 3个演示）。
  2. 草图分配计划：分为拆分模式（每人绘制目标环节的不同部分）或集群模式（所有人绘制同一目标）。0.1版Design Sprint默认采用集群模式；拆分模式适用于针对同一目标开展第二次冲刺、希望扩大覆盖范围的团队。
  3. 每位团队成员的四步草图：记录（20分钟回顾周一产出+闪电演示）、想法（20分钟粗略涂鸦）、疯狂8图（Crazy 8s，8分钟，针对最成熟的想法绘制8种变体）、方案草图（Solution Sketch，30-90分钟完成最终的3格故事板风格草图）。
  4. 招聘跟踪表更新：Riley（或招聘人员）确认周五的测试名额；同步任何取消情况，必要时启动备用名额。
规范结构请参考
references/TEMPLATE.md
，Brainshelf图书目录的周二工件示例请参考
references/EXAMPLE.md
。

Tuesday Time Structure

周二时间安排

The full Tuesday 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 + Monday recap + Tuesday agenda
  • 09:15-10:45: Lightning demos (each person 3 demos x 3 min + 1 min Facilitator extraction = ~12 min per person; 4-person team = ~50 min; 7-person team = ~85 min)
  • 10:45-11:00: Break
  • 11:00-11:30: Sketch assignment plan + Notes step (each person silently reviews Monday output and lightning demo board)
  • 11:30-12:30: Ideas step (each person silently doodles ideas in their notebook or Figma frame)
  • 12:30-13:30: Lunch + (in parallel) recruiting tracker check-in
  • 13:30-13:40: Crazy 8s (8 minutes, 8 variations of strongest Idea)
  • 13:40-15:30: Solution Sketch (final 3-panel sketch; everyone silent; Facilitator times)
  • 15:30-15:45: Break
  • 15:45-16:30: Sketches collected + named + photographed for Wednesday board; sketcher attribution hidden (Wednesday's heat-map is blind)
  • 16:30-17:00: Day-end check-in; confirm sketches uploaded; confirm Wednesday morning attendance
This skill's 180-minute timebox covers the Facilitator-led portions (lightning demos + assignment + collection). The silent sketch steps (Notes, Ideas, Crazy 8s, Solution Sketch) are individual work and run in parallel; the team is together in the room (or video call) but not collaborating.
完整的周二工作坊约7小时（09:00-12:30 + 13:30-17:00）。本Skill的整合工件将在当天逐步产出：
  • 09:00-09:15：开场+周一内容回顾+周二议程介绍
  • 09:15-10:45：闪电演示（每人3个演示×3分钟 + 1分钟主持人提炼 = 每人约12分钟；4人团队约50分钟；7人团队约85分钟）
  • 10:45-11:00：休息
  • 11:00-11:30：草图分配计划+记录环节（每人安静回顾周一产出和闪电演示看板）
  • 11:30-12:30：想法环节（每人在笔记本或Figma框架中安静涂鸦想法）
  • 12:30-13:30：午餐+（同步进行）招聘跟踪表核对
  • 13:30-13:40：疯狂8图（Crazy 8s，8分钟，绘制最成熟想法的8种变体）
  • 13:40-15:30：方案草图（最终3格草图；全程安静；主持人计时）
  • 15:30-15:45：休息
  • 15:45-16:30：收集草图+命名+拍照用于周三看板；隐藏绘制者信息（周三热图评审为匿名）
  • 16:30-17:00：当日收尾检查；确认草图已上传；确认周三上午参会情况
本Skill的180分钟时间盒涵盖主持人主导的环节（闪电演示+分配+收集）。安静绘制草图的环节（记录、想法、疯狂8图、方案草图）为独立工作，团队成员在同一房间（或视频会议）但不协作。

Common Pitfalls

常见误区

  • Group brainstorming. The single most common failure mode. The Sprint method explicitly forbids group sketching because it produces sketches that converge on the loudest voice, not the best idea. Facilitator's job is to enforce silence during sketch steps.
  • Sketches not concrete enough. A solution sketch must be understandable Wednesday morning WITHOUT the artist explaining it. If the heat-map team has to ask "what is this?", the sketch failed the readability bar.
  • Skipping lightning demos. Lightning demos are not optional warm-up; they inject outside patterns the team would not have generated. Skipping them produces inward-looking sketches.
  • Demo facilitator failing to extract reusable patterns. Each demo's reusable pattern must be captured (not the whole demo). "Spotify's home screen" is not a pattern; "feed of personalized cards with one-tap action" is.
  • Sketching the prototype. The solution sketch is a concept; the prototype is Thursday's build. Sketches that try to be the prototype are over-detailed in the wrong dimensions (visual polish, copy) and under-detailed in the right ones (interaction sequence, user reaction).
  • Sketcher attribution leaked into Wednesday heat-map. Wednesday's heat-map is blind (no sketcher names visible) so the team votes on the sketch, not the sketcher. If sketches arrive on Wednesday with names attached, the Facilitator strips them.
  • 集体头脑风暴：最常见的失败模式。Design Sprint方法明确禁止集体绘制草图，因为这会导致草图向声音最大的人的想法靠拢，而非最优方案。主持人的职责是在草图环节维持安静。
  • 草图不够具体：方案草图必须在周三上午无需绘制者解释就能被理解。如果热图评审团队需要问“这是什么？”，说明草图未达到可读性要求。
  • 跳过闪电演示：闪电演示并非可选的热身环节；它能为团队注入自身无法想到的外部模式。跳过会导致草图过于内向化。
  • 演示主持人未提炼可复用模式：必须捕捉每个演示的可复用模式（而非整个演示内容）。“Spotify的主页”不是模式；“带有一键操作的个性化卡片信息流”才是。
  • 将草图当作原型：方案草图是概念，原型是周四要制作的成品。试图充当原型的草图会在错误维度过度细化（视觉打磨、文案），而在正确维度（交互流程、用户反应）细化不足。
  • 绘制者信息泄露到周三热图评审：周三的热图评审为匿名（不显示绘制者姓名），以便团队基于草图本身投票，而非绘制者。如果草图在周三提交时带有姓名，主持人需将其移除。

Cross-Skill Usage

跨Skill使用

Prerequisites: 
tool-design-sprint-map-and-target
. Sketch consumes Monday's target moment as the design target for the four-step sketch protocol. Without a target moment, sketches diverge with no shared direction.
This skill does NOT invoke 
tool-note-and-vote
. Tuesday has no voting moment; all voting happens Wednesday after sketches are produced.
Next invocation in the sprint: 
tool-design-sprint-decide-and-storyboard
Wednesday morning.
前置Skill：
tool-design-sprint-map-and-target
。草图绘制环节将周一的目标环节作为四步草图流程的设计目标。没有目标环节，草图会偏离统一方向。
本Skill不会调用
tool-note-and-vote
。周二没有投票环节；所有投票都在周三产出草图后进行。
冲刺中的下一个调用Skill：周三上午的
tool-design-sprint-decide-and-storyboard
。

Canonical Sources

权威来源

Decider Checkpoint

决策者检查点

This skill ends with a Decider Checkpoint in 
references/TEMPLATE.md
. There is NO mid-day Tuesday decision; the Decider's role Tuesday is to be a sketcher among other sketchers (the Decider sketches independently like everyone else). The end-of-Tuesday Decider Checkpoint is a logistics confirmation: all sketches collected, attribution stripped, Wednesday morning attendance confirmed. The substantive Decider call comes Wednesday morning at the supervote.
本Skill在
references/TEMPLATE.md
中设有决策者检查点。周二中途无需决策；决策者在周二的角色是与其他成员一样独立绘制草图。周二结束时的决策者检查点是后勤确认：所有草图已收集、绘制者信息已移除、周三上午参会情况已确认。实质性的决策将在周三上午的超级投票环节做出。