tool-design-sprint-decide-and-storyboard

Runs Design Sprint Day 3 voting, critique, supervote, and storyboard production.

640|81|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/product-on-purpose/pm-skills --skill tool-design-sprint-decide-and-storyboard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tool-design-sprint-decide-and-storyboard
Source: https://github.com/product-on-purpose/pm-skills/tree/main/skills/tool-design-sprint-decide-and-storyboard
Command: npx skills add https://github.com/product-on-purpose/pm-skills --skill tool-design-sprint-decide-and-storyboard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Design Sprint teams often stall on Wednesday when deciding which solution sketch to prototype, defaulting to consensus averaging or endless debate instead of a clear Decider call. This Skill structures Day 3 of a Design Sprint so the team moves from Tuesday's sketches to a build-ready storyboard in one day.

Core Features & Use Cases

  • Structured decision sequence: Runs the art museum layout, silent heat map dot-voting, 3-minute speed critiques per sketch, straw poll, and the Decider's supervote, plus the rumble-vs-all-in-one call.
  • Storyboard production: Guides the team to a 5-15 panel storyboard covering the target moment plus setup and outcome panels, specific enough that Thursday's prototype build starts without re-debating design.
  • Templates and worked example: Ships a canonical artifact template and a complete Brainshelf book-catalog example showing heat map results, critique notes, supervote rationale, and a 9-panel storyboard.
  • Use Case: A product team finishing Tuesday's sketching session uses this Skill Wednesday morning to vote on four anonymized sketches, capture the Decider's supervote, and end the day with a locked storyboard that two builders can execute Thursday.

Quick Start

Run the Design Sprint Wednesday decide-and-storyboard session using Tuesday's four attribution-stripped sketches and produce the storyboard artifact from the template.

Frequently Asked Questions about tool-design-sprint-decide-and-storyboard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Design Sprint Wednesday decide and storyboard?

Post Tuesday's sketches anonymously in an art museum layout, run a silent heat map with 3 dots per voter, do 3-minute speed critiques per sketch, hold a straw poll, then have the Decider place the supervote. Finish by building a 5-15 panel storyboard that drives Thursday's prototype.

What is the difference between straw poll and supervote in a design sprint?

The straw poll is a non-binding vote where each team member places one large dot on their preferred sketch to inform the Decider. The supervote is the Decider's binding call that determines which sketch gets storyboarded; it is not a consensus average.

When should I choose rumble vs all-in-one in a design sprint?

Choose all-in-one (one storyboarded prototype) as the default. Choose rumble only when supervotes split clearly across two distinct approaches and the team has Thursday capacity to build two prototypes for Friday's interviews.

What happens if the Decider is absent on Design Sprint Wednesday?

The supervote cannot be delegated, so without the Decider the day produces a recommendation rather than a decision. The Skill explicitly lists an absent Decider as a when-not-to-use condition.

How many panels should a design sprint storyboard have?

The storyboard should contain 5-15 panels covering the target moment plus 1-2 setup panels and 1-2 outcome panels. Broader scope forces Thursday's builders to re-debate design instead of building.