Back to Details

cross-domain

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
A problem that resists its own field's first principles has often been solved elsewhere, years ago, under a different name. Strip the jargon until the structure shows, find the isomorphic problems distant fields have already met, and transfer the mechanisms that solved them — only the parts that survive the move.
Write in the language the user writes in.
某个领域内用自身第一性原理无法解决的问题，往往早已在其他领域以不同名称被解决。剥离专业术语直至问题的底层结构显现，找到其他领域已经遇到的isomorphic问题，并transfer解决这些问题的mechanisms——只保留那些跨领域适用的部分。
使用用户所使用的语言进行输出。

1. Strip the jargon

1. 剥离专业术语

If the argument is missing or lacks the specific sticking point, ask one question for the missing piece and stop.
Restate the problem as one a person in any field could face — nouns replaced by roles (a scarce resource, a feedback loop, a trust gap, a queue). Then find three things:
  • Underlying structure — the shape of the problem once the roles are named.
  • Core tension — the two things that cannot both be had, stated as X pulls against Y because Z. The sticking point is a symptom of it.
  • Why ordinary solutions fail — the fixes the user's field reaches for, and the specific reason each one breaks against that structure.
Synonyms are not abstraction: a restatement that keeps the field's nouns turns step 2 into a search for neighbours. Test it: a nurse, a farmer and a general should each be able to say "I have had that one." If a solution the user's field already uses would resolve the tension as stated, the tension is not yet the core one.
Done when the restatement contains no term from the user's field, and names the underlying structure, the core tension as two things pulling against each other, and one specific reason each ordinary solution fails.
如果问题描述缺失或未明确具体卡点，仅询问一个补充信息的问题即可停止。
将问题重述为任何领域的人都可能遇到的通用问题——用角色替代具体领域名词（如稀缺资源、反馈循环、信任缺口、队列）。随后找出三点内容：
  • Underlying structure — 明确角色后呈现的问题形态。
  • Core tension — 无法同时实现的两个目标，表述为X与Y相互冲突，原因是Z。卡点是这一矛盾的表现。
  • 常规解决方案失效的原因 — 用户所在领域常用的解决办法，以及每种办法与问题底层结构冲突的具体原因。
同义词替换并非抽象提炼：若重述仍保留领域专有名词，会导致第二步变成在相近领域寻找问题。验证标准：护士、农民和将军都能说出“我遇到过这类问题”。如果用户所在领域已有的解决方案就能解决当前表述的矛盾，说明该矛盾并非核心矛盾。
完成标志：重述内容不含用户所在领域的术语，明确指出underlying structure、core tension（即两个相互冲突的目标），以及每种常规解决方案失效的具体原因。

2. Find isomorphic problems

2. 寻找isomorphic问题

Search historical cases and at least three fields for problems with the same underlying structure. Choose fields distant from each other and from the user's — distance measured by how little the practitioners would recognise each other's vocabulary. Historical cases come in addition to the three fields, and each carries a documented outcome.
Match on structure: a case that shares the user's nouns but faces a different tension is decoration; a case with alien nouns that faces the same tension, and whose ordinary solutions failed for the same reason, is isomorphic.
Where memory of a case is thin, 
WebSearch
it; replace any case you cannot pin to a real field, a time and an outcome.
Done when there are historical cases, each with a documented outcome, and at least three fields, each distant from every other and from the user's, and every case passes the same-tension, same-failure test.
搜索历史案例及至少三个领域中具有相同underlying structure的问题。选择彼此之间、且与用户所在领域差异较大的领域——差异程度以从业者能否理解彼此的专业词汇为衡量标准。历史案例需额外补充，且每个案例都有记录在案的结果。
匹配标准为结构：若案例与用户问题共享领域名词但面临不同矛盾，则仅为表面相似；若案例使用完全陌生的名词，但面临相同矛盾，且常规解决方案因相同原因失效，则属于isomorphic问题。
若对某个案例记忆模糊，使用
WebSearch
检索；替换所有无法明确对应真实领域、时间和结果的案例。
完成标志：拥有多个带有记录结果的历史案例，以及至少三个彼此独立且与用户领域差异较大的领域案例，且所有案例都通过“相同矛盾、相同失效原因”测试。

3. Take each case apart

3. 拆解每个案例

For each case, in this order:
  1. What problem that field faced.
  2. The mechanism it used.
  3. Where it is similar to the user's problem.
  4. Which parts transfer.
  5. Under what conditions it fails.
