Principle
Separate stock from flow
Stocks remember history; flows change stocks.
Before you use it
- Use when
- When a system has accumulation, backlog, inventory, skill, debt or another quantity that changes over time.
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
Identify what accumulates and which inflows or outflows alter it. This prevents treating a large backlog as if it were only today's arrival rate.
An example
Unresolved defects are a stock; new defects and reopens are inflows, verified fixes are an outflow.
Check your result
The map distinguishes accumulated quantity from rates that change it.
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 readingSeparate stock from flow
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaDefine the system boundary before optimizing
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.