Use multiple analogies for the same problem
Draw on at least two different analogies for a new problem and see where they agree and diverge.
Why it works
Any single analogy highlights certain relationships and hides others. Using multiple analogies for the same target forces the different structural mappings to compete, which reveals which relational features are robust (they appear in every mapping) and which are artifacts of one particular base domain. The overlap between multiple analogies is more likely to capture something real; the divergence reveals where each analogy is doing ideological rather than cognitive work.
How to do it
- For a new problem, generate two or three analogies from different domains.
- Map the relational structure for each.
- Identify which conclusions appear in all mappings — those are most reliable.
- Identify where the analogies point in different directions — those are the genuinely uncertain areas.
Evidence
Multiple-source analogy is a principle endorsed in creative cognition and design thinking research; using multiple analogies reduces the over-fitting to one source domain that single analogies risk. (mechanistic)
The research here is more theoretical than experimental; generating high-quality multiple analogies requires strong knowledge of multiple domains.
Sources
- Gentner & Colhoun (2010), analogical processes in human thinking, Psychological Science — multiple analogies and robust inference
Common mistake
Using two analogies that are actually the same structural mapping in different surface dressing — they both need to come from genuinely different base domains to provide distinct structural perspectives.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for Analogical Reasoning
- Map the relational structure, not the surface features
Ask what relationships are shared between domains, not just what objects look similar.
- Use progressive alignment: start with similar cases and move to more distant ones
Learn relational structure by comparing easy cases before applying the same structure to harder ones.
- Check for false analogies: does the structural mapping actually hold?
Test whether a compelling analogy survives scrutiny of its relational structure.
- Transfer solutions across domains by mapping the structure of the problem
When stuck, search for problems in other domains with the same relational structure.
- Build a library of cases and reason from them
Accumulate a diverse set of cases with known outcomes, and retrieve structurally similar ones when facing a new problem.