storyboard
Six-frame visual narrative that guides stakeholders through a user's problem-to-solution journey.
- Follows a classic storytelling arc: introduce character, escalate problem, trigger urgency, reveal solution, show breakthrough, and illustrate improved outcome
- Designed for alignment meetings, feature pitches, and concept validation rather than UI mockups or technical documentation
- Requires upfront clarity on persona, problem statement, and solution definition; includes seven guided questions to develop authentic narrative
- Emphasizes emotional resonance and concrete outcomes over feature lists; includes anti-patterns and testing checklist to avoid generic personas and forced solution introductions
Purpose
Create a 6-frame visual narrative that tells the story of a user's journey from problem to solution, using the classic storytelling arc to build empathy, illustrate value, and make abstract product concepts concrete. Use this to align stakeholders, pitch features, communicate vision, or test if your solution resonates emotionally before building it.
This is not a UI mockup—it's a storytelling tool that brings the human side of your product to life.
Key Concepts
The 6-Frame Storyboard Structure
Based on classic narrative arcs, the 6-frame format follows this pattern:
- Frame 1: Main Character — Introduce the persona and their context
- Frame 2: The Problem Emerges — Show the challenge or obstacle they face
- Frame 3: The "Oh Crap" Moment — Escalate the problem to create urgency
- Frame 4: The Solution Appears — Introduce your product/feature
- Frame 5: The "Aha" Moment — Show the user experiencing the breakthrough
- Frame 6: Life After the Solution — Illustrate the improved state
Why This Works
More from deanpeters/product-manager-skills
prd-development
Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.
1.7Kuser-story
Create user stories with Mike Cohn format and Gherkin acceptance criteria. Use when turning user needs into development-ready work with clear outcomes and testable conditions.
1.7Kroadmap-planning
Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing. Use when turning strategy into a release plan that teams can execute.
1.5Kcompany-research
Create a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.
1.3Kproduct-strategy-session
Run an end-to-end product strategy session across positioning, discovery, and roadmap planning. Use when a team needs validated direction before committing to execution.
1.2Kprioritization-advisor
Choose a prioritization framework based on stage, team context, and stakeholder needs. Use when deciding between RICE, ICE, value/effort, or another scoring approach.
1.1K