tool-design-sprint-sketch
This skill structures Tuesday's independent solution-sketching phase of a Design Sprint, guiding each team member through lightning demos and a four-step sketch protocol (Notes, Ideas, Crazy 8s, Solution Sketch) without group brainstorming. Use it after Monday's Map and Target is approved and the team commits to silent, individual work, producing a lightning demo board and cohort of uncontaminated sketches for Wednesday's heat-map evaluation.
git clone --depth 1 https://github.com/product-on-purpose/pm-skills /tmp/tool-design-sprint-sketch && cp -r /tmp/tool-design-sprint-sketch/skills/tool-design-sprint-sketch ~/.claude/skills/tool-design-sprint-sketchSKILL.md
<!-- 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`](../../docs/reference/skill-families/design-sprint-skills-contract.md). This skill is a member of `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. ## 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. ## What This Skill Produces 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. ## 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. ## 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. ## Cross-Skill Usage 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
Run an ad-hoc ordered chain of pm-skills with shared context (ephemeral; routes to the pm-workflow-orchestrator)
Defines a testable hypothesis with clear success metrics and a validation approach. Use when forming assumptions to test or aligning a team on what success looks like, before any experiment is designed. To design the A/B test or experiment that will validate the hypothesis, use measure-experiment-design.
Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job. Use when deeply understanding customer motivations, designing for jobs, or reframing product positioning.
Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery. Use when structuring scattered feature ideas or communicating how the roadmap traces to outcomes. For ranking an existing flat list of candidates, use define-prioritization-framework instead; this skill discovers the list, it does not score one.
Run applicable prioritization frameworks (RICE, ICE, MoSCoW, Weighted Scoring, Kano) against a list of features or initiatives. Produces a comparison table showing where rankings agree and diverge across frameworks, and an executive summary with recommendation. Framework applicability is filtered by data availability; Kano requires customer research. Refuses to fabricate scores; produces an estimation scaffold when input data is missing.
Creates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.
Generates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form. Use when turning requirements into verifiable scenarios for engineering handoff and QA sign-off. For a dedicated catalog of boundary conditions, error states, and recovery paths across a feature, use deliver-edge-cases; to write the stories themselves, use deliver-user-stories.
Documents edge cases, error states, boundary conditions, race conditions, and recovery paths for a feature - the systematic catalog of what can go wrong and the failure modes to design for. Use during specification to map the failure surface and ensure comprehensive coverage, or during QA planning to identify boundary and limit scenarios to test. Distinct from deliver-acceptance-criteria, which writes story-level Given/When/Then checks; this skill produces the whole-feature edge-case catalog.