Design Sprint Sketch

Purpose

The Design Sprint Sketch (also called Solution Sketch) is the deep-dive sketching step from the Google Ventures Design Sprint. After rapid ideation with Crazy Eights, each participant picks their strongest concept and develops it into a detailed, self-explanatory three-panel sketch. These sketches become the basis for the team's decision on what to prototype.

At a glance

How to run

1. Review inspiration (5 min): Participants silently review notes, Crazy Eights, and any research on the walls.
2. Sketch the solution (20 min): Each person creates a three-panel storyboard of their best idea on A4 paper. The sketch must be self-explanatory — no verbal pitch accompanies it. Add annotations, titles, and flow arrows.
3. Anonymise (2 min): Fold the name under or use a code so the art museum review is unbiased.
4. Post on the wall (3 min): All sketches go up for the subsequent "art museum" and dot-voting step.

Materials needed

• A4 or A3 paper
• Thick markers (Sharpie-style)
• Sticky notes for annotations
• Tape for posting on walls
• Dot stickers for subsequent voting

Pitfalls & common mistakes

• Over-designing: This is a concept sketch, not a wireframe. Discourage pixel-level detail.
• Verbal explanations: If the sketch needs a speech to make sense, it needs more annotations.
• Groupthink: Keep sketching individual and silent — no peeking.
• Skipping the storyboard structure: Three panels (beginning, middle, end) tell a story; a single screen does not.

Inclusion & accessibility

• Stress that drawing skill is irrelevant — boxes, arrows, and words are fine.
• Offer lined templates for participants who find blank paper intimidating.
• Allow digital sketching for remote participants.
• Provide extra time for participants with motor impairments.

Variations

• Single-panel sketch: For simpler problems, one detailed panel may suffice.
• Collaborative sketch: Pairs co-create a sketch (sacrifices individual diversity).
• Digital-first: Use Figma or Miro with a three-frame template.

When NOT to use this

• When the problem is not yet framed — run How Might We or problem definition first.
• When the group has not done any divergent ideation — Crazy Eights should precede this.
• When time does not allow for the full sketch-review-vote cycle.

Source & further reading

• Jake Knapp, *Sprint* (2016)
• Google Design Sprint methodology
• AJ&Smart Sprint tutorials