visual-thinking

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Visual Analogy Creation: Cognitive Protocol

视觉类比创建：认知协议

Visual analogies succeed when they map relational structure from a familiar domain onto an unfamiliar domain, using spatial relationships to make abstract patterns concrete.

视觉类比的成功之处在于，它将熟悉领域的关系结构映射到陌生领域，并利用空间关系将抽象模式具象化。

Core Principle

核心原则

Add elements when they reveal structure; remove them when they obscure it. The question is: "Does this complexity serve understanding?"

当元素能够揭示结构时添加；当元素会模糊结构时移除。关键问题是：“这种复杂性是否有助于理解？”

Part 1: The Diagnostic Phase

第一部分：诊断阶段

Step 1.1: Extract the Core Relational Structure

步骤1.1：提取核心关系结构

Identify the pattern of relationships, not the surface features.

Procedure:

Write down the concept/system you need to visualize
Ask: "What relates to what here?" List all relationships
Ask: "What affects what?" List all causal chains
Ask: "What changes together?" List all correlations
Identify the single most important relationship - this is your core structure

Example - "Customer loyalty programs":

Relationships: Customer ↔ Company, Purchase ↔ Points, Points ↔ Rewards
Causal chains: Purchase → Points accumulate → Rewards unlock → More purchases
Changes together: Time invested ↔ Switching cost increases
Core structure: Incremental investment creates increasing exit barriers

