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.
Why it works
Gentner’s progressive alignment principle shows that people learn abstract relational structure best when they first compare highly similar cases — where the structural mapping is easy to see — and then extend that structure to more distant cases. This works because the initial close comparison activates the relational structure explicitly; once it is explicit, it can be re-applied to distant cases where surface features no longer provide the scaffolding. Starting with distant analogies forces learners to deal with surface noise before they have isolated the structure.
How to do it
- When trying to understand a new concept, start by comparing two similar cases where the structure is clear.
- Name the structural relationship explicitly before moving to a more distant case.
- Apply the named structure to the distant case, and check whether it still holds.
- Each level of distance should test and extend the structural understanding, not skip it.
Evidence
Progressive alignment has experimental support in Gentner’s research: children and adults learn relational concepts faster when comparisons proceed from similar to distant rather than the reverse. (observational)
Most direct evidence is from learning studies in controlled settings; transfer to professional problem-solving is theoretically grounded but less directly studied.
Sources
- Kotovsky & Gentner (1996), "Comparison and categorization in the development of relational similarity," Child Development
Common mistake
Starting with the exotic, distant analogy that feels clever and impressive rather than building the structural understanding from simpler cases first — the result is a metaphor that illuminates the speaker more than the problem.
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 multiple analogies for the same problem
Draw on at least two different analogies for a new problem and see where they agree and diverge.
- 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.