Back to Details

storyboard

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

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.
创建一个6帧视觉叙事内容，讲述用户从遇到问题到获得解决方案的完整旅程，借助经典叙事结构建立共情、体现产品价值，并将抽象的产品概念具象化。可用于对齐利益相关者、推介功能、传达产品愿景，或在开发前测试你的解决方案是否能引发情感共鸣。
这不是UI原型——它是一种讲故事的工具，能展现产品人性化的一面。

Key Concepts

核心概念

The 6-Frame Storyboard Structure

6帧故事板结构

Based on classic narrative arcs, the 6-frame format follows this pattern:
  1. Frame 1: Main Character — Introduce the persona and their context
  2. Frame 2: The Problem Emerges — Show the challenge or obstacle they face
  3. Frame 3: The "Oh Crap" Moment — Escalate the problem to create urgency
  4. Frame 4: The Solution Appears — Introduce your product/feature
  5. Frame 5: The "Aha" Moment — Show the user experiencing the breakthrough
  6. Frame 6: Life After the Solution — Illustrate the improved state
基于经典叙事弧，6帧格式遵循以下模式：
  1. 第1帧：主角 — 介绍用户画像及其所处场景
  2. 第2帧：问题浮现 — 展示他们面临的挑战或障碍
  3. 第3帧：“糟糕”时刻 — 升级问题以制造紧迫感
  4. 第4帧：解决方案出现 — 介绍你的产品/功能
  5. 第5帧：“顿悟”时刻 — 展示用户体验到的突破
  6. 第6帧：使用解决方案后的生活 — 描绘状态的改善

Why This Works

为何这种方法有效

  • Emotional engagement: Stories create empathy in ways specs can't
  • Concrete over abstract: Visual narrative makes vague concepts tangible
  • Memorable: People remember stories better than feature lists
  • Alignment tool: Stakeholders can react to a story and give feedback
  • Low-fidelity: Doesn't require polished design—sketches work great
  • 情感共鸣： 故事能以规格文档无法做到的方式建立共情
  • 具象化抽象概念： 视觉叙事让模糊的概念变得具体
  • 易记忆： 人们对故事的记忆远胜于功能列表
  • 对齐工具： 利益相关者可以针对故事给出反馈
  • 低保真： 无需精致设计——草图就足够好

Anti-Patterns (What This Is NOT)

反模式（这不是什么）

  • Not a user flow diagram: This is emotional storytelling, not process documentation
  • Not a feature demo: Focus on user outcomes, not product capabilities
  • Not marketing copy: Authentic narrative, not hype
  • 不是用户流程图： 这是情感叙事，而非流程文档
  • 不是功能演示： 聚焦用户成果，而非产品能力
  • 不是营销文案： 是真实的叙事，而非夸大宣传

When to Use This

适用场景

  • Pitching a new product or feature to stakeholders
  • Aligning teams on user value (product, design, engineering, execs)
  • Testing if a product idea resonates emotionally
  • Communicating vision at all-hands or investor meetings
  • Validating problem/solution fit before building
  • 向利益相关者推介新产品或功能
  • 让团队（产品、设计、工程、高管）对齐用户价值
  • 测试产品想法是否能引发情感共鸣
  • 在全员会议或投资者会议上传达愿景
  • 在开发前验证问题与解决方案的匹配度

When NOT to Use This

