presentation-design

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Presentation Design Diagnostic

演示文稿设计诊断

Purpose

目的

Design and evaluate presentations that communicate effectively. Provides frameworks for planning, visual design, cognitive load management, and evaluation. Applicable to any presentation tool (reveal.js, PowerPoint, Keynote, Google Slides).
设计并评估具备高效沟通能力的演示文稿。提供规划、视觉设计、认知负荷管理和评估的框架。适用于任何演示工具(reveal.js、PowerPoint、Keynote、Google Slides)。

Core Principle

核心原则

Audience-centered design. Every decision should serve audience understanding, not presenter convenience.

以受众为中心的设计。 每一项决策都应服务于受众的理解,而非演示者的便利。

Quick Reference: Common Problems

快速参考:常见问题

ProblemSymptomFix
Wall of TextSlides are paragraphsAssertion-evidence structure
Bullet Point DiseaseLists instead of visualsOne concept + visual evidence
Kitchen SinkEverything includedEssential vs. expandable content
Pretty but EmptyDesign without substanceMessage-first design
Cognitive OverloadToo much per slideOne key concept per slide

问题症状解决方法
文字堆砌幻灯片全是段落采用主张-证据结构
要点列表泛滥用列表而非视觉元素一个概念搭配视觉证据
内容冗余包含所有内容区分核心内容与可扩展内容
华而不实设计缺乏实质内容以信息为核心的设计
认知过载单页幻灯片内容过多每页仅呈现一个核心概念

Phase 1: Audience & Content Planning

第一阶段:受众与内容规划

Key Questions

关键问题

  1. Who specifically is my audience? What's their knowledge level?
  2. What's the ONE main message? What should they remember?
  3. What are 3-5 supporting points? How do they reinforce the message?
  4. What evidence supports each point? Visual, data, examples?
  5. What action should they take? What's the call to action?
  6. What are time constraints? What's essential vs. optional?
  1. 我的受众具体是谁? 他们的知识水平如何?
  2. 核心信息是什么? 他们应该记住什么?
  3. 有3-5个支撑论点是什么? 这些论点如何强化核心信息?
  4. 每个论点有哪些证据支持? 视觉资料、数据还是案例?
  5. 希望他们采取什么行动? 行动号召是什么?
  6. 时间限制是什么? 哪些是核心内容,哪些是可选内容?

Actions

行动项

  • Create audience persona(s)
  • Write one-sentence main message
  • Organize supporting points in logical flow
  • Identify evidence for each point
  • Define essential vs. expandable content
  • Sketch presentation flow

  • 创建受众画像
  • 用一句话概括核心信息
  • 按逻辑顺序组织支撑论点
  • 确定每个论点的支撑证据
  • 区分核心内容与可扩展内容
  • 勾勒演示文稿的流程框架

Phase 2: Visual Strategy

第二阶段:视觉策略

Assertion-Evidence Structure

主张-证据结构

Replace bullet points with:
  • Assertion: Clear, complete sentence stating the point
  • Evidence: Visual that supports the assertion
Instead of:
Key findings:
• Data shows increase
• Users engaged more
• Revenue improved
Use:
"User engagement increased 43% after redesign"
[Graph showing the increase]
用以下内容替代要点列表:
  • 主张: 清晰完整的句子,阐明核心观点
  • 证据: 支持该主张的视觉元素
反面示例:
Key findings:
• Data shows increase
• Users engaged more
• Revenue improved
正确示例:
"User engagement increased 43% after redesign"
[Graph showing the increase]

Visual Principles

视觉设计原则

  • Limited palette: 3-5 colors maximum
  • Typography hierarchy: 2-3 fonts with clear roles
  • Whitespace: Let content breathe
  • Consistency: Same layouts, same treatment
  • Visual progress: Help audience track where they are

  • 有限配色: 最多使用3-5种颜色
  • 字体层级: 使用2-3种字体,明确各自作用
  • 留白: 让内容有呼吸空间
  • 一致性: 统一布局与样式处理
  • 视觉进度: 帮助受众了解当前演示进度

