Back to Details

analogy

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Forced Analogy (Structural Transplant)

Forced Analogy（结构移植）

What this technique does

该方法的作用

Take the problem, strip it down to its bare structure — who the actors are, what flows between them, where it jams — and find a system in a distant domain that has the same shape. An immune system, an air-traffic control tower, a restaurant kitchen at dinner rush. Then ask what that system does about the jam that you don't, and carry the mechanism back as a concrete idea. The point is distance: the further the source domain sits from your problem, the more its solutions will look nothing like the ones already on your whiteboard.
Source: Synectics (William J.J. Gordon, Synectics: The Development of Creative Capacity, 1961), specifically the "direct analogy" operation; widely used in biomimicry and TRIZ-adjacent practice.
将问题剥离至核心结构——参与者是谁、什么在他们之间流动、瓶颈在哪里——然后在遥远领域中找到具有相同结构的系统，比如免疫系统、空中交通管制塔、晚餐高峰期的餐厅后厨。接着思考该系统针对瓶颈的解决方案是当前未采用的，将其机制转化为具体思路应用到当前问题。关键在于领域的距离：源领域与你的问题越远，其解决方案就越不同于你已有的思路。
来源：Synectics（威廉·J·J·戈登，《Synectics：创造性能力的开发》，1961年），具体为“直接类比”操作；广泛应用于仿生学及TRIZ相关实践。

Workflow

工作流程

Step 1: Confirm the target

步骤1：确认目标

A valid target is a concrete creative or design problem: how to grow something, how to route something, how to redesign a process or a system. If it is unclear, ask one focused question — "What's the system you're trying to reshape, and where does it jam?"
Refuse requests to perform analytical work — debugging, reviewing code, implementing a change — and suggest an analytical approach instead. Redesigning or ideating about such a process is a valid creative target: "reinvent our code-review ritual" is in scope; "review this PR" is not.
有效的目标是具体的创意或设计问题：如何拓展业务、如何优化路径、如何重新设计流程或系统。若目标不明确，可提出一个聚焦问题——“你试图重塑的系统是什么，瓶颈出在哪里？”
拒绝执行分析类工作的请求——如调试、代码评审、实现变更——转而建议分析类方法。对这类流程进行重新设计或构思属于有效的创意目标：“重新设计我们的代码评审流程”在适用范围内；“评审此PR”则不在。

Step 2: State the problem's structure in one sentence

步骤2：用一句话描述问题的结构

Reduce the target to actors, flows, and the bottleneck. No domain vocabulary, no solution language — just the shape. For example: "many independent producers, one congested channel, quality varies." This sentence is the load-bearing part of the whole technique; if it still names your industry, it is not abstract enough yet.
将目标简化为参与者、流动环节和瓶颈。不要使用领域术语或解决方案相关表述——只描述结构。例如：“众多独立生产者，一条拥堵的渠道，质量参差不齐。”这句话是整个方法的核心；如果它仍能体现你的行业特征，说明抽象程度还不够。

Step 3: Draw 3-5 domains whose structure rhymes

步骤3：选取3-5个结构匹配的领域

Pull from 
references/domain-pool.md
. Choose domains whose structural property matches the sentence from Step 2, not domains that sound related to your problem. Mix at least one biological, one operational, and one social/cultural so the transplants come from genuinely different logics. Never run more than five in a batch.
从
references/domain-pool.md
中选取。选择结构特征与步骤2中句子匹配的领域，而非与问题表面相关的领域。至少包含一个生物领域、一个运营领域和一个社会/文化领域，确保迁移的机制来自完全不同的逻辑。每次批量选取不超过5个领域。

Step 4: Per domain, map roles then transfer a mechanism

步骤4：针对每个领域，先映射角色再迁移机制

For each domain, do two things in order:
  1. Map the roles. State plainly which part of your problem corresponds to which part of the domain: "our users are the foragers, our channel is the trail." If the mapping is clean, one line does it.
  2. Ask the transfer question: "What does this domain DO about the bottleneck that we don't?" Then carry 1-2 of its actual mechanisms back as concrete ideas for your problem — not the imagery, the mechanism.
针对每个领域，依次完成两件事：
  1. 映射角色。 明确说明问题的各部分对应领域的哪些部分：“我们的用户相当于觅食者，我们的渠道相当于觅食路径。”如果映射清晰，一句话即可说明。
  2. 提出迁移问题：“该领域针对瓶颈的解决方案有哪些是我们未采用的？”然后将1-2个实际机制转化为针对当前问题的具体思路——迁移的是机制，而非表象。

Step 5: Meta-pattern scan

步骤5：元模式扫描

