Back to Details

storyline-builder

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Storyline Builder

故事线构建工具

A structured approach to building presentation storylines where each line becomes one slide title, creating a logical narrative flow.
这是一种构建演示文稿故事线的结构化方法，每条故事线对应一个幻灯片标题，形成连贯的叙事逻辑。

What is a Storyline?

什么是故事线？

A storyline is the backbone of a presentation - a sequence of messages that tells a complete story. Each line in the storyline becomes one slide title in the final deck.
Key characteristics:
  • Each line = one slide title (action-oriented message)
  • Logical flow from problem → context → analysis → solution
  • Slide titles are the message, not topics
  • Reader should understand the story from titles alone
故事线是演示文稿的核心骨架——一系列能完整讲述一个故事的信息点。故事线中的每一条内容都会成为最终演示文稿中的一个幻灯片标题。
核心特征：
  • 每条内容 = 一个幻灯片标题（以行动为导向的信息）
  • 遵循从问题→背景→分析→解决方案的逻辑脉络
  • 幻灯片标题是核心信息，而非主题
  • 仅通过标题就能让读者理解完整故事

Core Principles

核心原则

Action Titles
  • Titles state the finding, not the topic
  • Good: "Market grew 40% while revenue declined 5%"
  • Bad: "Market Analysis"
Logical Progression
  • Paint the problem or opportunity
  • Provide context (market, competitive landscape)
  • Show data to prove/disprove hypotheses
  • Present solution and next steps
Story Flow
  • Problem → Context → Analysis → Solution → Roadmap
  • Each slide builds on the previous
  • Clear beginning, middle, end
行动导向标题
  • 标题陈述结论，而非主题
  • 正面示例：“市场增长40%，但收入下降5%”
  • 反面示例：“市场分析”
逻辑递进
  • 阐述问题或机遇
  • 提供背景信息（市场、竞争格局）
  • 展示数据以验证或推翻假设
  • 呈现解决方案与下一步行动
故事脉络
  • 问题→背景→分析→解决方案→路线图
  • 每张幻灯片都建立在前一张的基础上
  • 有清晰的开头、发展和结尾

Storyline Templates by Situation

不同场景的故事线模板

1. Market Strategy / Pitch Deck

1. 市场战略 / 推介PPT

Flow: Market opportunity → Competitive position → Product strategy → Go-forward plan
Storyline:
1. [Market name] represents $XXB opportunity growing at XX% CAGR
2. We operate in [specific segment] worth $XXB with XX% growth
3. Top 3 competitors generate $XXM-XXB revenue growing XX-XX% annually
4. Our revenue of $XXM positions us as [rank/position] with XX% growth
5. [Product name] addresses [use case] for [target customer segment]
6. Top 10 customers span [industries/sectors], XX% enterprise vs XX% SMB split
7. Pricing structured as [model type] with $XX average contract value
8. Product differentiation built on [technology/approach] vs competitors
9. Key competitive advantages: [advantage 1], [advantage 2], [advantage 3]
10. Three growth opportunities identified: [opp 1], [opp 2], [opp 3]
11. Focus on [priority opportunity] based on market size and competitive position
12. 18-month roadmap prioritizes [capability 1], [capability 2], [capability 3]
脉络：市场机遇→竞争地位→产品战略→未来规划
Storyline:
1. [市场名称]代表着XX十亿美元的机遇，年复合增长率为XX%
2. 我们深耕的细分市场规模达XX十亿美元，增长率为XX%
3. 头部3家竞争对手的年收入在XX百万至XX十亿美元之间，年增长率为XX-XX%
4. 我们的年收入为XX百万美元，在市场中位列[排名/定位]，年增长率为XX%
5. [产品名称]针对[目标客户群体]的[使用场景]提供解决方案
6. 我们的Top10客户覆盖[行业/领域]，其中企业客户占XX%，中小企业占XX%
7. 定价采用[模式类型]，平均合同价值为XX美元
8. 产品基于[技术/方法]构建差异化优势，领先于竞争对手
9. 核心竞争优势：[优势1]、[优势2]、[优势3]
10. 已识别三大增长机遇：[机遇1]、[机遇2]、[机遇3]
11. 基于市场规模与竞争地位，优先聚焦[重点机遇]
12. 18个月路线图优先推进[能力1]、[能力2]、[能力3]

2. Internal Problem-Solving (Issue Tree Format)

2. 内部问题解决（议题树格式）