不适用场景

  • For technical implementation details (use architecture diagrams instead)
  • When the user problem is trivial or well-understood
  • As a replacement for user research (storyboards illustrate insights, don't create them)
  • 用于技术实现细节（改用架构图）
  • 用户问题微不足道或已被充分理解时
  • 替代用户研究（故事板是展示研究洞察，而非生成洞察）

Application

实践步骤

Use 
template.md
for the full fill-in structure.
使用
template.md
获取完整的填充式结构。

Step 1: Gather Context

步骤1：收集背景信息

Before creating the storyboard, ensure you have:
  • Persona clarity: Who is the main character? (reference 
    skills/proto-persona/SKILL.md
    )
  • Problem understanding: What challenge do they face? (reference 
    skills/problem-statement/SKILL.md
    )
  • Solution definition: What product/feature will help? (reference 
    skills/positioning-statement/SKILL.md
    )
  • Desired outcome: What does success look like for the user?
If missing context: Run discovery work first. Don't fabricate personas or problems.
创建故事板前，确保你已明确：
  • 清晰的用户画像： 主角是谁？（参考
    skills/proto-persona/SKILL.md
    ）
  • 对问题的理解： 他们面临什么挑战？（参考
    skills/problem-statement/SKILL.md
    ）
  • 解决方案定义： 什么产品/功能能提供帮助？（参考
    skills/positioning-statement/SKILL.md
    ）
  • 期望成果： 用户的成功状态是什么样的？
如果缺少背景信息： 先开展探索性工作。不要编造用户画像或问题。

Step 2: Answer the 7 Storyboard Questions

步骤2：回答7个故事板问题

Ask these questions one at a time to develop the narrative:
  1. Who is the main character experiencing this problem? (Name, age, role, context)
  2. Describe the problem or challenge the main character is facing.
  3. Describe the "Oh Crap" moment where the problem creates a major issue.
  4. How is the solution introduced to the main character?
  5. Describe the main character using the solution and experiencing an "Aha" moment.
  6. What is life like for the main character after using the solution?
  7. Do you have any specific visual style or rendering instructions? (Default: fat-marker sharpie sketches, minimal and monochrome)
逐一回答以下问题来构建叙事：
  1. 谁是遇到这个问题的主角？（姓名、年龄、角色、场景）
  2. 描述主角面临的问题或挑战。
  3. 描述“糟糕”时刻，即问题升级为重大事件的节点。
  4. 解决方案是如何呈现在主角面前的？
  5. 描述主角使用解决方案并经历“顿悟”时刻的场景。
  6. 使用解决方案后，主角的生活变成了什么样？
  7. 你有特定的视觉风格或呈现要求吗？（默认：粗马克笔手绘草图，极简、单色）

Step 3: Write the 6-Frame Narrative

步骤3：撰写6帧叙事

Based on the answers above, draft the narrative:
markdown
undefined
基于上述答案，起草叙事内容：
markdown
undefined

Generated 6-Frame Storyline

生成的6帧故事线

Frame 1: Introducing the Main Character
  • [Insert description of the main character, their setting, and context]
  • [Example: "Sarah, 35, is a freelance graphic designer juggling 10 client projects from her home office"]
Frame 2: The Problem Emerges
  • [Describe the main character's challenge and how it affects their life]
  • [Example: "She's drowning in invoice tracking—8 hours per month chasing late payments via spreadsheets and email"]
Frame 3: The 'Oh Crap' Moment
  • [Highlight the escalation of the problem into a major issue]
  • [Example: "A major client's payment is 2 weeks overdue. Sarah realizes she forgot to follow up because she was focused on design work. The client has now gone silent, and she's anxious about cash flow."]
Frame 4: The Solution Appears
  • [Explain how the solution is introduced and the main character's initial reaction]
  • [Example: "Sarah discovers SmartInvoice, a tool that automatically sends payment reminders at optimal times. She's skeptical—will it sound too pushy?—but decides to try it."]
Frame 5: The 'Aha' Moment
  • [Show the main character using the solution and experiencing a breakthrough]
  • [Example: "Two days later, Sarah receives a notification: 'Client XYZ just paid!' The AI-timed reminder worked—no awkward follow-up call needed. She feels relieved and in control."]
Frame 6: Life After the Solution
  • [Describe the resolution and how life improves after overcoming the problem]
  • [Example: "Sarah now spends 30 minutes per month on invoicing instead of 8 hours. She's reclaimed her evenings, spending time with family instead of chasing payments. Her cash flow is predictable, and her anxiety is gone."]
Optional Visual Elements
  • [If no visual style specified: "Use fat-marker, sharpie-style sketches—minimal, monochrome, hand-drawn feel"]
  • [If visual elements provided: "Include user-provided images, GIFs, or icons"]

---
第1帧：介绍主角
  • [插入主角的描述、所处场景及背景]
  • [示例：“萨拉，35岁，自由平面设计师，在家办公，同时处理10个客户项目”]
第2帧：问题浮现
  • [描述主角的挑战及其对生活的影响]
  • [示例：“她在发票追踪上不堪重负——每月要花8小时通过表格和邮件追讨逾期付款”]
第3帧：“糟糕”时刻
  • [突出问题升级为重大事件的节点]
  • [示例：“一位重要客户的付款逾期2周。萨拉发现自己因为专注设计工作而忘记跟进，现在客户已经失联，她对现金流感到焦虑。”]
第4帧：解决方案出现
  • [说明解决方案如何被引入，以及主角的初始反应]
  • [示例：“萨拉发现了SmartInvoice，一款能在最佳时间自动发送付款提醒的工具。她持怀疑态度——会不会显得太催逼？——但还是决定尝试。”]
第5帧：“顿悟”时刻
  • [展示主角使用解决方案并体验到突破的场景]
  • [示例：“两天后，萨拉收到一条通知：‘客户XYZ已付款！’AI定时提醒奏效了——无需尴尬的跟进电话。她感到如释重负，重新掌控了局面。”]
第6帧：使用解决方案后的生活
  • [描述问题解决后的状态，以及生活如何改善]
  • [示例：“萨拉现在每月只花30分钟处理发票，而非之前的8小时。她重新夺回了夜晚的时间，不再追讨付款，而是陪伴家人。她的现金流变得稳定，焦虑也消失了。”]
可选视觉元素
  • [如果未指定视觉风格：“使用粗马克笔手绘草图——极简、单色，具有手绘质感”]
  • [如果提供了视觉元素：“包含用户提供的图片、GIF或图标”]

---

Step 4: Visualize Each Frame

步骤4：可视化每一帧

For each frame, create or describe the visual:
Frame 1: Main Character
  • Visual: Sarah at her desk, surrounded by sticky notes, laptop open, coffee cup
  • Mood: Busy, slightly stressed
  • Tools: DALL·E, MidJourney, hand-drawn sketches
Frame 2: The Problem Emerges
  • Visual: Sarah staring at a spreadsheet labeled "Overdue Invoices," multiple browser tabs open
  • Mood: Overwhelmed
  • Details: Clock showing 10pm, to-do list getting longer
Frame 3: The 'Oh Crap' Moment
  • Visual: Sarah's phone showing "Day 14: Payment Overdue from Client XYZ" notification. Her face shows worry.
  • Mood: Anxious, urgent
  • Details: Calendar showing upcoming rent due date
Frame 4: The Solution Appears
  • Visual: Sarah's laptop showing the SmartInvoice landing page with headline "Stop Chasing Payments"
  • Mood: Curious, hopeful
  • Details: Testimonial quote: "Saved me 5 hours/month"
Frame 5: The 'Aha' Moment
  • Visual: Sarah's phone showing notification "Client XYZ just paid! $5,000 received." She's smiling, relieved.
  • Mood: Joy, relief, empowerment
  • Details: Background shows sunset—she's done with work early
Frame 6: Life After the Solution
  • Visual: Sarah playing with her kids in the backyard, laptop closed on the patio table
  • Mood: Peaceful, balanced
  • Details: Clock showing 6pm (not 10pm anymore)
为每一帧创建或描述视觉内容：
第1帧：主角
  • 视觉： 萨拉坐在书桌前，周围贴满便签，笔记本电脑开着，旁边放着咖啡杯
  • 情绪： 忙碌，略带压力
  • 工具： DALL·E, MidJourney, 手绘草图
第2帧：问题浮现
  • 视觉： 萨拉盯着标有“逾期发票”的表格，浏览器打开多个标签页
  • 情绪： 不堪重负
  • 细节： 时钟显示晚上10点，待办事项列表越来越长
第3帧：“糟糕”时刻
  • 视觉： 萨拉的手机显示“第14天：客户XYZ付款逾期”的通知。她脸上露出担忧的神情。
  • 情绪： 焦虑、紧迫
  • 细节： 日历显示即将到来的交租日期
第4帧：解决方案出现
  • 视觉： 萨拉的笔记本电脑显示SmartInvoice的着陆页，标题为“停止追讨付款”
  • 情绪： 好奇、抱有希望
  • 细节： 客户评价：“每月为我节省5小时”
第5帧：“顿悟”时刻
  • 视觉： 萨拉的手机显示通知“客户XYZ已付款！到账5000美元”。她面带微笑，如释重负。
  • 情绪： 愉悦、释然、充满掌控感
  • 细节： 背景是日落——她提前完成了工作
第6帧：使用解决方案后的生活
  • 视觉： 萨拉在后院和孩子玩耍，笔记本电脑关在露台桌上
  • 情绪： 平静、平衡
  • 细节： 时钟显示下午6点（不再是晚上10点）

Step 5: Test the Storyboard

示例

Ask these questions:
  1. Is the main character relatable? Would your target persona recognize themselves?
  2. Is the problem visceral? Do people feel the frustration in Frame 2-3?
  3. Is the "Oh Crap" moment real? Does it escalate the problem authentically?
  4. Is the solution introduction natural? Or does it feel forced/contrived?
  5. Is the "Aha" moment believable? Can users imagine experiencing this?
  6. Is the "after" state aspirational? Would users want this outcome?
If any answer is "no," revise.
查看
examples/sample.md
获取完整的故事板示例。
迷你示例节选：
markdown
**第1帧：** 萨拉，35岁，自由设计师，同时处理10个客户项目\n**第2帧：** 每月花8小时追讨逾期发票\n**第3帧：** 5000美元付款逾期2周\n```

---

Examples

常见陷阱

—

陷阱1：通用用户画像

See 
examples/sample.md
for full storyboard examples.
Mini example excerpt:
markdown
**Frame 1:** Sarah, 35, freelance designer juggling 10 clients\n**Frame 2:** Spends 8 hours/month chasing overdue invoices\n**Frame 3:** $5,000 payment is 2 weeks overdue\n```

---
症状： “这位是用户，一位忙碌的职场人士”
后果： 没有人能与这个角色产生共鸣。
解决方法： 具体化：“这位是萨拉，35岁，自由设计师，同时处理10个客户项目，在家办公，热爱设计但讨厌行政工作。”

Common Pitfalls

陷阱2：薄弱的问题描述

Pitfall 1: Generic Persona

—
Symptom: "Meet User, a busy professional"
Consequence: No one identifies with this character.
Fix: Get specific: "Meet Sarah, 35, freelance designer, juggling 10 clients, home office, loves design but hates admin."
症状： “用户在效率方面有问题”
后果： 问题无法引发情感共鸣。
解决方法： 让问题更具象：“萨拉每月花8小时追讨逾期发票，错过家庭晚餐，对现金流感到焦虑。”

Pitfall 2: Weak Problem

陷阱3：生硬的解决方案引入

Symptom: "User has a problem with efficiency"
Consequence: Problem doesn't resonate emotionally.
Fix: Make it visceral: "Sarah spends 8 hours/month chasing overdue invoices, missing family dinners, feeling anxious about cash flow."
症状： “用户神奇地发现了我们的产品”
后果： 显得刻意，不真实。
解决方法： 展示真实的发现场景：“萨拉在设计师论坛看到推荐”或“萨拉的同事提到了这款产品。”

Pitfall 3: Forced Solution Introduction

陷阱4：以功能为中心的“顿悟”时刻

Symptom: "User magically discovers our product"
Consequence: Feels contrived, not authentic.
Fix: Show realistic discovery: "Sarah sees a recommendation in a designer forum" or "Sarah's colleague mentions it."
症状： “用户看到仪表盘后喜欢上了这些功能”
后果： 没有情感回报。
解决方法： 聚焦成果：“萨拉收到通知：‘到账5000美元！’她如释重负——无需尴尬的电话跟进。”

Pitfall 4: Feature-Centric "Aha" Moment

陷阱5：模糊的“之后”状态

Symptom: "User sees the dashboard and loves the features"
Consequence: No emotional payoff.
Fix: Focus on outcome: "Sarah gets notification: '$5,000 received!' She's relieved—no awkward call needed."
症状： “现在生活变好了”
后果： 缺乏吸引力和具体性。
解决方法： 具体化：“萨拉现在下午6点就下班了，晚上不再追讨客户，而是陪伴孩子。按时付款率从50%提升到80%。”

Pitfall 5: Vague "After" State

参考资料

—

相关技能

Symptom: "Life is better now"
Consequence: Not aspirational or concrete.
Fix: Be specific: "Sarah leaves work at 6pm now, spending evenings with her kids instead of chasing clients. On-time payments jumped from 50% to 80%."
  • skills/proto-persona/SKILL.md
    — 定义主角
  • skills/problem-statement/SKILL.md
    — 为第2-3帧构建问题框架
  • skills/positioning-statement/SKILL.md
    — 为第4帧的解决方案引入提供信息
  • skills/jobs-to-be-done/SKILL.md
    — 为第6帧的期望成果提供信息

References

外部框架

Related Skills

—
  • skills/proto-persona/SKILL.md
    — Defines the main character
  • skills/problem-statement/SKILL.md
    — Frames the problem for Frame 2-3
  • skills/positioning-statement/SKILL.md
    — Informs the solution introduction in Frame 4
  • skills/jobs-to-be-done/SKILL.md
    — Informs the desired outcome in Frame 6
  • Joseph Campbell, The Hero's Journey (1949) — 经典叙事结构
  • Pixar的故事规则 — “从前……每天……直到有一天……”
  • Donald Miller, Building a StoryBrand (2017) — 故事驱动的营销框架

External Frameworks

Dean的作品

  • Joseph Campbell, The Hero's Journey (1949) — Classic narrative structure
  • Pixar's story rules — "Once upon a time... Every day... Until one day..."
  • Donald Miller, Building a StoryBrand (2017) — Story-driven marketing frameworks
  • Storyboard Storytelling Prompt (6-Frame Storyline Generator)

Dean's Work

来源

  • Storyboard Storytelling Prompt (6-Frame Storyline Generator)
  • 改编自
    https://github.com/deanpeters/product-manager-prompts
    仓库中的
    prompts/storyboard-storytelling-prompt.md
技能类型： 组件 建议文件名： 
storyboard.md
建议存放位置： 
/skills/components/
依赖： 参考
skills/proto-persona/SKILL.md
, 
skills/problem-statement/SKILL.md
, 
skills/positioning-statement/SKILL.md
, 
skills/jobs-to-be-done/SKILL.md

Provenance

—
  • Adapted from 
    prompts/storyboard-storytelling-prompt.md
    in the 
    https://github.com/deanpeters/product-manager-prompts
    repo.
Skill type: Component Suggested filename: 
storyboard.md
Suggested placement: 
/skills/components/
Dependencies: References 
skills/proto-persona/SKILL.md
, 
skills/problem-statement/SKILL.md
, 
skills/positioning-statement/SKILL.md
, 
skills/jobs-to-be-done/SKILL.md
—