Home
cd ../playbooks
Product ManagementIntermediate

Storyboard (6-Frame Narrative)

Create a 6-frame visual storyboard (character → problem → "oh crap" moment → solution → "aha" moment → life after) — narrative for stakeholder alignment, concept reviews, and empathy-building.

60-90 minutes
By communitySource
#storyboard#narrative#visioning#empathy#storytelling#alignment

Your stakeholder pitch was a feature list and a wireframe — and the room was polite but unmoved. People remember stories, not specs. A 6-frame storyboard puts a person in the room: Sarah at 10pm, drowning in invoices, then 6pm three months later playing with her kids. Same product, completely different reaction. The arc does the work specs can't.

Who it's for: PMs pitching features, founders communicating vision, design leads building empathy, exec teams testing emotional resonance pre-build

Example

"Storyboard our SmartInvoice feature" → Frame 1 Sarah (35, freelance designer, 10 clients) → Frame 2 (8hr/mo chasing invoices) → Frame 3 ($5K overdue, anxious) → Frame 4 (discovers SmartInvoice) → Frame 5 (AI reminder works, $5K received!) → Frame 6 (6pm, kids, 50%→80% on-time)

CLAUDE.md Template

New here? 3-minute setup guide → | Already set up? Copy the template below.

# Storyboard (6-Frame Narrative)

Create a 6-frame visual narrative telling a user's journey from problem to solution. Build empathy, illustrate value, make abstract concepts concrete. Test if a solution resonates emotionally before building it.

Not a UI mockup. A storytelling tool that brings the human side to life.

## The 6-Frame Structure

1. **Main Character** — persona + context
2. **Problem Emerges** — challenge they face
3. **"Oh Crap" Moment** — escalation creates urgency
4. **Solution Appears** — your product/feature introduced
5. **"Aha" Moment** — breakthrough experience
6. **Life After** — improved state

## Why This Works

- **Emotional engagement** — stories create empathy specs can't
- **Concrete over abstract** — visual narrative makes vague tangible
- **Memorable** — stories beat feature lists
- **Alignment tool** — stakeholders can react and give feedback
- **Low-fidelity** — sketches work; doesn't need polished design

**Anti-patterns:** Not a user flow diagram. Not a feature demo. Not marketing copy.

## When to Use

**Use:** Pitching new product/feature, aligning teams on user value, testing emotional resonance, all-hands/investor vision, validating problem/solution fit pre-build.
**Don't use:** Technical implementation (use diagrams), trivial problems, as research replacement.

## Application

### Step 1: Gather Context

- Persona (`proto-persona`)
- Problem (`problem-statement`)
- Solution (`positioning-statement`)
- Desired outcome

Don't fabricate. Run discovery first if missing.

### Step 2: Answer 7 Storyboard Questions

1. Who is the main character experiencing this problem? (name, age, role, context)
2. Describe the problem or challenge.
3. Describe the "Oh Crap" moment — when problem creates major issue.
4. How is the solution introduced?
5. Describe the character using the solution and the "Aha" moment.
6. What is life like after using the solution?
7. Visual style? (default: fat-marker sharpie sketches, monochrome)

### Step 3: Write the 6-Frame Narrative

```markdown
**Frame 1: Introducing the Main Character**
- Sarah, 35, freelance graphic designer juggling 10 client projects from her home office

**Frame 2: The Problem Emerges**
- Drowning in invoice tracking — 8 hours/month chasing late payments via spreadsheets and email

**Frame 3: The 'Oh Crap' Moment**
- Major client's payment is 2 weeks overdue. Sarah forgot to follow up. Client has gone silent. Anxious about cash flow.

**Frame 4: The Solution Appears**
- Sarah discovers SmartInvoice on a designer forum. Skeptical but tries it.

**Frame 5: The 'Aha' Moment**
- Two days later: "Client XYZ just paid!" The AI-timed reminder worked. No awkward call. Relieved.

**Frame 6: Life After the Solution**
- 30 minutes/month on invoicing instead of 8 hours. Evenings reclaimed. Cash flow predictable. Anxiety gone.
```

### Step 4: Visualize Each Frame

For each frame: visual scene + mood + key details. Tools: DALL·E, MidJourney, hand sketches.

### Step 5: Test the Storyboard

1. Is the main character relatable to your target?
2. Is the problem visceral (people *feel* it)?
3. Is the "Oh Crap" moment real?
4. Is the solution introduction natural (not forced)?
5. Is the "Aha" moment believable?
6. Is the "after" state aspirational?

If any "no," revise.

## Common Pitfalls

1. **Generic persona** ("busy professional") → "Sarah, 35, freelance designer, 10 clients, hates admin"
2. **Weak problem** ("efficiency issues") → visceral with consequences ("missing family dinners, anxiety")
3. **Forced solution introduction** ("magically discovers") → realistic discovery (forum, colleague)
4. **Feature-centric "Aha"** ("loves the dashboard") → outcome-focused ("$5K received! Relieved.")
5. **Vague "after"** ("life is better") → specific ("leaves at 6pm, on-time payments 50%→80%")

## References

- `proto-persona` — main character
- `problem-statement` — Frame 2-3
- `positioning-statement` — Frame 4
- `jobs-to-be-done` — Frame 6 outcome

**External:**
- Joseph Campbell, *The Hero's Journey* (1949)
- Pixar story rules ("Once upon a time... Every day... Until one day...")
- Donald Miller, *Building a StoryBrand* (2017)
README.md

What This Does

Walks through 7 generative questions then drafts a 6-frame narrative (main character → problem → "oh crap" → solution → "aha" → after). Adds visualization guidance per frame (mood, tools, key details). Includes 5 stress tests for relatability, viscerality, and aspirational ending.

Pairs with proto-persona, problem-statement, positioning-statement, and jobs-to-be-done.


Quick Start

mkdir -p ~/Documents/Storyboard
mv ~/Downloads/CLAUDE.md ~/Documents/Storyboard/
cd ~/Documents/Storyboard
claude

Provide persona context, problem framing, and solution overview. Claude drafts the 6-frame narrative and stress-tests for emotional resonance.


The 6 Frames

Frame Purpose
1. Main Character Specific persona + context
2. Problem Emerges Daily friction shown viscerally
3. "Oh Crap" Moment Escalation — stakes go up
4. Solution Appears Realistic discovery, not magic
5. "Aha" Moment Outcome experienced, not features admired
6. Life After Concrete + aspirational improved state

Tips & Best Practices

  • Specific persona, not "busy professional." Sarah, 35, freelance designer beats anonymous user.
  • Visceral problem. "Missed family dinners, anxious about cash flow" beats "efficiency issues."
  • Realistic solution discovery. Forum recommendation or colleague mention beats "magically finds product."
  • Outcome-focused "Aha." "$5K received! Relieved" beats "loves the dashboard."
  • Concrete "after." "Leaves at 6pm, on-time payments 50%→80%" beats "life is better."

Common Pitfalls

  • Generic persona that no one identifies with
  • Weak problem that doesn't resonate emotionally
  • Forced or magical solution discovery
  • Feature-centric "aha" moment instead of outcome
  • Vague "life after" without specifics or aspiration

$Related Playbooks