Protocol
Use a behavior-over-time view before root-cause stories
Patterns over time constrain causal stories.
Before you use it
- Use when
- When a current snapshot is driving a confident explanation of a dynamic problem.
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
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.
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 readingUse a behavior-over-time view before root-cause stories
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Use before this ideaLook for policy resistance before scaling
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.