Core Idea
Definition
System Dynamics is a framework for understanding how accumulations, rates of change, feedback loops, and delays combine to produce system behavior over time.
In Plain English
A system is not just what it contains. It is how things build up, drain away, react to each other, and change over time.
How It Works
Static snapshots hide the mechanics of change. System dynamics makes those mechanics visible by asking what is accumulating, what is flowing in or out, what feedback loops are reinforcing or balancing movement, and where delays distort perception. This matters because many problems come from managing levels while ignoring rates, or treating recurring outcomes as isolated events rather than structural behavior. Once the moving parts are clear, you can predict overshoot, bottlenecks, drift, oscillation, and collapse more effectively than by using one-step cause-and-effect stories.
When to Use
- •When the same outcome keeps recurring despite repeated fixes
- •When behavior changes over time in ways that feel nonlinear or unstable
- •When managing growth, capacity, inventory, trust, or other accumulations
- •When trying to model a system rather than a one-off event
- •When policies create surprising long-run outcomes
Examples
Everyday
Your email inbox is a stock. Incoming mail and processed mail are flows. If inflow consistently exceeds outflow, the backlog grows even if you feel busy all day.
Professional
Customer trust accumulates slowly and can drain quickly. Support quality, product reliability, and response time influence that stock over time through reinforcing and balancing loops.
Extreme Case
A city infrastructure system can oscillate between congestion relief and renewed congestion when capacity expansions change behavior and demand with long delays.
Common Mistakes
- •Treating stocks like flows or flows like stocks
- •Ignoring time delays that destabilize the system
- •Trying to fix visible symptoms without changing the structure
- •Using systems language loosely without specifying what is actually accumulating or feeding back
Limits & Failure Modes
- •The framework can become too abstract if not tied to real variables
- •Building a useful system model takes time and judgment
- •Important variables may be hard to measure directly
- •A clean diagram can still miss political, emotional, or cultural realities
How to Practice
stocks and flows
For a problem you care about, identify what is accumulating and what increases or decreases that accumulation.
behavior over time
Sketch how the system's key variables changed over weeks, months, or years instead of discussing only the current snapshot.
structure before blame
When a recurring issue appears, ask what system design keeps reproducing it before assigning fault to individuals.
Related Cognitive Biases
linearity bias
People expect straight-line relationships in systems governed by accumulation, delay, and feedback.
event orientation bias
People focus on visible incidents instead of the underlying structure generating repeated behavior.
recency bias
People overread the latest signal and underread the longer pattern of system motion.
Related Mental Models
Related Skills
Advanced Notes
Historical Origin
System dynamics was formalized by Jay Forrester and later expanded through management science, ecology, and policy analysis.
Philosophical Context
It reflects a structural, time-sensitive conception of causality that resists reduction to isolated events or linear chains.
Further Reading
- Business Dynamics by John D. Sterman
- Thinking in Systems by Donella H. Meadows
- Industrial Dynamics by Jay W. Forrester