Transfer solutions across domains by mapping the structure of the problem

When stuck, search for problems in other domains with the same relational structure.

Why it works

Analogical transfer — applying a solution from one domain to a structurally similar problem in another — is how many important innovations happen. The challenge is that people naturally search for solutions in the same domain as the problem, missing the structurally similar solutions in adjacent fields. Explicitly abstracting the relational structure of the problem (a "schema") and searching for that schema in other domains opens the solution space.

How to do it

1. Describe the problem purely in relational terms, removing all domain-specific vocabulary.
2. Ask: "What other domains deal with this same abstract relationship?"
3. Investigate how those domains solve the problem.
4. Map the solution back to your domain, checking which elements transfer and which do not.

Evidence

Analogical transfer is well documented in problem-solving research; Gick and Holyoak’s classic work showed that presenting a structural analogy helped subjects solve Duncker’s radiation problem. Transfer occurs more reliably when subjects are prompted to notice the structural similarity rather than discovering it spontaneously. (observational)

Spontaneous analogical transfer is rare; explicit prompting to consider analogies is usually required. The solution also needs to actually apply to the target, which requires verification, not just structural resemblance.

Sources

• Gick & Holyoak (1980), "Analogical problem solving," Cognitive Psychology, 12(3), 306–355

Common mistake

Doing the abstract relational description once and declaring victory — the transfer only works if the solution is actually re-mapped back to the target domain in concrete, actionable terms.