# 🔗 Analogies and Unusual Connections

By Better Wise

You have two generators in your toolkit already: mind mapping to spread out the obvious, and SCAMPER to bend an idea in seven directions. Both of them work mostly inside your own problem space. This lesson does something different. It leaves the room. You go find a mechanism that already works somewhere else, in a domain that has nothing to do with your problem, and you carry it back.

Why bother? Because the first ideas you produce are almost always the ones everyone else produces too. Borrowing from a distance is how you get options that no one in your competitive set would think to try.

By the end of this lesson you can:

- Explain the difference between a surface analogy and a structural analogy
- Run a three-step transfer: extract the mechanism, abstract it, reapply it
- Pick source domains that are far enough away to be useful
- Test a transferred idea cheaply before committing to it

## Surface Look-Alikes vs. Structure That Travels

Most analogies people make are cosmetic. "Our app should be like Uber, but for dog walkers." That tells you almost nothing except the business model you already knew. It copies the surface.

A structural analogy copies the mechanism: the part that makes the thing work. Uber's real mechanism is not "an app with a map." It is *idle capacity matched to demand in real time, with trust handled by a rating layer*. That mechanism travels. It can be reapplied to unused parking spots, to empty delivery vans on return trips, to spare hours of a skilled retiree.

Here is the test. Ask: **if I stripped away the brand, the industry, and the visual style, what rule is still operating?** Whatever survives is the mechanism, and the mechanism is what you borrow.

| Surface analogy | Structural analogue | Mechanism you can move |
| --- | --- | --- |
| "Like Netflix for books" | Library hold queues | Scarcity resolved by waiting lists, not inventory |
| "Like a Ferrari for cooking" | Formula 1 pit stop | Parallel work split across specialized roles |
| "Like Tinder for jobs" | Emergency room triage | Fast reject, fast route, no queue for the clear cases |

> **Note:** 
> A useful analogy is one where you can name the mechanism in a single sentence and then point to at least two other places that same sentence is true.

## The Three-Step Transfer

This is the whole technique. It takes about ten minutes once you are warmed up.

```mermaid
flowchart TD
    A["🔍<br/>Pick a distant domain"] --> B["⚙️<br/>Name the mechanism"]
    B --> C["🧩<br/>Abstract it to a rule"]
    C --> D["🎯<br/>Force it onto your problem"]
    D --> E["🧪<br/>Sketch a cheap test"]
```

**Step 1, pick a distant domain.** Distance is the point. If your problem is about onboarding new employees, do not look at other onboarding programs. Look at the first fifteen minutes of a swimming lesson, at how a hostel welcomes a stranger, at how a game teaches its controls without a manual.

**Step 2, name the mechanism in one sentence.** "The swimming instructor gets you into the water before teaching any stroke, because fear of water blocks learning technique." No jargon. If you cannot say it plainly, you have not found the mechanism yet.

**Step 3, abstract it into a rule.** Strip the specifics until it becomes a principle: *remove the feared element first, then teach the skill.* Now it can dock anywhere.

**Step 4, force the transfer.** Apply the abstracted rule to your problem and complete this sentence: "In my situation, the feared element is ____, so I would remove it by ____."

**Step 5, sketch a cheap test.** Every transferred idea sounds cleverer than it is. Write down the smallest thing you could build in an afternoon to see whether the mechanism actually holds.

### Exercise: Run one transfer now

Pick the domain *emergency room triage*. Name its mechanism in one sentence, abstract it, then apply it to your capstone problem.

**Check your thinking**

A reasonable answer: the mechanism is "patients are sorted by severity within seconds of arrival, so critical cases never wait behind routine ones." The abstract rule: **route by severity before serving by arrival order.** Applied to a capstone about, say, a course feedback tool, that becomes: surface the one comment that signals a learner about to drop out at the top, instead of listing all comments by date. A cheap test: manually re-sort last month's feedback by urgency and ask three instructors which view they would act on first.

If your answer described what an ER *looks like* rather than how it *decides*, go back to step 2.

## Where to Look for Unusual Sources

Randomness is not the same as distance. You want sources that are structurally rich and mechanically explicit. Five buckets that reliably produce material:

1. **Craft and trade.** Bakers, welders, bookbinders. These domains make tacit rules visible because mistakes are expensive.
2. **Nature and biology.** Immune systems, mycelium networks, seed dispersal, molting.
3. **Games and sport.** Rules, scoring, handicaps, turn order, respawn.
4. **Everyday rituals.** Airport security, queuing at a bakery, the first day of school.
5. **Institutions.** Courtrooms, museums, blood banks, fire stations.

A surface analogy copies what a thing _____, while a structural analogy copies the _____ that makes it work.
The transfer step is to state the mechanism as a _____ that survives when the original domain is stripped away.
Borrowing from a _____ domain produces more original options than borrowing from a near neighbor in the same industry.
Every transferred idea needs a cheap _____ before you trust it.

### Exercise: Five sources, ninety seconds

Set a timer. Write one mechanism from each of the five buckets above, in one sentence each. Then circle the one that makes you slightly uncomfortable because you cannot yet see how it would fit your project. That one is your best candidate.

**Guidance**

Discomfort is a useful signal here. An analogy that fits too easily is probably a surface analogy in disguise, or something you already knew. The one that resists translation is the one that forces a genuinely new option. Do not discard it because the mapping is incomplete. Partial mappings generate the interesting half-ideas.

## Keeping Analogies Honest

Borrowed ideas fail in two predictable ways. First, **the mapping breaks silently**: the source mechanism depended on a condition your problem does not have. Hospitals triage by severity because a delay can kill. If your users face no real cost for waiting, severity routing adds friction for nothing. Second, **the novelty carries the argument**: the idea feels fresh, so nobody tests whether it works. Freshness is not evidence.