Flow: Problem framing → Root cause analysis → Solution options → Prioritization → Next steps
Storyline:
1. [Problem statement] - current state at XX vs target of XX
2. Problem driven by three factors: [factor 1], [factor 2], [factor 3]
3. [Factor 1] contributes $XXM impact (XX% of total problem)
4. [Factor 2] contributes $XXM impact (XX% of total problem)
5. [Factor 3] contributes $XXM impact (XX% of total problem)
6. Root cause analysis reveals [key insight from data]
7. Three solution approaches identified to address root causes
8. Solution 1: [approach] - XX% impact, $XXM investment, XX weeks
9. Solution 2: [approach] - XX% impact, $XXM investment, XX weeks
10. Solution 3: [approach] - XX% impact, $XXM investment, XX weeks
11. Prioritize [solution X] based on impact/effort analysis
12. Implementation roadmap: [Phase 1 by date], [Phase 2 by date], [Phase 3 by date]
13. Success metrics: [metric 1], [metric 2], [metric 3] tracked [frequency]
脉络：问题界定→根本原因分析→解决方案选项→优先级排序→下一步行动
Storyline:
1. [问题陈述] - 当前状态为XX，目标为XX
2. 问题由三大因素驱动：[因素1]、[因素2]、[因素3]
3. [因素1]造成的影响达XX百万美元（占总问题的XX%）
4. [因素2]造成的影响达XX百万美元（占总问题的XX%）
5. [因素3]造成的影响达XX百万美元（占总问题的XX%）
6. 根本原因分析揭示了[数据得出的关键洞察]
7. 已确定三种解决根本原因的方案
8. 方案1：[方法] - 影响XX%，投资XX百万美元，耗时XX周
9. 方案2：[方法] - 影响XX%，投资XX百万美元，耗时XX周
10. 方案3：[方法] - 影响XX%，投资XX百万美元，耗时XX周
11. 基于影响/投入分析，优先选择[方案X]
12. 实施路线图：[阶段1截止日期]、[阶段2截止日期]、[阶段3截止日期]
13. 成功指标：[指标1]、[指标2]、[指标3]，跟踪频率为[频率]

3. Project Roadmap / Implementation Plan

3. 项目路线图 / 实施计划

Flow: Approach → Phases → Activities → Timeline → Success criteria
Storyline:
1. Project objective: [goal statement with measurable outcome]
2. Four-phase approach over XX weeks: Discovery → Design → Build → Launch
3. Project roadmap spans XX weeks with clear owners and milestones:
   - Phase 1 (Weeks 1-X): User research - XX interviews across [segments] | Owner: [role]
   - Phase 2 (Weeks X-X): Solution design - Define stories, sprint planning | Owner: [role]
   - Phase 3 (Weeks X-X): MVP build - [features] across XX sprints | Owner: [role]
   - Phase 4 (Weeks X-X): Launch - Onboard XX customers | Owner: [role]
