Checklist
Look for policy resistance before scaling
Scale changes the environment that produced the pilot result.
When it fits
- When a pilot works locally and the team wants to scale it without testing system response.
When to avoid it
- A causal map is a hypothesis, not proof. Keep evidence, time scale, boundary choices and alternative explanations visible before acting on a loop.
Checklist
- Which resource becomes scarce at scale?
- Which actor changes behavior?
- Which delay becomes material?
- Which feedback loop was absent in the pilot?
Why it matters
Before expansion, check whether constrained resources, incentives, queues, learning, market response or governance will react differently at scale.
An example
A small manual review pilot succeeds with expert attention; scaling creates a review queue that erases the benefit.
Check your result
The scale decision includes at least one system-response risk and a corresponding test or monitor.
Keep this limit in mind
- A causal map is a hypothesis, not proof. Keep evidence, time scale, boundary choices and alternative explanations visible before acting on a loop.
Connected ideas
Use beforeUse a behavior-over-time view before root-cause stories
Evidence and sources
Supports
System dynamics work emphasizes that well-intended interventions can be defeated by feedback-driven system responses, a pattern described as policy resistance.
A qualitative feedback story is not enough; links, delays and predicted behavior still need empirical or operational checking.
System Dynamics Modeling: Tools for Learning in a Complex World · Abstract