Protocol
Map the balancing loop behind a limit
Limits often emerge from balancing feedback.
When it fits
- When progress improves at first and then stalls despite continued effort.
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 how growth increases a constraint, corrective response or depletion that pushes the system back toward a target or ceiling.
Steps
- Name the target or growing variable.
- Find the constraint that rises with growth.
- Trace the corrective response.
- Mark delays that can cause overshoot.
An example
Adding parallel projects initially raises output, then coordination load grows and slows completion, balancing the gain.
Check your result
The suspected limit is represented as a closed counteracting loop rather than a vague 'capacity issue.'
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 withPut delays on the map
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