Protocol
Trace side effects through another loop
Side effects often travel through a different feedback path.
Before you use it
- Use when
- When a fix works on its primary metric but overall outcomes worsen.
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.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
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.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingTrace side effects through another loop
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaAsk how the system will respond to the intervention
Evidence and sources
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
Edition and review
Version 0.1.0
No review details are supplied for this edition.