Core Idea
Definition
Analogical reasoning infers something about a target case by mapping relevant similarities from a better-understood source case.
In Plain English
You use a known situation as a model for a new one and ask which lessons truly carry over.
Framework Structure
Components
Flow
Choose familiar case -> Map deep similarities -> Transfer lesson cautiously -> Check where the analogy breaks
How to Apply
- 1.Choose a source example that is understood in more detail than the target problem
- 2.Identify the structural similarities rather than surface resemblance
- 3.State which properties are being transferred and why
- 4.List where the analogy may fail or stop applying
- 5.Use the analogy to generate hypotheses, then test them against the target reality
When to Use
- •Explaining complex ideas to others
- •Generating strategy from prior cases
- •Teaching, framing, and sensemaking
- •Innovation by adapting patterns across domains
- •Early-stage reasoning when direct models are weak
When NOT to Use
- •When the similarity is mostly aesthetic or rhetorical
- •When the domains differ on the variables that actually matter
- •When the analogy is being used as proof rather than as a guide
- •When precise measurement is available and should replace metaphor
Example
Problem
A founder wants to improve how a small product team handles work-in-progress.
Application
- 1.Choose restaurant kitchen flow as a source domain because throughput and congestion are visible there
- 2.Map the shared structure: queues, handoffs, bottlenecks, and overloaded stations
- 3.Transfer the lesson that too many simultaneous tickets slow the whole system
- 4.Adapt the idea into explicit work-in-progress limits for the product team
Conclusion
The team should reduce parallel work because the kitchen analogy reveals how visible busyness can lower total throughput.
Takeaway
A good analogy reveals an underlying structure you can reuse, not just a colorful comparison.
Common Mistakes
- •Using analogies that feel clever but hide key differences
- •Transferring conclusions without transferring constraints
- •Confusing narrative resonance with structural fit
- •Letting an analogy harden into dogma
- •Failing to specify the breakpoints of the comparison
How to Practice
structure not story
For each analogy you use, write down the exact relationship pattern being transferred.
analogy break test
Deliberately list three ways the analogy could fail so you do not mistake it for a proof.
cross domain reframe
Take one problem each week and explain it through a domain with very different surface features.
Related Cognitive Biases
surface similarity bias
People often overvalue visible resemblance and miss deeper structural differences.
halo effect
A respected source domain can make a weak analogy feel stronger than it is.
overconfidence
A satisfying analogy can create false certainty before the target case is tested directly.
Related Frameworks
Related Skills
Variants & Extensions
Typical Failure Modes
- •Superficial comparison
- •Ignoring disanalogies
- •Using analogy as proof
Further Reading
- Surfaces and Essences by Douglas Hofstadter and Emmanuel Sander
- The Model Thinker by Scott E. Page
- Made to Stick by Chip Heath and Dan Heath