Phase 3: Cognitive Load Management

第三阶段:认知负荷管理

One Concept Per Slide

每页一个核心概念

Each slide should answer: "What's the ONE thing I want them to take from this?"
每张幻灯片都应回答:“我希望他们从这一页获取的唯一信息是什么?”

Progressive Disclosure

渐进式信息披露

Reveal information sequentially instead of all at once:
  1. Show initial state
  2. Add first element with context
  3. Add second element building on first
逐步展示信息,而非一次性全部呈现:
  1. 展示初始状态
  2. 添加第一个元素并说明背景
  3. 添加第二个元素,基于前一个内容展开

Spoken vs. Shown

展示内容与口述内容的区分

Show on SlideSpeak Aloud
Key assertionElaboration
Visual evidenceContext and explanation
Critical dataInterpretation
Next stepWhy it matters
幻灯片展示内容口述内容
核心主张详细阐述
视觉证据背景与解释
关键数据解读分析
下一步行动重要性说明

Code Examples (Technical Talks)

代码示例(技术演讲)

  • Syntax highlighting always
  • Highlight the critical line
  • Build up complex examples
  • Remove boilerplate when possible

  • 始终启用语法高亮
  • 高亮关键代码行
  • 逐步构建复杂示例
  • 尽可能移除冗余代码

Phase 4: Structure Patterns

第四阶段:结构模式

Horizontal vs. Vertical (Multi-Level Navigation)

横向与纵向(多层导航)

Horizontal slides: Main narrative flow Vertical slides: Supporting details (optional deep dives)
Example:
  • Horizontal: "Three Key Factors in Customer Retention"
  • Vertical (under that): Detailed slide for each factor
横向幻灯片: 主要叙事流程 纵向幻灯片: 支撑细节(可选深度内容)
示例:
  • 横向:“客户留存的三个关键因素”
  • 纵向(该幻灯片下):每个因素的详细说明幻灯片

Time Flexibility

时间灵活性

Mark content as:
  • Essential: Must cover in any version
  • Standard: Include with normal time
  • Expandable: Include only with extra time

将内容标记为:
  • 核心内容: 任何版本都必须涵盖
  • 标准内容: 常规时长下需包含
  • 可扩展内容: 仅在有额外时间时添加

Evaluation Framework

评估框架

1. Audience-Centered Design (Rate 1-5)

1. 以受众为中心的设计(评分1-5)

CriterionScoreNotes
Content matches audience knowledge level
Clear value proposition for audience
Adaptable to time constraints
Navigation structure aids understanding
Red Flags:
  • Presenter-focused rather than audience-focused
  • No consideration of audience's existing knowledge
评估标准得分备注
内容匹配受众知识水平
为受众提供清晰的价值主张
可根据时间限制调整
导航结构有助于理解
红色预警:
  • 以演示者为中心而非以受众为中心
  • 未考虑受众的现有知识水平

2. Visual Clarity (Rate 1-5)

2. 视觉清晰度(评分1-5)

CriterionScoreNotes
Assertion-evidence structure used
Visual elements balance text
Visual hierarchy guides attention
Consistent design elements
Thoughtful whitespace
Red Flags:
  • Bullet-point overuse
  • Text-heavy slides
  • Cluttered layouts
评估标准得分备注
采用主张-证据结构
视觉元素与文字平衡
视觉层级引导注意力
设计元素保持一致
合理运用留白
红色预警:
  • 过度使用要点列表
  • 幻灯片文字过多
  • 布局杂乱

3. Cognitive Load (Rate 1-5)

3. 认知负荷(评分1-5)

CriterionScoreNotes
One key concept per slide
Appropriate text density
Judicious animations/transitions
Code properly formatted (if applicable)
Supporting details accessible, not distracting
Red Flags:
  • Multiple complex concepts per slide
  • Excessive text competing with speech
  • Animation overuse
