Collision-Zone Thinking
Revolutionary insights from forcing unrelated concepts to collide.
[GOAL]
Generate breakthrough solutions by treating X like Y and seeing what emerges.
[CONTEXT]
Core principle: Deliberate metaphor-mixing generates novel solutions.
Use when:
- •"I've tried everything in this domain"
- •Solutions feel incremental, not breakthrough
- •Need innovation, not optimization
[PROCESS]
- •Pick two unrelated concepts from different domains
- •Force combination: "What if we treated [A] like [B]?"
- •Explore emergent properties: What new capabilities appear?
- •Test boundaries: Where does the metaphor break?
- •Extract insight: What did we learn?
[EXAMPLES]
| Stuck On | Try Treating As | Might Discover |
|---|---|---|
| Code organization | DNA/genetics | Mutation testing, evolutionary algorithms |
| Service architecture | Lego bricks | Composable microservices, plug-and-play |
| Data management | Water flow | Streaming, data lakes, flow-based systems |
| Request handling | Postal mail | Message queues, async processing |
| Error handling | Circuit breakers | Fault isolation, graceful degradation |
Best source domains: physics, biology, economics, psychology
[IMPORTANT]
- •Wild combinations often yield best insights
- •Test metaphor boundaries rigorously
- •Document even failed collisions (they teach)
- •Best insights come from outside your domain
See Also
- •[[when-stuck]] - Dispatch to right technique
- •[[inversion-exercise]] - Flip assumptions