Cross-Disciplinary Creativity

Activate when: 'we need a breakthrough idea', 'everything in our industry looks the same', 'we've exhausted all options in our field', 'how do we innovate in a way no competitor has tried', 'need to think completely outside the box'. Do NOT activate when: home domain has a known solution needing better execution; user wants to brainstorm more options within their existing field.

Overview

Importing an actual mechanism from a foreign domain and applying it structurally to a home-domain problem — producing a configuration no expert in either field could conceive alone. Not metaphor-making; the mechanism must be imported structurally, not just referenced.

Sequencing: Use AFTER [first-principles] (decomposes home domain first). Use WITH [point-line-plane-solid] (plane→solid transition). Use BEFORE [non-consensus-thinking] (to hold the non-consensus position under expert pressure).

When to Use

Use when: industry is producing structurally similar solutions; a problem has resisted all home-domain attempts; you need radical differentiation from incumbents; a foreign technology has appeared that no one in your field has noticed.

When NOT to use: home domain has well-tested solutions needing better execution; synthesis produces only metaphors; foreign mechanism is poorly understood; hours-level time pressure (synthesis requires incubation).

Coaching Novices (Adaptive Front Door)

• Engine mode: user has a concrete case → run The Process directly.
• Coach mode: user unfamiliar or no concrete case → guide step by step.

In Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.

1. "The most valuable innovations are invented by people who apply a solution from one domain to a problem in another. This skill makes that transfer deliberate."
2. "Tell me the problem you're stuck on and what approaches have been tried. That domain boundary is where we look."
3. "Gutenberg imported the screw press from wine production, metallurgy from his trade, oil-based ink from painters, codex format from monks. None were new — the combination was unprecedented."

[WAIT — do not advance until user responds]

4. "Name your home-domain problem in one sentence. What three unrelated domains face the same underlying structural challenge? Pick the one you know least — that's where your mechanism may live."

[WAIT — do not advance until user responds]

5. "Structural novelty means solutions no competitor can copy, because the mechanism is invisible to them from inside their domain."

[WAIT — do not advance until user responds]

The Process

Gate: Confirm home-domain local search is genuinely exhausted before starting.

1. State the problem precisely — home domain, specific problem, what was tried and why it failed.
2. Map home-domain tools and assumptions — these are the boundaries you will cross.
3. Restate the problem structurally — strip domain-specific language to reveal the underlying challenge.
4. List 3 unrelated domains facing the same structural problem (ecology, military strategy, thermodynamics, game design…).
5. For each: name the specific mechanism it uses — not an analogy; a concrete process/structure/technique.
6. Force the combination — apply the foreign mechanism: what translates directly, what needs adaptation?

Stop-rule: Metaphor ("like going viral") → return to step 5. Mechanism (specific replication structure with calibrated parameters) → proceed.

Output: Cross-Domain Synthesis Map

text

Home domain / Problem: [Name] | [One precise sentence] | [Abstract structural restatement]
Home-domain attempts: [List + why each fell short]
Foreign domain 1: [Domain] | Structural equivalent | Mechanism | Translation proposal
Foreign domain 2: [Domain] | Structural equivalent | Mechanism | Translation proposal
Foreign domain 3: [Domain] | Structural equivalent | Mechanism | Translation proposal
Proposed combination: [Which mechanisms combined → new configuration]
Stop-rule: Mechanism or metaphor? (If metaphor: return to step 5)
Novel configuration: [What would be built or done differently]
First test: [Smallest experiment to confirm the mechanism works]

→ Method in Action: Gutenberg's Printing Press (c. 1440)

Packs

• Product/tech: Airbnb imported e-commerce reputation trust into physical space rental. Uber combined taxi dispatch logic with commodity-market dynamic pricing.
• Life sciences: CRISPR-Cas9 imported from bacterial immune systems into gene editing.
• Org design: Toyota imported Deming's statistical quality control (statistics) into automotive manufacturing.

Applying It Well

1. Mechanisms not metaphors — describe what would be built differently; if you can't, go deeper.
2. Distance = novelty — distant domains produce combinations incumbents cannot see.
3. Know the foreign mechanism deeply — surface-level borrowing produces gimmicks.
4. Structural abstraction is the bridge — "distributed node consistency" opens the problem to immunology, computing, evolutionary biology.
5. Expect expert resistance — signal of novelty, not error. Test before scaling — foreign mechanisms have unpredictable failure modes.

→ Primary sources: references/sources.md

Common Rationalizations

[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.

Rationalization	Why It's a Trap
[D] "That domain is too different to be relevant."	Distance is the feature — "too different" is where novelty lives.
[D] "We don't have expertise in that foreign domain."	Resource constraint, not conceptual objection — hire, partner, or consult.
[D] "We tried cross-field inspiration before and got nothing actionable."	Inspiration (metaphors) reliably produces nothing. Mechanism import reliably does.
[D] "If this were valuable, someone in our industry would have done it."	Incumbents are structurally least likely to see foreign mechanisms as relevant.
[D] "Our domain is regulated — we can't import from other domains."	Regulatory constraints are a parameter in combination design, not a veto.
→ Add [O] entries here after each real use — paste the actual failure pattern	What went wrong and why

Red Flags

• Output is analogies/metaphors with no description of what would be built differently.
• All brainstorm options are variants of what competitors already do — import has not occurred.
• Foreign domain selected is too close to the home domain to produce novelty.
• Imported mechanism is not deeply understood — used as buzzword, not structural tool.
• Expert resistance treated as evidence of error rather than novelty.

Verification

• Problem restated in abstract structural terms (domain-specific language removed).
• 3 foreign domains identified — at least one genuinely distant from the home domain.
• For each foreign domain, a specific mechanism named (not analogy).
• Proposed combination describes what would be built or done differently (mechanism, not metaphor).
• Stop-rule explicitly applied. Smallest-viable test designed.
• Source domain, mechanism, and adaptation documented in Cross-Domain Synthesis Map.

---

Part of deciqAI Knowledge Skills — open-source thinking skills that make rigor executable for AI agents. Built by deciqAI · https://deciqai.com · Contributions welcome — see the template at the repo root.