Replication, Not Scaling
Spreading through relationship, not franchise. Patterns that propagate because people adopt and adapt them, not because a central authority deploys them.
The Distinction
Scaling means making one thing bigger: more users, more locations, more capacity. The thing itself stays the same. McDonald’s scales.
Replication means many people making their own version of a pattern. Each instance adapts to local conditions. The pattern is recognizable but the implementation varies. Sourdough replicates.
Scaling requires control. Replication requires trust — trust that people will adapt the pattern well, that local variations are features not bugs, that the pattern is robust enough to survive translation.
Why It Matters
Replication means not one instance getting bigger, but many people building their own versions — different hardware, different crops, different communities, same underlying patterns.
This requires appropriate-technology: tools and methods that can be understood and adapted locally. And it requires documentation that teaches principles, not procedures.
Connections
- mutual-aid — cooperation spreads through relationship
- appropriate-technology — tools that can be adapted locally
- Elinor Ostrom — each commons adapts to local conditions
- Robin Sloan — home-cooked software as replication
- Christopher Alexander — patterns as replicable starting points
- seeds-not-solutions — seeds replicate; solutions scale
A recipe replicates. A factory scales. The recipe survives the factory’s bankruptcy.