评估标准得分备注
每页一个核心概念
文字密度适中
合理运用动画/转场效果
代码格式规范(如适用)
支撑细节易获取且不分散注意力
红色预警:
  • 单页幻灯片包含多个复杂概念
  • 文字过多与口述内容冲突
  • 过度使用动画

4. Accessibility (Rate 1-5)

4. 可访问性(评分1-5)

CriterionScoreNotes
Works across display sizes
Sufficient color contrast
Inclusive imagery and language
Font sizes appropriate
Red Flags:
  • Poor contrast
  • Too-small fonts
  • Non-inclusive content

评估标准得分备注
适配不同显示尺寸
色彩对比度充足
图像与语言具备包容性
字体大小合适
红色预警:
  • 色彩对比度差
  • 字体过小
  • 内容缺乏包容性

Implementation Checklist

实施检查清单

Structure

结构

  • Main message clear in first 2 minutes
  • Supporting points organized logically
  • Essential vs. expandable content marked
  • Navigation aids understanding
  • 核心信息在开头2分钟内明确传达
  • 支撑论点逻辑清晰
  • 标记核心内容与可扩展内容
  • 导航结构有助于理解

Content

内容

  • Assertion-evidence structure used
  • Visual evidence supports assertions
  • One concept per slide
  • Code examples properly formatted
  • 采用主张-证据结构
  • 视觉证据支撑主张
  • 每页一个核心概念
  • 代码示例格式规范

Visual

视觉设计

  • Consistent color palette
  • Typography hierarchy
  • Sufficient whitespace
  • Elements aligned
  • 配色方案统一
  • 字体层级清晰
  • 留白充足
  • 元素对齐

Accessibility

可访问性

  • Color contrast verified
  • Font sizes appropriate
  • Alternative text for key images

  • 已验证色彩对比度
  • 字体大小合适
  • 关键图像配有替代文本

Improvement Prioritization

改进优先级

After evaluation:
1. Critical Issues (Fix immediately):
  • Blocks audience understanding
  • Accessibility failures
  • Core message unclear
2. Important Enhancements (Second priority):
  • Cognitive load issues
  • Visual consistency problems
  • Structure improvements
3. Nice-to-Have Refinements:
  • Advanced animations
  • Custom styling
  • Polish details

评估完成后:
1. 关键问题(立即修复):
  • 阻碍受众理解
  • 可访问性问题
  • 核心信息模糊
2. 重要优化(第二优先级):
  • 认知负荷问题
  • 视觉一致性问题
  • 结构优化
3. 锦上添花的改进:
  • 高级动画效果
  • 自定义样式
  • 细节打磨

Anti-Patterns

反模式

1. The Data Dump

1. 数据堆砌

Pattern: Every slide full of data, charts, and statistics without interpretation or hierarchy. Why it fails: Audiences can't process raw data in real-time. Without interpretation, they're left doing analysis instead of learning. Most data is forgotten immediately. Fix: One insight per slide with visual evidence supporting the insight. State the conclusion; show the proof. The audience should understand your point before seeing the data.
模式: 每张幻灯片都充满数据、图表和统计信息,缺乏解读与层级划分。 问题所在: 受众无法实时处理原始数据。没有解读的话,他们会忙于分析而非学习。大部分数据会被立即遗忘。 解决方法: 每页呈现一个洞察点,搭配支撑该洞察的视觉证据。先给出结论,再展示证据。受众应在看到数据前理解你的观点。

2. The Script Reader

2. 照本宣科

Pattern: Slides that contain the speaker's full script—bullet points that are really paragraphs. Why it fails: Audiences read faster than speakers talk. They read ahead, then tune out when you say what they already read. The slides become teleprompter, not communication tool. Fix: Slides show what you can't say; you say what you can't show. Visuals, diagrams, and key assertions on screen. Context, explanation, and elaboration spoken.
模式: 幻灯片包含演讲者的完整讲稿——要点列表实际上是段落。 问题所在: 受众阅读速度比演讲者说话快。他们会提前读完内容,然后在你重复他们已读内容时走神。幻灯片变成了提词器,而非沟通工具。 解决方法: 幻灯片展示你无法口述的内容;你口述幻灯片无法展示的内容。屏幕上呈现视觉元素、图表和核心主张,口述背景、解释和详细阐述。

