Analogy Engine
Transfer patterns across domains by mapping structure, not surface similarity: identify roles, flows, feedback loops, and bottlenecks in a source world, then find the same skeleton in the target problem.
When to Use
- Domain experts have exhausted conventional playbooks and options feel interchangeable.
- You want inspiration from biology, logistics, hospitality, games, or other far fields.
- A tempting metaphor appears—use this skill to verify it before betting on it.
Workflow
- State the problem in abstract terms (inputs, actors, state, goals, failure modes).
- Pick a distant domain (biomimicry, another industry, or “What would X do?”—e.g., a restaurant handling a software reliability issue).
- Map structural correspondences: what plays which role? Where is the queue, the filter, the catalyst?
- Translate one or two mappings into concrete tactics; list where the analogy breaks and adjust.
- Prefer analogies backed by shared dynamics, not shared vocabulary.
Examples
Example 1: Latency spikes: kingfisher beak → smooth boundary transitions; test whether “gradual impedance change” applies to API batching vs sharp bursts.
Example 2: Onboarding drop-off: compare to restaurant seating—reservation, waitlist, and “first drink” map to pre-auth, staggered rollout, and instant value.
1---2name: analogy-engine3description: Analogy Engine4---5# Analogy Engine67Transfer patterns across domains by mapping **structure**, not surface similarity: identify roles, flows, feedback loops, and bottlenecks in a source world, then find the same skeleton in the target problem.89## When to Use10- Domain experts have exhausted conventional playbooks and options feel interchangeable.11- You want inspiration from biology, logistics, hospitality, games, or other far fields.12- A tempting metaphor appears—use this skill to **verify** it before betting on it.1314## Workflow151. State the problem in abstract terms (inputs, actors, state, goals, failure modes).162. Pick a distant domain (biomimicry, another industry, or “What would X do?”—e.g., a restaurant handling a software reliability issue).173. Map **structural** correspondences: what plays which role? Where is the queue, the filter, the catalyst?184. Translate one or two mappings into concrete tactics; list where the analogy **breaks** and adjust.195. Prefer analogies backed by shared dynamics, not shared vocabulary.2021## Examples22**Example 1:** Latency spikes: kingfisher beak → smooth boundary transitions; test whether “gradual impedance change” applies to API batching vs sharp bursts.2324**Example 2:** Onboarding drop-off: compare to restaurant seating—reservation, waitlist, and “first drink” map to pre-auth, staggered rollout, and instant value.
sethdford