Protocol
Map the reinforcing loop behind growth
Reinforcing feedback can make change compound.
When it fits
- When a trend accelerates and the team treats each period as independent.
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
Trace a loop in which an increase eventually causes more increase in the same direction, then identify the delay and the condition that could weaken or reverse it.
Steps
- Choose the growing variable.
- Trace how it changes another variable.
- Close the loop back to the original variable.
- Mark delay and limiting conditions.
An example
More public evidence creates more inbound opportunities, which create more strong cases that can become public evidence—until delivery capacity constrains the loop.
Check your result
The loop closes causally and includes at least one plausible limit or counter-loop.
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 beforeMap the balancing loop behind a limit
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