Why this works (Gentner's Structure-Mapping Theory): Analogies succeed by aligning systems of relations, not by matching surface attributes.

识别关系模式，而非表面特征。

操作流程：

写下需要可视化的概念/系统
提问：“这里的各个元素之间存在怎样的关联？”列出所有关系
提问：“哪些元素会影响其他元素？”列出所有因果链
提问：“哪些元素会同步变化？”列出所有相关性
找出最重要的单一关系——这就是你的核心结构

示例 - “客户忠诚度计划”：

关系：客户 ↔ 企业，消费 ↔ 积分，积分 ↔ 奖励
因果链：消费 → 积分累积 → 奖励解锁 → 更多消费
同步变化：投入时间 ↔ 转换成本增加
核心结构：渐进式投入会形成不断提高的退出壁垒

理论依据（Gentner的结构映射理论）：类比的成功源于关系系统的对齐，而非表面属性的匹配。

Step 1.2: Classify the Question Type (6W Framework)

步骤1.2：分类问题类型（6W框架）

Determine what KIND of understanding you're creating, which constrains the visual form.

Decision tree:

IF asking "what kind of thing is this?" or "how do these categories relate?"
  → WHO/WHAT (Qualitative/Portrait)
  → Use: Venn diagrams, attribute lists, categorical groupings

ELSE IF asking "how much/many?" or "compare quantities"
  → HOW MUCH (Quantitative/Charts)
  → Use: Bar charts, line graphs, proportional areas

ELSE IF asking "where is this in relation to other things?"
  → WHERE (Positional/Maps)
  → Use: 2x2 matrices, positioning maps, spatial layouts

ELSE IF asking "in what order?" or "when does this happen?"
  → WHEN (Temporal/Timelines)
  → Use: Sequential flows, timelines, stages

ELSE IF asking "how does this work?" or "what's the mechanism?"
  → HOW (Process/Flowcharts)
  → Use: Flow diagrams, cycle diagrams, system maps

ELSE IF asking "why does this happen?" or "what causes what?"
  → WHY (Causation/Multi-variable)
  → Use: Causal diagrams, feedback loops, correlation plots

Why this works (Tversky's Mind in Motion): Different cognitive tasks require different spatial structures.

确定你要达成的理解类型，这会限制视觉形式的选择。

决策树：

IF asking "what kind of thing is this?" or "how do these categories relate?"
  → WHO/WHAT (Qualitative/Portrait)
  → Use: Venn diagrams, attribute lists, categorical groupings

ELSE IF asking "how much/many?" or "compare quantities"
  → HOW MUCH (Quantitative/Charts)
  → Use: Bar charts, line graphs, proportional areas

ELSE IF asking "where is this in relation to other things?"
  → WHERE (Positional/Maps)
  → Use: 2x2 matrices, positioning maps, spatial layouts

ELSE IF asking "in what order?" or "when does this happen?"
  → WHEN (Temporal/Timelines)
  → Use: Sequential flows, timelines, stages

ELSE IF asking "how does this work?" or "what's the mechanism?"
  → HOW (Process/Flowcharts)
  → Use: Flow diagrams, cycle diagrams, system maps

ELSE IF asking "why does this happen?" or "what causes what?"
  → WHY (Causation/Multi-variable)
  → Use: Causal diagrams, feedback loops, correlation plots

理论依据（Tversky的《思维运动》）：不同的认知任务需要不同的空间结构。

Step 1.3: Identify the Image Schema

步骤1.3：识别意象图式

Find the pre-conceptual spatial pattern that matches your relational structure.

Universal image schemas:

CONTAINER - Inclusion/exclusion/boundaries

Geometric: Circles, boxes, nested shapes
Relations: Inside/outside, member/non-member, bounded/unbounded
Example: "Users in our ecosystem" → Nested circles

PATH - Progression/journey/sequence

Geometric: Lines with direction, connected segments
Relations: Start/end, before/after, progress/regress
Example: "Customer journey" → Path with waypoints

FORCE - Causation/influence/pressure

Geometric: Arrows, vectors, pushing/pulling
Relations: Cause/effect, strong/weak, resist/yield
Example: "Market forces" → Opposing arrows

BALANCE - Trade-offs/equilibrium/reciprocity

Geometric: Scales, see-saws, balanced arrangements
Relations: Equal/unequal, stable/unstable, compensate
Example: "Work-life balance" → Scale with weights

LINK - Connection/relationship/dependency

Geometric: Lines connecting nodes
Relations: Connected/disconnected, strong/weak ties, central/peripheral
Example: "Social network" → Graph with nodes and edges

CYCLE - Repetition/feedback/recursion

Geometric: Loops, circles, spirals
Relations: Reinforce/balance, growth/decay, iterate
Example: "Feedback loop" → Circular arrows

SCALE - Magnitude/hierarchy/levels

Geometric: Vertical position, size differences, nested levels
Relations: More/less, superior/subordinate, macro/micro
Example: "Organizational hierarchy" → Pyramid or tree

Why this works (Lakoff & Johnson's Conceptual Metaphor Theory): Abstract reasoning is grounded in bodily experience of space.

找到与你的关系结构匹配的前置概念空间模式。

通用意象图式：

容器 - 包含/排除/边界

几何形式：圆形、方框、嵌套形状
关系：内部/外部、成员/非成员、有界/无界
示例：“我们生态系统中的用户” → 嵌套圆形

路径 - 进展/旅程/序列

几何形式：带方向的线条、连接的线段
关系：起点/终点、之前/之后、前进/后退
示例：“客户旅程” → 带途经点的路径

力 - 因果/影响/压力

几何形式：箭头、向量、推/拉图形
关系：因/果、强/弱、抵抗/屈服
示例：“市场力量” → 相对的箭头

平衡 - 权衡/均衡/互惠

几何形式：天平、跷跷板、平衡布局
关系：相等/不等、稳定/不稳定、补偿
示例：“工作与生活的平衡” → 带砝码的天平

链接 - 连接/关系/依赖

几何形式：连接节点的线条
关系：连接/断开、强/弱关系、中心/边缘
示例：“社交网络” → 带节点和边的图

循环 - 重复/反馈/递归

几何形式：循环、圆形、螺旋
关系：强化/平衡、增长/衰减、迭代
示例：“反馈循环” → 环形箭头

尺度 - 量级/层级/级别

几何形式：垂直位置、大小差异、嵌套层级
关系：多/少、上级/下级、宏观/微观
示例：“组织层级” → 金字塔或树状结构

理论依据（Lakoff & Johnson的概念隐喻理论）：抽象推理基于人类对空间的身体体验。

Part 2: The Generation Phase

第二部分：生成阶段

Step 2.1: Source Domain Selection via Structural Matching

步骤2.1：通过结构匹配选择源领域

Find a familiar domain that has the SAME relational structure, even if surface features differ completely.

Procedure:

List your target domain's relational properties:
- From Step 1.1: "X relates to Y by [relationship type]"
- From Step 1.3: "The geometric essence is [image schema]"
Generate source domain candidates:
- Query: "What familiar things have this same pattern of relationships?"
- Consider: Physical objects, natural phenomena, games, human relationships, machines, economics, biology
- List 5-10 candidates

Test structural alignment: Create explicit mapping table:

Target Element → Source Element
Relation 1     → Equivalent Relation
Relation 2     → Equivalent Relation

Evaluate mapping quality:
- ✓ Do ALL key relations have equivalents?
- ✓ Are the relations the SAME TYPE (causal→causal, hierarchical→hierarchical)?
- ✓ Does the source domain add insight, not just restate?
- ✓ Is the source domain more familiar than the target?

Why this works (Hofstadter & Sander's Analogy Theory): Analogy is about finding abstract sameness beneath surface differences. Quality depends on structural isomorphism.

找到具有相同关系结构的熟悉领域，即使表面特征完全不同。

操作流程：

列出目标领域的关系属性：
- 来自步骤1.1：“X与Y的关系是[关系类型]”
- 来自步骤1.3：“几何本质是[意象图式]”
生成源领域候选：
- 提问：“哪些熟悉的事物具有这种相同的关系模式？”
- 考虑：物理对象、自然现象、游戏、人际关系、机器、经济学、生物学
- 列出5-10个候选

测试结构对齐：创建明确的映射表：

Target Element → Source Element
Relation 1     → Equivalent Relation
Relation 2     → Equivalent Relation

评估映射质量：
- ✓ 所有关键关系都有对应项吗？
- ✓ 关系类型是否一致（因果→因果、层级→层级）？
- ✓ 源领域是否能带来新见解，而非仅仅重复？
- ✓ 源领域是否比目标领域更熟悉？

理论依据（Hofstadter & Sander的类比理论）：类比是在表面差异之下寻找抽象的共性。质量取决于结构同构性。

Step 2.2: Refine Through Conceptual Blending

步骤2.2：通过概念整合进行优化

Create emergent meaning by selectively combining elements from source and target.

Procedure:

Create the mapping table:

Target Domain | Source Domain | Blended Concept | Emergent Insight

Identify emergent structure:
- What does the blend reveal that neither domain alone shows?
- What new inferences does the mapping enable?
Test inferential productivity:
- Can you make predictions in the target domain using source domain logic?
- Do these predictions reveal non-obvious insights?

Why this works (Fauconnier & Turner's Conceptual Blending): Meaning emerges from the blend. Good analogies create insights that exist in neither source nor target alone.

通过选择性结合源领域和目标领域的元素，创造新的含义。

操作流程：

创建映射表：

Target Domain | Source Domain | Blended Concept | Emergent Insight

识别涌现结构：
- 整合后的概念揭示了哪些单独领域无法体现的内容？
- 这种映射能带来哪些新的推论？
测试推论有效性：
- 能否利用源领域的逻辑对目标领域做出预测？
- 这些预测是否揭示了非显而易见的见解？

理论依据（Fauconnier & Turner的概念整合理论）：含义源于整合过程。优秀的类比能创造出源领域和目标领域单独都不存在的见解。

Step 2.3: Determine SQVID Settings

步骤2.3：设置SQVID参数

Configure the visual style to match audience and purpose.

S - STRUCTURAL DETAIL LEVEL

What this controls: How much internal structure to reveal

IF concept's insight requires seeing internal mechanisms/interactions
  → ELABORATE (show subsystems, intermediate steps, feedback loops)
ELSE IF concept's insight is in overall pattern/relationship
  → SIMPLE (show high-level structure only)

Test: Does showing internal detail change the conclusion?
  YES → Elaborate reveals necessary structure
  NO → Simple reveals essential pattern

Q - QUALITY vs. QUANTITY

What this controls: Categorical or numerical information

IF insight is about characteristics/attributes/types/categories
  → QUALITY (labels, distinctions, feature descriptions)
ELSE IF insight is about amounts/measurements/comparisons/magnitudes
  → QUANTITY (numbers, scales, proportions, data encodings)

V - VISION vs. EXECUTION

What this controls: Temporal reference frame

IF showing ideal state OR future goal OR possibility space OR aspirational
  → VISION (how it should/could be, potential)
ELSE IF showing current state OR actual data OR constraints OR reality
  → EXECUTION (how it is, actuality)

I - INDIVIDUAL vs. COMPARISON

What this controls: Number of entities and focus

IF showing one entity's internal structure/behavior/properties
  → INDIVIDUAL (deep dive into single case)
ELSE IF showing relationships between entities OR contrasting alternatives
  → COMPARISON (multiple entities, relative positioning)

D - DELTA vs. STATUS QUO

What this controls: Temporal dynamics

IF emphasizing change/transformation/trend/evolution
  → DELTA (before/after, trajectories, rates of change)
ELSE IF emphasizing current configuration/snapshot/state
  → STATUS QUO (present moment, what exists now)

Why this works (Tufte's Visual Display Principles): Every visual encoding choice should match the type of information being conveyed.

根据受众和目的配置视觉风格。

S - 结构细节层级

控制内容：揭示多少内部结构

IF concept's insight requires seeing internal mechanisms/interactions
  → ELABORATE (show subsystems, intermediate steps, feedback loops)
ELSE IF concept's insight is in overall pattern/relationship
  → SIMPLE (show high-level structure only)

Test: Does showing internal detail change the conclusion?
  YES → Elaborate reveals necessary structure
  NO → Simple reveals essential pattern

Q - 定性 vs 定量

控制内容：分类或数值信息

IF insight is about characteristics/attributes/types/categories
  → QUALITY (labels, distinctions, feature descriptions)
ELSE IF insight is about amounts/measurements/comparisons/magnitudes
  → QUANTITY (numbers, scales, proportions, data encodings)

V - 愿景 vs 执行

控制内容：时间参考框架

IF showing ideal state OR future goal OR possibility space OR aspirational
  → VISION (how it should/could be, potential)
ELSE IF showing current state OR actual data OR constraints OR reality
  → EXECUTION (how it is, actuality)

I - 个体 vs 对比

控制内容：实体数量和焦点

IF showing one entity's internal structure/behavior/properties
  → INDIVIDUAL (deep dive into single case)
ELSE IF showing relationships between entities OR contrasting alternatives
  → COMPARISON (multiple entities, relative positioning)

D - 变化 vs 现状

控制内容：时间动态

IF emphasizing change/transformation/trend/evolution
  → DELTA (before/after, trajectories, rates of change)
ELSE IF emphasizing current configuration/snapshot/state
  → STATUS QUO (present moment, what exists now)

理论依据（Tufte的视觉展示原则）：每一个视觉编码选择都应与所传达的信息类型匹配。

Part 3: The Construction Phase

第三部分：构建阶段

Step 3.1: Translate Relational Structure to Spatial Structure

步骤3.1：将关系结构转换为空间结构

Convert abstract relationships into concrete spatial relationships.

Spatial encoding rules:

Causation → Arrows
- A causes B: Arrow from A to B
- Mutual causation: Arrows both directions (cycle)
- Strong/weak: Thick/thin arrows
Magnitude → Size or Position
- More/greater: Larger size OR higher vertical position
- Less/smaller: Smaller size OR lower vertical position
Time → Horizontal or Vertical Progression
- Earlier → Left OR bottom
- Later → Right OR top
Similarity → Proximity
- Related concepts: Close together
- Different concepts: Far apart
Hierarchy → Vertical Position or Nesting
- Superordinate: Above OR containing
- Subordinate: Below OR contained
Process Flow → Connected Path
- Sequential: Linked chain
- Parallel: Side-by-side paths
- Branching: Path splits
Intensity/Degree → Visual Variable
- More intense: Darker, thicker, larger
- Less intense: Lighter, thinner, smaller

Why this works (Tversky's Cognitive Design Principles): When spatial structure matches conceptual structure, comprehension is immediate.

将抽象关系转化为具体的空间关系。

空间编码规则：

因果关系 → 箭头
- A导致B：从A指向B的箭头
- 相互因果：双向箭头（循环）
- 强/弱关系：粗/细箭头
量级 → 大小或位置
- 更多/更大：更大尺寸或更高垂直位置
- 更少/更小：更小尺寸或更低垂直位置
时间 → 水平或垂直进展
- 更早 → 左侧或底部
- 更晚 → 右侧或顶部
相似性 → proximity（邻近度）
- 相关概念：靠近彼此
- 不同概念：远离彼此
层级 → 垂直位置或嵌套
- 上级：上方或包含其他元素
- 下级：下方或被包含
流程 → 连接路径
- 顺序：链接的链条
- 并行：并排路径
- 分支：路径分叉
强度/程度 → 视觉变量
- 更强：颜色更深、线条更粗、尺寸更大
- 更弱：颜色更浅、线条更细、尺寸更小

理论依据（Tversky的认知设计原则）：当空间结构与概念结构匹配时，理解会瞬间发生。

Step 3.2: Apply Progressive Structure Revelation

步骤3.2：应用渐进式结构揭示

Build from core structure outward, testing at each layer whether additional structure adds insight.

Construction procedure:

Layer 0 - Core Relationship Hypothesis State in one sentence what relationship/pattern/mechanism you're revealing. This is your north star.

Layer 1 - Essential Structure

Identify minimum elements needed to show the relationship
Draw the relationship using appropriate spatial encoding
STOP. Test: Does this make the stated relationship visible?
- If YES → Proceed to Layer 2
- If NO → Revise core relationship or element selection

Layer 2 - Structural Context

Identify what modulates/constrains/amplifies the core relationship
Add these elements and their relationships
STOP. Test: Does this reveal how the system behaves under different conditions?
- If YES → Context adds genuine insight
- If NO → Remove context, it's not structural

Layer 3 - Structural Detail

Identify whether understanding requires seeing HOW the relationships work internally
Add mechanism details ONLY if they change conclusions
STOP. Test: Does this detail reveal non-obvious behavior?
- If YES → Keep, you're showing necessary complexity
- If NO → Remove, it's decorative

Layer 4 - Exceptional Structure

Add ONLY if interesting behavior happens at extremes or boundaries
Show what breaks, saturates, or reverses
Test: Does this explain real-world observations that normal case doesn't?

Decision rule: Include layers 0-1 always. Include 2 if behavior is context-dependent. Include 3-4 only if explaining observed phenomena requires them.

Key insight: Each layer should add genuine structural insight, not decorative detail.

Why this works (Tufte's Data-Ink Ratio): Maximize the proportion of ink devoted to data.

从核心结构向外构建，在每一层测试新增结构是否能带来见解。

构建流程：

第0层 - 核心关系假设 用一句话陈述你要揭示的关系/模式/机制。这是你的指导方针。

第1层 - 基础结构

识别展示关系所需的最少元素
使用合适的空间编码绘制关系
停止测试：这是否能让陈述的关系清晰可见？
- 如果是 → 进入第2层
- 如果否 → 修改核心关系或元素选择

第2层 - 结构背景

识别调节/约束/强化核心关系的因素
添加这些元素及其关系
停止测试：这是否揭示了系统在不同条件下的行为？
- 如果是 → 背景带来了真正的见解
- 如果否 → 删除背景，它不属于结构范畴

第3层 - 结构细节

判断理解是否需要了解关系的内部运作方式
仅在细节会改变结论时添加机制细节
停止测试：这些细节是否揭示了非显而易见的行为？
- 如果是 → 保留，你展示的是必要的复杂性
- 如果否 → 删除，这只是装饰性内容

第4层 - 特殊结构

仅在极端或边界条件下出现有趣行为时添加
展示哪些情况会中断、饱和或逆转
测试：这是否解释了常规情况无法说明的真实世界现象？

决策规则：始终包含第0-1层。如果行为依赖于背景，则包含第2层。仅在解释观察到的现象需要时，才包含第3-4层。

关键见解：每一层都应带来真正的结构见解，而非装饰性细节。

理论依据（Tufte的数据墨水比原则）：最大化用于数据的墨水比例。

Step 3.3: Validate Through Mental Simulation

步骤3.3：通过心理模拟验证

Test if someone can "run" your visual like a simulation in their mind.

Validation procedure:

Trace test: Can you follow a path through the visual?
- Start at beginning, follow connections, reach conclusion or cycle
Prediction test: Can you predict what happens next?
- Given initial state, following the relationships, infer next state
Manipulation test: Can you mentally change one variable and see effects?
- If X increases, what happens to Y?
Explanation test: Can someone unfamiliar explain it back?
- If explanation ≠ intended insight, visual fails

Why this works (Hegarty's Mental Animation Theory): Effective diagrams support mental simulation.

测试他人是否能在脑海中像运行模拟一样理解你的视觉内容。

验证流程：

追踪测试：能否沿着视觉内容中的路径追踪？
- 从起点开始，跟随连接，到达结论或循环
预测测试：能否预测接下来会发生什么？
- 给定初始状态，遵循关系，推断下一个状态
操作测试：能否在脑海中改变一个变量并查看影响？
- 如果X增加，Y会发生什么？
解释测试：不熟悉内容的人能否反向解释它？
- 如果解释与预期见解不符，视觉内容失败

理论依据（Hegarty的心理动画理论）：有效的图表支持心理模拟。

Part 4: Refinement Protocols

第四部分：优化协议

Anti-Pattern Detection

反模式检测

Run this checklist on every visual analogy:

□ DECORATION TRAP For each visual element: "Does this encode information about relationships?"

If NO → REMOVE IT
Note: Styling that encodes information (color for category, depth for hierarchy) is NOT decoration

□ STRUCTURAL MISMATCH Does the analogy break down at boundaries or in important cases?

Test: Push to extremes. Does it still work?
Test: Apply to relevant edge cases. Does it break?

□ SURFACE SIMILARITY TRAP Are you matching on appearance rather than relationships?

Create explicit mapping table from Step 2.1
Verify RELATIONSHIP TYPE matches (causal→causal, part-whole→part-whole)

□ MULTIPLE INSIGHTS Can you state the insight in one sentence?

If NO → Create multiple visuals, each with single clear insight
Note: Complex visuals showing ONE multilayered structure are acceptable

□ PRECISION THEATER Are you showing false precision?

Test: Is the data/relationship actually that precise?
If NO → Use approximation that honestly reflects uncertainty

□ COGNITIVE LOAD Does the visual require excessive working memory?

Test: How many distinct relationships must be held simultaneously?
If >7 → Consider breaking into multiple linked visuals or hierarchical organization

对每个视觉类比运行以下检查清单：

□ 装饰陷阱 对于每个视觉元素：“它是否编码了关于关系的信息？”

如果否 → 删除它
注意：用于编码信息的样式（如类别用颜色、层级用深度）不属于装饰

□ 结构不匹配 类比在边界或重要场景下是否失效？

测试：推向极端情况，它是否仍然有效？
测试：应用于相关边缘案例，它是否会失效？

□ 表面相似性陷阱 你是否在匹配外观而非关系？

创建步骤2.1中的明确映射表
验证关系类型是否匹配（因果→因果、整体-部分→整体-部分）

□ 多见解混淆 你能否用一句话陈述见解？

如果否 → 创建多个视觉内容，每个内容仅包含一个清晰的见解
注意：展示单一多层结构的复杂视觉内容是可接受的

□ 虚假精准陷阱 你是否展示了虚假的精准性？

测试：数据/关系是否真的如此精准？
如果否 → 使用能真实反映不确定性的近似表达

□ 认知过载 视觉内容是否需要过多的工作记忆？

测试：必须同时记住多少种不同的关系？
如果超过7种 → 考虑拆分为多个关联的视觉内容或采用层级组织

Structural Validity Test

结构有效性测试

TEST 1: Structural Completeness Does the visual show all relationships necessary for the insight?

TEST 2: Mapping Fidelity For analogies: Does every mapped relationship preserve its type?

TEST 3: Cognitive Simulation Can someone mentally "run" the system using your visual?

TEST 4: Insight Necessity Does the visual reveal something non-obvious?

TEST 5: Boundary Testing Does the analogy break at extremes you care about?

TEST 6: Emergent Insight Check Does the mapping reveal implications you didn't initially consider?

TEST 7: Clarity Under Modification If you change one element, do the consequences propagate correctly?

测试1：结构完整性 视觉内容是否展示了见解所需的所有关系？

测试2：映射保真度 对于类比：每个映射的关系是否保留了其类型？

测试3：认知模拟 能否利用你的视觉内容在脑海中“运行”系统？

测试4：见解必要性 视觉内容是否揭示了非显而易见的内容？

测试5：边界测试 类比在你关注的极端情况下是否会失效？

测试6：涌现见解检查 映射是否揭示了你最初未考虑到的含义？

测试7：修改清晰度 如果你更改一个元素，后果是否能正确传递？

Quick Reference

快速参考

Image Schema Quick Match

意象图式快速匹配

YOUR CONCEPT INVOLVES...     → USE THIS SCHEMA → VISUAL FORM

Categories/membership        → CONTAINER       → Circles, Venn diagrams
Sequence/journey             → PATH            → Linear flow, timeline
Influence/causation          → FORCE           → Arrows, vectors
Trade-offs/reciprocity       → BALANCE         → Scales, see-saw
Relationships/links          → LINK            → Network graph
Repetition/feedback          → CYCLE           → Loops, circular arrows
Magnitude/hierarchy          → SCALE           → Vertical position, size

YOUR CONCEPT INVOLVES...     → USE THIS SCHEMA → VISUAL FORM

Categories/membership        → CONTAINER       → Circles, Venn diagrams
Sequence/journey             → PATH            → Linear flow, timeline
Influence/causation          → FORCE           → Arrows, vectors
Trade-offs/reciprocity       → BALANCE         → Scales, see-saw
Relationships/links          → LINK            → Network graph
Repetition/feedback          → CYCLE           → Loops, circular arrows
Magnitude/hierarchy          → SCALE           → Vertical position, size

6W Quick Decision

6W快速决策

QUESTION TYPE → VISUAL FORM     → SHOWS

Who/What?     → Portrait        → Categories, attributes
How much?     → Chart           → Quantities, comparisons
Where?        → Map             → Position, relationships
When?         → Timeline        → Sequence, duration
How?          → Flowchart       → Process, mechanism
Why?          → Causal diagram  → Causation, correlation

QUESTION TYPE → VISUAL FORM     → SHOWS

Who/What?     → Portrait        → Categories, attributes
How much?     → Chart           → Quantities, comparisons
Where?        → Map             → Position, relationships
When?         → Timeline        → Sequence, duration
How?          → Flowchart       → Process, mechanism
Why?          → Causal diagram  → Causation, correlation

Spatial Encoding Rules

RELATIONSHIP → ENCODE AS

Causation    → Arrow
Magnitude    → Size or vertical position
Time         → Horizontal axis or sequence
Similarity   → Proximity
Hierarchy    → Nesting or vertical stack
Flow         → Connected path
Intensity    → Darkness, thickness, size

RELATIONSHIP → ENCODE AS

Causation    → Arrow
Magnitude    → Size or vertical position
Time         → Horizontal axis or sequence
Similarity   → Proximity
Hierarchy    → Nesting or vertical stack
Flow         → Connected path
Intensity    → Darkness, thickness, size

Summary: The Complete Protocol

总结：完整协议

Phase 1: Diagnose (What am I showing?)

Extract core relational structure
Classify question type (6W)
Identify image schema

Phase 2: Generate (What's it like?) 4. Find source domain with structural match 5. Create explicit mapping table 6. Test for emergent insights (blending) 7. Set SQVID parameters

Phase 3: Construct (How do I show it?) 8. Translate relations to spatial structure 9. Build progressive layers (0-4) 10. Validate through mental simulation

Phase 4: Refine (What can I remove?) 11. Run anti-pattern checks 12. Apply Structural Validity Tests 13. Iterate until structural clarity achieved

Throughout: Remember the Why

Gentner: Match relational structure, not surface features
Lakoff & Johnson: Ground abstract concepts in spatial experience
Tversky: Spatial relationships carry conceptual relationships
Tufte: Maximize information, minimize ink
Hofstadter: Analogy creates insight through novel mapping

The Meta-Principle: Visual analogies succeed by making the invisible visible through structural correspondence. Every element must earn its place by revealing structure.

阶段1：诊断（我要展示什么？）

提取核心关系结构
分类问题类型（6W）
识别意象图式

阶段2：生成（它像什么？） 4. 找到具有结构匹配的源领域 5. 创建明确的映射表 6. 测试涌现见解（整合） 7. 设置SQVID参数

阶段3：构建（我如何展示它？） 8. 将关系转换为空间结构 9. 构建渐进式层级（0-4） 10. 通过心理模拟验证

阶段4：优化（我可以删除什么？） 11. 运行反模式检查 12. 应用结构有效性测试 13. 迭代直到实现结构清晰

贯穿始终：牢记理论依据

Gentner：匹配关系结构，而非表面特征
Lakoff & Johnson：将抽象概念基于空间体验
Tversky：空间关系承载概念关系
Tufte：最大化信息，最小化冗余
Hofstadter：类比通过新颖映射创造见解

元原则：视觉类比通过结构对应使不可见的内容可见。每个元素都必须通过揭示结构来证明其存在的合理性。

Part 5: Animated Visual Storytelling

第五部分：动画视觉叙事

When the medium is video or interactive composition (not a static image), time becomes a structural dimension. Animation controls attention, reveals relationships sequentially, and creates emotional response through pacing.

当媒介是视频或交互式作品（而非静态图像）时，时间成为结构维度。动画控制注意力，按顺序揭示关系，并通过节奏营造情感反应。

5.1: Narrative Arc for Technical Explainers

5.1：技术讲解的叙事弧线

Every animated visualization needs a story structure with clear beats. Dead time kills engagement.

The 5-beat arc:

Hero moment (0-15% of duration): The subject fills the frame. Close camera. The viewer understands WHAT they're looking at before anything happens. Never start zoomed out — earn the wide shot.
The question (15-25%): Pose the problem or choice. Text overlay: "How do you render it?" This creates tension that the rest of the animation resolves.
The mechanism (25-55%): Show HOW the system works. This is where the structural analogy plays out spatially. Side-by-side comparisons are powerful here — the viewer's eye races between the two approaches.
The punchline (55-70%): The payoff. The parallel side finishes while the sequential side is still going. The "4× faster" moment. This should arrive when the viewer is primed but not bored.
The hold (70-100%): Let the conclusion breathe. Camera orbits toward the winner. But don't hold too long — 3-4 seconds max, not 30% of the video.

Common timing mistake: The punchline arrives too late. If the video is 14 seconds, the punchline should hit by second 10, not second 13.

每个动画可视化都需要清晰的故事结构和节奏。无效的时间安排会降低参与度。

5节拍弧线：

主角时刻（时长0-15%）：主体填满画面。镜头拉近。在任何动作发生前，让观众明白他们看到的是什么。永远不要从远景开始——要逐步过渡到广角镜头。
提出问题（15-25%）：提出问题或选择。文本叠加：“如何渲染它？”这会制造张力，后续动画将解决该问题。
展示机制（25-55%）：展示系统如何运作。这是结构类比在空间上发挥作用的部分。并排对比非常有效——观众的目光会在两种方法之间来回切换。
点睛之笔（55-70%）：回报时刻。并行处理的一侧完成，而串行处理的一侧仍在进行。“快4倍”的时刻。这应该在观众做好准备但尚未感到厌烦时出现。
收尾停留（70-100%）：让结论自然呈现。镜头向获胜方环绕。但不要停留太久——最多3-4秒，而非视频时长的30%。

常见时间错误：点睛之笔出现太晚。如果视频时长14秒，点睛之笔应在第10秒前出现，而非第13秒。

5.2: Camera as Attention Director

5.2：镜头作为注意力引导器

Camera position is not neutral — it IS the viewer's focus.

Camera rules:

Start close, earn the wide shot: Begin with the subject filling the frame. Pull back only when you need to reveal context (new elements, comparison). The pull-back itself is a narrative beat.
Pull back BEFORE new elements appear: If you're going to add worker nodes below the timeline, pull the camera back first so there's room. Never let elements appear off-screen.
Orbit toward the winner: In a comparison, the camera should drift toward the winning side in the final act. The loser recedes. The viewer's perspective literally shifts to favor the answer.
Snap zoom for emphasis: When the key metric appears ("4× faster"), a quick 200-300ms zoom snap toward it, then ease back. This is the visual equivalent of bold text.
Subtle shake during activity: Very light camera vibration (0.01-0.02 units) during processing phases makes the scene feel alive. Too much is nauseating.

镜头位置并非中立——它就是观众的焦点。

镜头规则：

从近景开始，逐步过渡到广角：从主体填满画面开始。仅在需要揭示背景（新元素、对比）时拉远镜头。拉远本身就是一个叙事节拍。
在新元素出现前拉远镜头：如果你要在时间轴下方添加工作节点，先拉远镜头留出空间。永远不要让元素从画面外突然出现。
向获胜方环绕：在对比场景中，镜头应在最后阶段向获胜方移动。失败方逐渐退去。观众的视角会实际转向支持答案。
快速缩放强调重点：当关键指标出现（如“快4倍”）时，快速200-300ms缩放至该指标，然后缓慢恢复。这相当于视觉上的粗体文本。
活动期间轻微震动：在处理阶段，镜头轻微震动（0.01-0.02单位）会让场景更生动。震动过大会让人不适。

5.3: Comparison Visualization (The Race Pattern)

5.3：对比可视化（竞速模式）

When showing "our way vs the old way," a side-by-side race is far more compelling than sequential before/after.

The race pattern:

Start unified: Show one object (the composition, the data, the process)
Dramatic split: A laser cut, a flash, a duplication event. This is a story beat, not a quiet transition.
Label immediately: "Traditional" (dim) vs "Editframe" (bright). Use brand names, not abstract CS terms.
Race simultaneously: Both sides process at the same time. The viewer's eye bounces between them. Progress indicators make the speed difference visible.
Winner finishes first: The fast side completes while the slow side is visibly behind. Hold this moment — it's the proof.

Color coding emotion:

Slow/old/bad: warm tones (orange, amber), dimmer, lower opacity
Fast/new/good: cool tones (blue, teal), brighter, higher emissive

当展示“我们的方法 vs 旧方法”时，并排竞速比顺序的前后对比更有吸引力。

竞速模式：

统一开始：展示一个对象（合成内容、数据、流程）
戏剧性拆分：激光切割、闪光、复制事件。这是一个叙事节拍，而非平淡的过渡。
立即标注：“传统方式”（暗淡） vs “Editframe”（明亮）。使用品牌名称，而非抽象的计算机科学术语。
同步竞速：两侧同时处理。观众的目光会在两者之间来回移动。进度指示器会让速度差异可视化。
获胜方先完成：快速的一侧完成时，慢速的一侧明显落后。停留这一刻——这就是证据。

颜色编码情感：

慢/旧/差：暖色调（橙色、琥珀色），更暗，更低透明度
快/新/好：冷色调（蓝色、蓝绿色），更亮，更高发光度

5.4: Concrete > Abstract

5.4：具象 > 抽象

Every element must represent something the viewer recognizes.

The "box + label" trap: The default failure mode is abstract boxes with labels ("SERIALIZE", "INITIALIZE", "F₁"). These communicate nothing — they're just a flowchart with shadows.

Better: Show a timeline that looks like a real editor timeline (multi-track, varied clip lengths). Show worker nodes that pulse and glow during processing. Show progress bars that fill at different rates. Show particles streaming through active nodes. The viewer should understand what's happening even without the text labels.

Metrics close the sale: "4× faster" is concrete. "Parallel processing" is abstract. Always end with a measurable claim.

每个元素都必须代表观众能识别的事物。

“方框+标签”陷阱：常见的失败模式是带标签的抽象方框（“SERIALIZE”、“INITIALIZE”、“F₁”）。这些传达不了任何信息——它们只是带阴影的流程图。

更好的做法：展示看起来像真实编辑器时间轴的时间轴（多轨道、不同剪辑长度）。展示处理期间会脉动和发光的工作节点。展示以不同速率填充的进度条。展示在活动节点中流动的粒子。即使没有文本标签，观众也应能理解正在发生的事情。

指标促成转化：“快4倍”是具象的。“并行处理”是抽象的。始终以可衡量的结论结束。

5.5: Sizing for the Medium

5.5：适配媒介的尺寸

Objects need to be significantly larger than you think for rendered video output.

Rules of thumb:

If an element is smaller than 5% of the frame width, it's invisible in the rendered output
Progress bars need to be at least 3-4% of frame height to be visible
Text overlays need 50% larger font than you'd use in a web page (the video has lower effective resolution)
Particle effects need to be 2-3× larger than looks good in live preview (they compress poorly)
Test by rendering and watching the output, not by looking at the live preview

对于渲染视频输出，对象需要比你想象的大得多。

经验法则：

如果元素小于画面宽度的5%，在渲染输出中会不可见
进度条需要至少占画面高度的3-4%才能可见
文本叠加的字体需要比网页中使用的大50%（视频的有效分辨率更低）
粒子效果需要比实时预览中看起来合适的大2-3倍（它们压缩效果差）
通过渲染并观看输出测试，而非仅看实时预览

5.6: 3D as a Structural Tool

5.6：3D作为结构工具

3D perspective adds depth hierarchy and professional polish, but it must serve the structure.

When 3D helps: Showing parallelism (side-by-side lanes), hierarchy (above/below), progression (near/far from camera), emphasis (closer = more important)

When 3D hurts: When the concept is inherently 2D (flowcharts, timelines). When the perspective distortion obscures the comparison. When it's purely decorative.

3D lighting communicates: Brighter = active/important. Shadows = grounding/reality. Emissive glow = energy/processing. Specular highlights = quality/polish.

3D视角增加了深度层级和专业质感，但必须服务于结构。

3D有用的场景：展示并行性（并排通道）、层级（上方/下方）、进展（离镜头近/远）、强调（越近越重要）

3D有害的场景：当概念本质上是2D时（流程图、时间轴）。当透视扭曲模糊了对比时。当它纯粹是装饰性时。

3D灯光传达信息：更亮=活跃/重要。阴影=真实感/落地。发光=能量/处理。镜面高光=质感/精致。

Additional Resources

额外资源

For detailed worked examples (technical debt, network effects, compound interest, etc.) and domain-specific pattern libraries, see examples.md.

For advanced techniques (progressive disclosure, constraint highlighting, diachronic comparison) and common failure modes with corrections, see advanced.md.

如需详细的实践示例（技术债务、网络效应、复利等）和特定领域的模式库，请查看examples.md。

如需高级技术（渐进式披露、约束高亮、历时对比）和常见失败模式及修正方法，请查看advanced.md。