Protocol
Use a behavior-over-time view before root-cause stories
Patterns over time constrain causal stories.
When it fits
- When a current snapshot is driving a confident explanation of a dynamic problem.
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
Plot or reconstruct the variable over a meaningful horizon, mark interventions and regime changes, then ask which candidate mechanisms could produce that shape.
Steps
- Choose the key outcome variable.
- Plot its history at a useful cadence.
- Mark major interventions or boundary changes.
- Reject explanations inconsistent with the observed timing.
An example
A backlog spike began before the new release, weakening the claim that the release alone caused it.
Check your result
The preferred explanation fits the timing and shape better than alternatives, not just the latest observation.
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 withTurn the causal map into a testable model question
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