storytelling

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Storytelling

叙事技巧

When to Use

适用场景

Shape a story spine (setup → tension → resolution) for a decision, launch, or change
Tailor the same facts into executive, board, customer, or team narratives
Build a data story with honest framing, context, and uncertainty
Draft product or strategy narratives that connect problem, choice, and proof
Turn incidents or postmortems into blameless, actionable stories
Explain actuarial or insurance risk to non-technical stakeholders without diluting rigor
Outline slide or visual narrative flow (section purpose, not final design)
Distill key messages (3–5 MECE bullets) aligned to one audience and one ask

为决策、产品发布或变革构建story spine（setup → tension → resolution）
将相同事实调整为适合高管、董事会、客户或团队的叙事版本
构建包含真实呈现、背景信息及不确定性说明的data story
撰写连接问题、选择与实证的产品或战略叙事
将事故或复盘内容转化为无责、可落地的叙事
在不降低严谨性的前提下，向非技术利益相关方解释精算或保险风险
梳理幻灯片或可视化叙事的流程（仅需说明章节目的，无需最终设计）
提炼与单一受众及单一诉求匹配的核心信息（3–5个相互独立、完全穷尽的要点）

When NOT to Use

不适用场景

Reframe jargon or produce dual-audience briefs without building narrative arc →
```
cross-department-translation
```
Org-wide messaging hierarchy, launch/crisis wording packs, or comms cadence →
```
communication-lead
```
Issue trees, business cases, or steerCo analysis as the primary deliverable →
```
business-consultant
```
API docs, runbooks, tutorials, or information architecture →
```
tech-writer-researcher
```
Long-form creative fiction, screenplays, or character-driven prose
Brand voice, campaign creative, or marketing copy without strategic narrative framing → route to marketing or brand skills if present; pair with
```
communication-lead
```
for approved external lines
Legal contract language, regulatory filings, or compliance attestation narratives →
```
commercial-counsel
```
,
```
compliance-engineer
```
,
```
actuarial-consulting
```
as appropriate

仅重构术语或制作双受众简报但未构建叙事弧 → 转用
```
cross-department-translation
```
全公司消息层级、发布/危机话术包或沟通节奏 → 转用
```
communication-lead
```
以问题树、商业案例或指导委员会分析为主要交付物 → 转用
```
business-consultant
```
API文档、运行手册、教程或信息架构 → 转用
```
tech-writer-researcher
```
长篇创意小说、剧本或角色驱动的散文
无战略叙事框架的品牌调性、营销活动创意或营销文案 → 若有相关营销或品牌技能则转至对应技能；如需获批的对外话术，可搭配
```
communication-lead
```
使用
法律合同语言、监管申报或合规认证叙事 → 根据情况转用
```
commercial-counsel
```
、
```
compliance-engineer
```
、
```
actuarial-consulting
```

Related skills

Need	Skill
Cross-functional reframing and dual-audience briefs	`cross-department-translation`
Company narrative consistency across stakeholders	`communication-lead`
Strategy options, business case, steerCo analysis	`business-consultant`
Long-form research synthesis and technical docs	`tech-writer-researcher`
Actuarial methods, reserves, regulatory deliverables	`actuary` , `actuarial-consulting`
Incident program, severity, paging, postmortem process	`incident-management-engineer`
Product positioning and UX copy	`product-designer`

需求	技能
跨职能重构与双受众简报	`cross-department-translation`
跨利益相关方的公司叙事一致性	`communication-lead`
战略选项、商业案例、指导委员会分析	`business-consultant`
长篇研究整合与技术文档	`tech-writer-researcher`
精算方法、准备金、监管交付物	`actuary` , `actuarial-consulting`
事故管理流程、严重等级、告警、复盘流程	`incident-management-engineer`
产品定位与UX文案	`product-designer`

Core Workflows

核心工作流程

1. Clarify audience, ask, and proof

1. 明确受众、诉求与实证

Before drafting, lock:

Field	Question
Audience	Who must understand, believe, or act?
Ask	One decision or behavior change
Stakes	What happens if they misunderstand?
Proof	Metrics, examples, quotes (verified only)
Constraints	Legal, competitive, or timing guardrails

If the task is only vocabulary translation, route to

cross-department-translation

See
references/storytelling_scope_and_principles.md
.

