---
title: "Design Sprint Decide and Storyboard: Storevine Brief Interface Validation"
description: "Storevine Wednesday artifact: 4 sketches heat-mapped, Mei supervotes a Sketch A + D hybrid via rumble decision, 7-panel storyboard from Monday email open through Tuesday action-taken."
artifact: design-sprint-decide-and-storyboard
version: "1.0"
repo_version: "2.15.0"
skill_version: "0.1.0"
created: 2026-05-16
status: sample
thread: storevine
context: "Storevine specialty-retail managed-intelligence service; Design Sprint week of 2026-07-13 testing Monday brief comprehension + actionability + trust after 4-week design-partner pilot"
---

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->

## Scenario

Wednesday 2026-07-15. Tuesday closed with 4 sketches uploaded as A/B/C/D to Storevine shared workspace. The team invokes `tool-design-sprint-decide-and-storyboard`. This is one of the rare cases where the Decider chooses rumble - testing two distinct sketches because Sketch A and Sketch D both validate from different angles and the team has Thursday capacity.

## Art Museum Layout

Shared Figma frame; 4 sketches A/B/C/D side-by-side. Attribution stripped (sketch metadata removed; viewing order randomized).

## Heat Map

3 dots per voter (4 voters x 3 = 12 total).

| Sketch | Dots | Hottest elements |
|---|---|---|
| Sketch A | 4 | Named-analyst attribution; subject line = top action |
| Sketch B | 3 | Card-stack visual; mobile-first |
| Sketch C | 1 | Quantified $-impact per action |
| Sketch D | 4 | "What changed" narrative lead; PDF/web split |

## Speed Critique Notes

### Sketch A

**What the team sees:** Trust-through-analyst-attribution. Subject line carries the top action so even unopened email delivers the lead. Carlos's name + photo is the credibility signal.

**Compelling:** Subject-line top-action; named attribution.

**What would worry me:** Doesn't scale beyond Carlos (need named-analyst for every customer); subject-line action assumes context we may not have.

### Sketch B

**What the team sees:** Mobile-first card-stack. Web companion = primary, PDF = secondary. Visual-led.

**Compelling:** Card stack; mobile-first.

**What would worry me:** Card-stack may add visual friction in the first-30-sec scan; web companion as primary may fragment if email open is the canonical entry point.

### Sketch C

**What the team sees:** Severity-badge prioritization with $-impact. PDF-only rejects fragmentation.

**Compelling:** $-impact projection.

**What would worry me:** $-impact projections are hard to validate operationally (off by 20% = trust break); severity badges may feel manipulative; PDF-only loses drill-down value.

### Sketch D

**What the team sees:** Narrative-led ("what changed"); clear PDF/web role split.

**Compelling:** Narrative lead; PDF/web split clarity.

**What would worry me:** Narrative lead may slow first-30-sec scan (worried merchandiser reads narrative, not actions); web companion drill-down only is restrictive.

## Straw Poll

| Voter | Pick |
|---|---|
| Mei | A |
| Tasha | D |
| Devon | C |
| Carlos | A |

## Supervote

**Decider:** Mei.

**Supervote placement:** 2 dots on Sketch A + 1 dot on Sketch D. Rumble.

**Decider's rationale:** Mei chose rumble because Sketch A and Sketch D test different first-30-sec hypotheses (A: subject-line action delivery + named-analyst trust; D: narrative-led "what changed" + PDF/web split). If first-30-sec scan is the question, testing both gives the strongest signal. Team capacity Thursday is sufficient (Tasha can build 2 Figma frame sets with Devon supporting). Carlos will run interview Tasks act with both prototypes shown in counterbalanced order.

## Rumble vs All-in-One

**Decision:** Rumble (Sketch A + Sketch D).

## Storyboard

7 panels covering email-open through Tuesday action-taken; ONE storyboard with branches for the 2 prototypes.

| Panel | What customer sees | Action | Response | Notes |
|---|---|---|---|---|
| 1 | Mon 07:30 AM phone; email subject (Sketch A: "Monday: 3 actions..."; Sketch D: "Monday Brief - Week of Jul 13") | Opens email | Body loads | Subject lines differ between prototypes |
| 2 | Email body (Sketch A: top action sentence + 2-more link; Sketch D: "What changed" narrative + 3-bullet action list) | Reads | - | First-30-sec scan moment is here |
| 3 | Taps PDF attachment OR web companion link | Tap | Opens | Counterbalance which gets tapped first |
| 4 | PDF view (Sketch A: numbered cards + analyst sidebar; Sketch D: same cards + deeper analyst commentary) | Scrolls | - | |
| 5 | Web companion (Sketch A: deeper drill-down per action; Sketch D: drill-down only) | Taps action | Opens drill-down | |
| 6 | Tue 09:00 AM: returns to phone email; "thinking about action #1" | Re-opens brief | - | Recall moment |
| 7 | Takes action #1 (calls supplier or updates POS order) | Action taken | - | Payoff |

## Decider Checkpoint

- [x] Mei confirms rumble call (Sketch A + Sketch D)
- [x] Mei confirms 7-panel storyboard build-ready
- [x] Mei accepts the un-storyboarded concerns as known weaknesses
- [x] Mei commits Friday PM 14:00-18:00 PT

**Signed:** Mei (founder, PM/CEO), 2026-07-15 16:50 PT.