After the batch, look across the mechanisms that transferred well and name the structural insight they share — "every domain that helped treated the bottleneck as a routing problem, not a volume problem." State it explicitly. This cross-domain observation is usually worth more than any single transplant.
完成批量迁移后，审视所有有效迁移的机制，总结它们共有的结构洞察——“所有有用的领域都将瓶颈视为路径规划问题，而非容量问题。”明确表述这一洞察。这种跨领域观察通常比单个迁移的价值更大。

Step 6: Honest ranking, no closure pressure

步骤6：如实排序，无决策压力

Pick the sharpest transplants. Say which are weak and why. Offer next moves — draw more domains, go deeper on one, switch technique, or stop — and let the user choose. Never push the user to commit.
选出最有价值的迁移方案。指出哪些方案较弱及其原因。提供后续行动选项——选取更多领域、深入研究某一方案、更换方法或停止——由用户选择。切勿强迫用户做出决策。

Honesty mechanics

如实性机制

One-forced-role rule. A clean mapping costs you one metaphorical leap. The moment a domain needs a second forced role to keep working — "well, if the ants were also the queen, and the trail were also the nest..." — the structure doesn't actually rhyme, and you are now decorating rather than transplanting. Abandon it visibly and say why.
Surface analogies are named and dropped. A domain that shares vocabulary with your target but not structure is the most seductive trap and the most useless. Call it out as surface-level and drop it. A batch where every domain transfers cleanly is a tell that the output is being retrofitted; expect at least one honest abandonment.
When no domain rhymes. If every domain needs a second forced role, the fault is usually the Step 2 sentence, not the domains. Rewrite it once. If the rewrite still names no bottleneck, stop drawing domains — name the diagnosis, suggest the technique that fits it as the user's next move, and stop there rather than running it yourself:
  • The structure sentence keeps coming out as a solution rather than a shape → suggest 
    concept-fan
    , which climbs until the real problem appears.
  • There is a genuine structure but nothing distant maps onto it → suggest 
    random-stimulus
    , which needs no structural rhyme to make a jump.
单一强制角色规则。 清晰的映射只需一次隐喻性跳转。当某个领域需要第二个强制角色才能继续匹配时——“嗯，如果蚂蚁同时也是蚁后，路径同时也是巢穴……”——说明结构并不真正匹配，此时你只是在做表面修饰而非结构移植。应明确放弃该领域并说明原因。
识别并舍弃表面类比。 与目标共享术语但结构不匹配的领域是最具诱惑性的陷阱，也是最无用的。要指出这是表面类比并舍弃。如果所有领域都能完美匹配，说明结果是刻意调整的；至少应有一个领域被如实舍弃。
无匹配领域的情况。 如果所有领域都需要第二个强制角色，问题通常出在步骤2的句子上，而非领域本身。重新改写一次句子。如果改写后的句子仍未明确瓶颈，则停止选取领域——说明诊断结果，建议用户使用适合的方法，而非继续执行当前方法：
  • 结构句子始终偏向解决方案而非结构描述 → 建议使用
    concept-fan
    方法，直到找到真正的问题。
  • 存在明确结构但无遥远领域可匹配 → 建议使用
    random-stimulus
    方法，无需结构匹配即可实现思路跳转。

What NOT to do

禁忌事项

  • Don't pick domains that share vocabulary with the target. Software-to-marketplace, app-to-platform — too close. The shared words hide the fact that no real transfer happened. The whole value is distance.
  • Don't transfer aesthetics instead of mechanisms. "A coral reef is colorful and diverse, so our product should feel vibrant" is decoration, not a transplant. Transfer what the reef does (structure built by many small organisms becomes shelter for others), not how it looks.
  • Don't run more than 5 domains per batch. Returns diminish and the mappings blur together.
  • Don't rescue a domain that needs more than one forced role. Drop it and move on.
  • 不要选择与目标共享术语的领域。 软件到市场、应用到平台——距离太近。共享术语会掩盖未发生真正迁移的事实。该方法的核心价值在于领域的距离。
  • 不要迁移表象而非机制。“珊瑚礁色彩丰富、种类多样，所以我们的产品应充满活力”属于表面修饰，而非结构移植。要迁移珊瑚礁的运作机制（众多微小生物构建的结构成为其他生物的庇护所），而非其外观。
  • 每次批量选取不要超过5个领域。 收益会递减，映射也会变得模糊。
  • 不要挽救需要多个强制角色的领域。 直接舍弃并继续。

References

参考资料

  • references/domain-pool.md
     — structurally rich source domains to draw from, with the transferable property of each
  • references/worked-example.md
     — a real session showing the full shape, one genuine abandonment included
  • references/domain-pool.md
     —— 结构丰富的源领域库，包含每个领域的可迁移特征
  • references/worked-example.md
     —— 完整的实际案例，包含一个真实的舍弃过程