Protocol
Map the reinforcing loop behind growth
Reinforcing feedback can make change compound.
Before you use it
- Use when
- When a trend accelerates and the team treats each period as independent.
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
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.
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 readingMap the reinforcing loop behind growth
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaSeparate stock from flow
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.