Far-Analogy Ideation

Most ideation transfers solutions from near domains (products like yours), which yields obvious, low-novelty ideas. Far-analogy ideation deliberately reaches to distant domains - nature, other industries, games, history - and transfers the deep relational structure of a working solution there, not its surface features. The originality comes from the distance; the validity comes from mapping structure, not surface similarity. The output is a far-analogy transfer sheet of candidate mechanisms to adapt. The failure to avoid: surface-matching ("both involve networks"), which produces cute-but-useless analogies and carries none of the benefit.

When to Use

• Near, obvious solutions are exhausted or all look alike.
• You want genuinely original approaches, not incremental variations.
• The problem has a clear underlying structure that can be stated abstractly.

When NOT to Use

• An obvious near solution already exists and works (far analogy is overkill and riskier).
• When you need to converge and decide (use a decision skill).
• When only a surface match is available (a forced, surface-level analogy is worse than none).
• Execution tasks with no real ideation need.

Instructions