The guard against both is the same discipline you used in the last lesson: write down the assumption the transfer depends on, then design the smallest test that could prove it wrong. If the analogy survives one honest test, you have earned the right to build more of it.

## Field Notes for Borrowing Ideas

- **Name the mechanism before you name the idea.** If you cannot say the source's rule in one sentence, you are about to copy a surface.
- **Go two domains away, not one.** One step away gives you competitors. Two steps gives you structure.
- **Write the failure condition first.** "This works only if ____" tells you what to test.
- **Common mistake: collecting analogies instead of transferring them.** A notebook full of clever parallels is not progress. One transfer that reaches a sketchable test beats twenty observations.
- **Rule of thumb: three transfers per problem.** After three, you start producing variations of the same mechanism.

## What to Carry Forward

- Structural analogies transfer mechanisms; surface analogies transfer looks.
- The transfer runs: distant domain, mechanism in one sentence, abstract rule, forced application, cheap test.
- Discomfort at the mapping stage is a good sign, not a problem to fix.
- Every borrowed mechanism rests on a condition. Name it and test it.

Next, the checkpoint brings mind mapping, SCAMPER, and this transfer method together so you can choose the right generator for the state your idea is in.

Front: Surface analogy vs. structural analogy
Back: Surface copies what a thing looks like; structural copies the mechanism that makes it work.

Front: What question reveals a mechanism?
Back: If I strip away brand, industry, and style, what rule is still operating?

Front: Uber's transferable mechanism
Back: Idle capacity matched to demand in real time, with trust handled by a rating layer.

Front: First step of the transfer process
Back: Pick a source domain that is distant from your problem, not adjacent to it.

Front: How plainly must the mechanism be stated?
Back: In one sentence, no jargon; if you cannot, you have not found it yet.

Front: What does step 3, abstraction, produce?
Back: A general rule with the original domain's specifics stripped out, so it can dock anywhere.

Front: The forced-transfer sentence
Back: 'In my situation, the feared element is ____, so I would remove it by ____.'

Front: Why sketch a cheap test for every transfer?
Back: Transferred ideas feel cleverer than they are; a small test checks whether the mechanism holds.

Front: Five reliable source buckets
Back: Craft and trade, nature and biology, games and sport, everyday rituals, institutions.

Front: Why is discomfort a good signal at the mapping stage?
Back: An analogy that fits too easily is likely a surface analogy or something you already knew.

Front: How failure mode one: the mapping breaks silently
Back: The source mechanism depended on a condition your problem does not have.

Front: How failure mode two: novelty carries the argument
Back: The idea feels fresh, so nobody tests whether it actually works.

Front: Rule of thumb for number of transfers per problem
Back: Three; beyond that you start producing variations of the same mechanism.

Front: Guard against both analogy failure modes
Back: Name the assumption the transfer depends on, then design the smallest test that could disprove it.

---

## Contents

Part of [🧠 Original Creativity: Generate Ideas Beyond the Obvious](https://everwise.study/courses/original-creativity-generate-ideas-beyond-the-obvious.md)

- **🧭 Foundations: Thinking Modes and Observation**
  - [🔀 Divergent and Convergent Thinking: One Loop](https://everwise.study/courses/original-creativity-generate-ideas-beyond-the-obvious/divergent-and-convergent-thinking.md)
  - [🔍 Observation: Noticing What Others Walk Past](https://everwise.study/courses/original-creativity-generate-ideas-beyond-the-obvious/observation-for-creative-ideas.md) (sign-in required)
  - [🔒 Creative Constraints: Turning Limits into Levers](https://everwise.study/courses/original-creativity-generate-ideas-beyond-the-obvious/creative-constraints.md)
  - [✅ Checkpoint: Thinking Modes and Observation](https://everwise.study/courses/original-creativity-generate-ideas-beyond-the-obvious/checkpoint-thinking-modes-observation.md)
- **🗺️ Generating Options: Mapping, SCAMPER, Analogies**
  - [🕸️ Mind Mapping and Clustering: Brain Dump to Themes](https://everwise.study/courses/original-creativity-generate-ideas-beyond-the-obvious/mind-mapping-and-clustering.md)
  - [🔧 SCAMPER: Seven Prompts to Stretch an Idea](https://everwise.study/courses/original-creativity-generate-ideas-beyond-the-obvious/scamper-prompts.md)
  - [🔗 Analogies and Unusual Connections](https://everwise.study/courses/original-creativity-generate-ideas-beyond-the-obvious/analogies-and-unusual-connections.md) — this lesson
  - [✅ Checkpoint: Idea Generation Techniques](https://everwise.study/courses/original-creativity-generate-ideas-beyond-the-obvious/checkpoint-idea-generation-techniques.md)
- **🧪 Challenge, Augment, and Test**
  - [🎩 Reverse Brainstorming and Six Thinking Hats](https://everwise.study/courses/original-creativity-generate-ideas-beyond-the-obvious/reverse-brainstorming-and-six-hats.md)
  - [🤖 AI as a Sparring Partner, Not an Answer Key](https://everwise.study/courses/original-creativity-generate-ideas-beyond-the-obvious/ai-as-sparring-partner.md)
  - [🚀 Capstone: Original Concept Brief and Test Plan](https://everwise.study/courses/original-creativity-generate-ideas-beyond-the-obvious/capstone-concept-brief-and-test-plan.md) (premium content)
  - [✅ Checkpoint: From Concept to Test](https://everwise.study/courses/original-creativity-generate-ideas-beyond-the-obvious/checkpoint-concept-to-test.md) (premium content)
- [Course cheatsheet](https://everwise.study/courses/original-creativity-generate-ideas-beyond-the-obvious/cheatsheet.md) (premium content)