撰写前需确定以下内容：

字段	问题
受众	谁需要理解、信服或采取行动？
诉求	单一决策或行为改变目标
风险	若受众误解会产生什么后果？
实证	经核实的指标、案例、引用内容
约束条件	法律、竞争或时间限制

若任务仅为词汇翻译，转用

cross-department-translation

。

参考文档：
references/storytelling_scope_and_principles.md

2. Build the story spine

2. 构建故事主线

Use a single through-line:

Setup — context the audience already accepts
Tension — gap, risk, or opportunity (named clearly)
Turn — insight, decision, or intervention
Resolution — outcome, next step, or open question (honest)

Derive 3–5 key messages from the spine; each message needs one proof point.

See
references/narrative_structure_and_arcs.md
.

采用单一贯穿线：

Setup — 受众已认可的背景信息
Tension — 明确指出的差距、风险或机遇
Turn — 洞察、决策或干预措施
Resolution — 结果、下一步行动或坦诚提出的开放性问题

从主线中提炼3–5个核心信息；每个信息需搭配一个实证点。

参考文档：
references/narrative_structure_and_arcs.md

3. Tune register and channel

3. 调整风格与渠道

Match depth, jargon, and tone to audience and medium (live talk, memo, deck, status page).

See
references/audience_and_register.md
.

根据受众与媒介（现场演讲、备忘录、演示文稿、状态页面）匹配内容深度、术语使用及语气。

参考文档：
references/audience_and_register.md

4. Tell the data story

4. 讲述数据故事

Lead with the so what; show trend and comparison; state uncertainty; avoid chartjunk narratives.

See
references/data_and_metrics_storytelling.md
.

以“核心价值”开篇；展示趋势与对比；说明不确定性；避免冗余的图表叙事。

参考文档：
references/data_and_metrics_storytelling.md

5. Executive, board, and strategy stories

5. 高管、董事会与战略叙事

Pyramid the recommendation; separate decision from appendix; pre-empt predictable objections.

See
references/executive_board_and_strategy_stories.md
.

采用金字塔结构呈现建议；将决策内容与附录分离；提前预判可能的反对意见。

参考文档：
references/executive_board_and_strategy_stories.md

6. Incident, change, and actuarial narratives

6. 事故、变革与精算叙事

Blameless incident arcs; change stories with empathy and timeline; risk stories with ranges and drivers—not false precision.

See
references/incident_change_and_actuarial_narratives.md
.

采用无责事故叙事弧；包含同理心与时间线的变革故事；呈现风险范围与驱动因素而非虚假精确值的风险故事。

参考文档：
references/incident_change_and_actuarial_narratives.md

Output standards

输出标准

One primary ask per story; secondary asks subordinate
Plain language; define acronyms once per artifact
No fabricated quotes, metrics, or causation
Label estimates, scenarios, and confidence explicitly
For slides: section intent + headline + 1–2 supporting bullets (not full visual design)
Version and timestamp incident or crisis story drafts

每个故事仅包含一个核心诉求；次要诉求需服从核心诉求
使用平实语言；每个文档中首字母缩写仅需定义一次
不得编造引用内容、指标或因果关系
明确标注估算值、场景及置信度
对于幻灯片：需包含章节意图+标题+1-2个支撑要点（无需完整视觉设计）
为事故或危机叙事草稿添加版本号及时间戳

When to load references

何时调用参考文档

Scope, ethics, boundaries →

references/storytelling_scope_and_principles.md

Arcs, spine, key messages →

references/narrative_structure_and_arcs.md

Audience and register →
```
references/audience_and_register.md
```

Metrics and charts as narrative →

references/data_and_metrics_storytelling.md

Exec, board, strategy, pitch →

references/executive_board_and_strategy_stories.md

Incident, change, actuarial risk →

references/incident_change_and_actuarial_narratives.md

范围、伦理、边界 →

references/storytelling_scope_and_principles.md

叙事弧、主线、核心信息 →

references/narrative_structure_and_arcs.md

受众与风格 →
```
references/audience_and_register.md
```

指标与图表叙事 →

references/data_and_metrics_storytelling.md

高管、董事会、战略、推介 →

references/executive_board_and_strategy_stories.md

事故、变革、精算风险 →

references/incident_change_and_actuarial_narratives.md