80 lines
2.7 KiB
Markdown
80 lines
2.7 KiB
Markdown
# Collision-Zone Thinking
|
|
|
|
Force unrelated concepts together to discover emergent properties. "What if we treated X like Y?"
|
|
|
|
## Core Principle
|
|
|
|
Revolutionary insights from deliberate metaphor-mixing. Treat X like Y and see what emerges.
|
|
|
|
## When to Use
|
|
|
|
| Symptom | Action |
|
|
|---------|--------|
|
|
| Stuck in conventional thinking | Force wild domain collision |
|
|
| Solutions feel incremental | Need breakthrough, not optimization |
|
|
| "Tried everything in this domain" | Import concepts from elsewhere |
|
|
| Need innovation, not iteration | Deliberately mix unrelated ideas |
|
|
|
|
## Quick Reference Collisions
|
|
|
|
| Treat This | Like This | Discovers |
|
|
|------------|-----------|-----------|
|
|
| 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 |
|
|
|
|
## Process
|
|
|
|
1. **Pick two unrelated concepts** from different domains
|
|
2. **Force combination** - "What if we treated [A] like [B]?"
|
|
3. **Explore emergent properties** - What new capabilities appear?
|
|
4. **Test boundaries** - Where does the metaphor break?
|
|
5. **Extract insight** - What did we learn?
|
|
|
|
## Detailed Example
|
|
|
|
**Problem:** Complex distributed system with cascading failures
|
|
|
|
**Collision:** "What if we treated services like electrical circuits?"
|
|
|
|
**Emergent properties:**
|
|
- Circuit breakers (disconnect on overload)
|
|
- Fuses (one-time failure protection)
|
|
- Ground faults (error isolation)
|
|
- Load balancing (current distribution)
|
|
- Voltage regulation (rate limiting)
|
|
|
|
**Where it works:** Preventing cascade failures, fault isolation
|
|
|
|
**Where it breaks:** Circuits don't have retry logic, healing mechanisms
|
|
|
|
**Insight gained:** Failure isolation patterns from electrical engineering
|
|
|
|
## Best Source Domains
|
|
|
|
Rich domains for concept mining:
|
|
- **Physics** - Forces, thermodynamics, relativity
|
|
- **Biology** - Evolution, ecosystems, immune systems
|
|
- **Economics** - Markets, incentives, game theory
|
|
- **Psychology** - Cognition, behavior, motivation
|
|
- **Architecture** - Structure, flow, space utilization
|
|
|
|
## Red Flags
|
|
|
|
You need collision-zone thinking when:
|
|
- "I've tried everything in this domain"
|
|
- Solutions feel incremental, not breakthrough
|
|
- Stuck in conventional thinking
|
|
- Need innovation, not optimization
|
|
- "Standard approach isn't working"
|
|
|
|
## Remember
|
|
|
|
- Wild combinations often yield best insights
|
|
- Test metaphor boundaries rigorously
|
|
- Document even failed collisions (they teach)
|
|
- Breakthrough > incremental improvement
|
|
- Question: "What would [domain expert] do?"
|