3. The Template Trap

3. 模板陷阱

Pattern: Dropping content into a generic template without considering how the design serves the message. Why it fails: Design should support comprehension, not just look professional. Generic templates create generic communication. One-size-fits-all fits no one well. Fix: Design serves message. Ask: what visual structure helps this specific audience understand this specific content? Start from communication need, not template options.
模式: 将内容直接套入通用模板,不考虑设计如何服务于信息传达。 问题所在: 设计应辅助理解,而非仅仅看起来专业。通用模板会导致千篇一律的沟通效果,一刀切的设计无法满足所有需求。 解决方法: 设计服务于信息传达。思考:什么样的视觉结构能帮助特定受众理解特定内容?从沟通需求出发,而非模板选项。

4. The Animation Circus

4. 动画滥用

Pattern: Transitions, builds, and effects everywhere—flying text, spinning images, fade after fade. Why it fails: Animation is attention. Every effect says "look at this." When everything animates, nothing stands out. Audiences become overwhelmed or numbed. Fix: Animation only for progressive disclosure (building complex ideas step by step) or emphasis (highlighting the key point). Default to no animation; add only with purpose.
模式: 到处使用转场、构建动画和特效——飞动的文字、旋转的图像、不断的淡入淡出。 问题所在: 动画是为了吸引注意力。每个特效都在说“看这里”。当所有内容都有动画时,没有内容会脱颖而出。受众会感到不知所措或麻木。 解决方法: 仅在渐进式信息披露(逐步构建复杂观点)或强调(突出核心内容)时使用动画。默认不使用动画;仅在有明确目的时添加。

5. The Bullet Point Disease

5. 要点列表泛滥

Pattern: Slide after slide of bullet point lists—the default structure for everything. Why it fails: Bullet points are for documents, not presentations. They encourage equal weight for unequal ideas, text-heavy slides, and passive reading instead of active viewing. Fix: Use assertion-evidence structure. Replace bullet lists with clear assertions supported by visual evidence. If you need a list, question whether it needs to be a slide.
模式: 一页接一页的要点列表——适用于所有内容的默认结构。 问题所在: 要点列表适用于文档,而非演示文稿。它们会让不同重要性的观点显得同等重要,导致幻灯片文字过多,受众被动阅读而非主动观看。 解决方法: 采用主张-证据结构。用清晰的主张搭配视觉证据替代要点列表。如果确实需要列表,先考虑是否需要做成幻灯片。

Integration

集成

Inbound (feeds into this skill)

输入(为该技能提供支持)

SkillWhat it provides
speech-adaptationSpoken content structure to coordinate with visuals
story-senseNarrative structure for presentation flow
(content expertise)Subject matter to communicate
技能提供内容
speech-adaptation与视觉元素协调的口述内容结构
story-sense演示流程的叙事结构
(content expertise)需传达的主题内容

Outbound (this skill enables)

输出(该技能赋能的内容)

SkillWhat this provides
(implementation)Design principles for any presentation tool
(delivery)Slides designed to support effective speaking
技能提供内容
(implementation)适用于任何演示工具的设计原则
(delivery)支持高效演讲的幻灯片设计

Complementary

互补技能

SkillRelationship
speech-adaptationPresentation-design handles visuals; speech-adaptation handles spoken content. Design together for coordination
voice-analysisUnderstanding the presenter's voice helps design slides that match their natural delivery style
技能关系
speech-adaptation演示文稿设计负责视觉元素;speech-adaptation负责口述内容。需协同设计以实现协调统一
voice-analysis了解演讲者的语音特点,有助于设计匹配其自然演讲风格的幻灯片