Protocol
Trace side effects through another loop
Side effects often travel through a different feedback path.
When it fits
- When a fix works on its primary metric but overall outcomes worsen.
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.
Why it matters
Start from the intervention, trace the intended path, then deliberately search for a second path that changes capacity, incentives, information or delay. Compare time scales.
Steps
- Draw the intended causal path.
- Search for a second path through another subsystem.
- Mark whether the side effect is faster or slower.
- Choose a monitoring signal for both.
An example
Automation cuts manual effort immediately but gradually reduces operator familiarity, increasing recovery time during rare exceptions.
Check your result
The model names a plausible second path and a signal that could falsify it.
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
Useful withLook for policy resistance before scaling
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