The mechanism is the causal move, not the policy's name: "triage" is a name; "sort by marginal benefit of intervention rather than by severity" is the mechanism. Transfer names parts: the parts that ride on the shared structure move, the parts that ride on the field's own conditions stay behind. Failure conditions are the ones under which the mechanism stops working or backfires, written so the user can check their own situation against them.
Done when every case carries all five items, each mechanism reads as a causal move, each transfer names parts, and each failure condition is checkable against the user's situation.
针对每个案例，按以下顺序梳理：
  1. 该领域曾面临的问题。
  2. 所采用的mechanism。
  3. 与用户问题的相似之处。
  4. 可transfer的部分。
  5. 失效的条件。
mechanism指的是因果性举措，而非政策名称：“分诊（triage）”是名称；“按干预的边际效益而非严重程度排序”才是mechanism。Transfer指的是可迁移的部分：基于共享结构的部分可以迁移，基于领域特有条件的部分则需保留。失效条件指的是mechanism停止作用或产生反效果的场景，需以用户可对照自身情况检查的方式表述。
完成标志：每个案例都包含上述五项内容，每个mechanism都被表述为因果性举措，每个transfer都明确可迁移部分，且每个失效条件都可对照用户自身情况进行检查。

4. Select and translate three mechanisms

4. 筛选并转化三个mechanisms

Choose the three mechanisms most worth borrowing. Rank by how directly each attacks the core tension and how much of it transfers; a clever mechanism that touches a symptom loses to a plain one that hits the tension.
Translate each into a solution fitted to the user's situation — back into their vocabulary, inside their constraints, starting from their current approach. Name what changes, what it costs, and the failure condition from step 3 restated as the sign to watch for. "Do what that field did" is a pointer, not a translation; the translation is something the user could start.
Done when three mechanisms are each translated into the user's own terms, and each names the change, its cost, and its failure sign.
选出三个最值得借鉴的mechanisms。排序标准为：对core tension的直接攻击程度，以及可迁移的范围；针对症状的巧妙mechanism，不如直击核心矛盾的朴素mechanism。
将每个mechanism转化为适配用户场景的解决方案——回归用户的专业词汇，在其约束条件内，基于当前方法进行调整。明确指出需要改变的内容、所需成本，以及将第三步中的失效条件重述为需要警惕的信号。“照搬该领域的做法”只是指引，而非转化；转化后的方案需是用户可以立即着手实施的内容。
完成标志：三个mechanisms均已转化为用户的专属术语表述，且每个方案都明确了变更内容、成本及失效预警信号。

5. Recommend the first experiment, then deliver

5. 推荐首个实验方案，然后交付成果

From the three solutions, design the minimum experiment most worth running first. Low-cost: cheap enough, in money and effort, to run without asking anyone's approval. Reversible: undone without residue if it fails. Prefer the experiment that tests the core tension fastest over the mechanism that promises most. State the result that confirms the mechanism transfers and the result that kills it.
Deliver, in this order:
  • Abstracted problem — jargon-free: the underlying structure, the core tension, and why ordinary solutions fail.
  • Cases — the historical cases and at least three distant fields, each with its five items in order.
  • Three mechanisms — each named as a causal move and translated into the user's situation, with its change, cost and failure sign.
  • First experiment — the minimum experiment: low-cost and reversible, with its confirming and killing results and how to undo it.
Done when the experiment names its cost, its reversal, and its confirming and killing results, and every deliverable above is present in order.
从三个解决方案中，设计首个最值得开展的最小化实验。实验需满足：低成本——在资金和精力上足够低廉，无需征得他人批准即可开展；可逆转——若失败可完全撤销且无残留影响。优先选择能最快验证core tension的实验，而非预期收益最高的mechanism。明确指出可验证mechanism可迁移的结果，以及证明其不可行的结果。
按以下顺序交付成果：
  • 抽象后的问题——无专业术语：包含underlying structure、core tension，以及常规解决方案失效的原因。
  • 案例集合——历史案例及至少三个跨领域案例，每个案例按前述五项内容依次呈现。
  • 三个mechanisms——每个都以因果性举措命名，并转化为用户场景下的方案，包含变更内容、成本及失效预警信号。
  • 首个实验方案——最小化实验：具备低成本、可逆转特性，明确验证结果、否定结果及撤销方式。
完成标志：实验方案明确了成本、撤销方式、验证结果及否定结果，且所有交付内容按顺序完整呈现。