4. Core team of XX across [# domains]: PM, Design, Engineering, [other] - Gap: Need [X more roles] and $XXK investment
5. Success criteria: [metric 1] = XX, [metric 2] = XX by [date]
6. ROI measurement: Track [business metric] over XX months
脉络：方法→阶段→活动→时间线→成功标准
Storyline:
1. 项目目标：[带有可衡量成果的目标陈述]
2. 采用四阶段方法，耗时XX周：发现→设计→构建→上线
3. 项目路线图跨度XX周，明确负责人与里程碑：
   - 阶段1（第1-X周）：用户研究 - 针对[群体]完成XX次访谈 | 负责人：[角色]
   - 阶段2（第X-X周）：解决方案设计 - 定义需求故事、冲刺规划 | 负责人：[角色]
   - 阶段3（第X-X周）：MVP构建 - 在XX个冲刺中完成[功能] | 负责人：[角色]
   - 阶段4（第X-X周）：上线 - 完成XX位客户的入驻 | 负责人：[角色]
4. 核心团队共XX人，涵盖[X个领域]：项目经理、设计、工程、[其他角色] - 缺口：需补充[X个岗位]及XX万美元投资
5. 成功标准：[指标1] = XX，[指标2] = XX，截止日期为[日期]
6. ROI测算：在XX个月内跟踪[业务指标]

How to Build a Storyline

如何构建故事线

Step 1: Identify the situation type
  • Market/strategy deck?
  • Problem-solving presentation?
  • Project roadmap?
  • Choose appropriate template
Step 2: Customize the flow
  • Replace placeholders with specific content
  • Add or remove slides based on story needs
  • Maintain logical progression
Step 3: Write action titles
  • Each line should be a complete message
  • Include data points and specifics
  • Test: Can someone understand your story from titles alone?
Step 4: Verify flow
  • Does it progress logically?
  • Are there gaps in the logic?
  • Does it lead to clear next steps?
Step 5: Build slides
  • Each storyline becomes one slide
  • Slide title = storyline
  • Slide body supports the title message
步骤1：确定场景类型
  • 市场/战略演示文稿？
  • 问题解决类演示文稿？
  • 项目路线图？
  • 选择合适的模板
步骤2：定制脉络
  • 用具体内容替换占位符
  • 根据故事需求添加或删除幻灯片
  • 保持逻辑递进
步骤3：撰写行动导向标题
  • 每条内容应是完整的信息
  • 包含数据点与具体细节
  • 测试：仅通过标题，他人能否理解你的故事？
步骤4：验证逻辑脉络
  • 逻辑递进是否顺畅？
  • 是否存在逻辑缺口？
  • 是否指向清晰的下一步行动？
步骤5：制作幻灯片
  • 每条故事线对应一张幻灯片
  • 幻灯片标题 = 故事线内容
  • 幻灯片正文为标题信息提供支撑

Common Storyline Patterns

常见故事线模式

Problem-to-Solution Arc
Problem statement → Problem sizing → Root causes → 
Solution options → Recommendation → Implementation plan
Market-to-Strategy Arc
Market opportunity → Competitive landscape → Our position → 
Product strategy → Roadmap → Expected outcomes
Analysis-to-Action Arc
Key question → Hypotheses → Data analysis → 
Insights → Recommendations → Next steps
问题到解决方案的脉络
问题陈述→问题规模界定→根本原因→
解决方案选项→推荐方案→实施计划
市场到战略的脉络
市场机遇→竞争格局→我们的定位→
产品战略→路线图→预期成果
分析到行动的脉络
核心问题→假设→数据分析→
洞察→建议→下一步行动

Usage Guidelines

使用指南

When creating storyline:
  • Start with the end in mind (what decision/action needed?)
  • Use MECE principles to organize sections
  • Include quantitative support where possible
  • Make the "so what" clear at each step
When reviewing storyline:
  • Can you understand the full story from titles alone?
  • Is the logical flow clear?
  • Are titles action-oriented (not topics)?
  • Does it lead to clear conclusion/next steps?
  • Are data points specific (not vague)?
构建故事线时：
  • 以终为始（需要达成什么决策/行动？）
  • 运用MECE原则组织内容模块
  • 尽可能加入量化支撑
  • 每一步都明确说明“这意味着什么”
评审故事线时：
  • 仅通过标题能否理解完整故事？
  • 逻辑脉络是否清晰？
  • 标题是否为行动导向（而非主题）？
  • 是否得出清晰的结论/下一步行动？
  • 数据点是否具体（而非模糊）？

Common Mistakes to Avoid

需避免的常见错误

  • Topic titles: "Market Analysis" instead of "Market growing 40% CAGR"
  • Missing the "so what": Data without interpretation
  • Illogical jumps: Skipping steps in reasoning
  • Too granular: 50 slides when 15 would tell the story
  • No ending: Storyline trails off without clear next steps
  • Vague language: "Good performance" instead of "Revenue grew 25%"
  • 主题式标题：用“市场分析”代替“市场年复合增长率达40%”
  • 缺失“关键结论”：只展示数据而不做解读
  • 逻辑跳跃：跳过推理步骤
  • 过于细碎：用50张幻灯片才能讲清的故事，其实15张就足够
  • 无结尾：故事线没有明确的下一步行动就草草结束
  • 模糊表述：用“表现良好”代替“收入增长25%”

Tips for Effective Storylines

打造高效故事线的技巧

Start with structure
  • Outline major sections first
  • Fill in detailed slides within each section
  • Typical deck: 15-25 slides for exec presentation
Consider executive summary upfront
  • Optional first slide summarizing key message
  • Useful for: Problem statement, recommendation, expected impact
  • Allows execs to get punchline immediately
  • Rest of deck provides supporting detail
Use parallel structure
  • Keep similar sections in similar format
  • Makes story easier to follow
  • Example: If slide 5 is "Factor 1: $XXM impact", slide 6 should be "Factor 2: $XXM impact"
Include signposts
  • Use section breaks or agenda slides
  • Help audience know where they are in story
  • Example: "Three drivers of the problem" followed by three slides
Build to the punchline
  • Lead audience through your thinking
  • Don't jump to recommendations without proof
  • But don't bury the lede - executive summary upfront often works
Iterate
  • First draft won't be perfect
  • Review logical flow
  • Get feedback before building full slides
  • Much easier to reorganize storyline than finished slides
从结构入手
  • 先勾勒主要模块
  • 在每个模块内填充详细幻灯片
  • 高管演示文稿通常为15-25张幻灯片
考虑前置执行摘要
  • 可选的第一张幻灯片，总结核心信息
  • 适用于：问题陈述、推荐方案、预期影响
  • 让高管能快速获取核心要点
  • 演示文稿其余部分提供支撑细节
运用平行结构
  • 相似模块采用相似格式
  • 让故事更易理解
  • 示例：如果第5张幻灯片是“因素1：XX百万美元影响”，第6张应为“因素2：XX百万美元影响”
设置导航标识
  • 使用章节分隔或议程幻灯片
  • 帮助受众了解自己在故事中的位置
  • 示例：“问题的三大驱动因素”之后紧跟三张对应幻灯片
逐步引出核心结论
  • 引导受众跟随你的思路
  • 不要在没有证据的情况下直接给出建议
  • 但也不要隐藏核心信息——前置执行摘要通常很有效
反复迭代
  • 第一稿不会完美
  • 评审逻辑脉络
  • 在制作完整幻灯片前获取反馈
  • 调整故事线比修改已完成的幻灯片容易得多