System Dynamics
What it is
System Dynamics is a way of studying how systems behave over time.
It focuses on feedback loops, delays, accumulations, flows, causal relationships, and the way connected parts create patterns that are not always obvious from looking at the parts separately.
System Dynamics is closely associated with Jay Forrester and work that emerged from MIT in the mid-20th century. It became influential in business, public policy, operations, environmental modeling, and complex-systems analysis because it offered a way to model how systems change, reinforce themselves, resist change, or produce unintended consequences over time.
Where Systems Thinking helps people see relationships, System Dynamics gives more formal attention to how those relationships produce movement, delay, buildup, depletion, escalation, correction, collapse, or stability.
In plain language: System Dynamics studies how connected parts, feedback, and delays cause a system’s behavior to change over time.
Why it matters to MNKY Math
System Dynamics matters to MNKY Math because many outcomes are not produced instantly.
They build.
They drift.
They compound.
They delay.
They reinforce.
They correct too late.
They appear suddenly after being shaped slowly.
A metric may change behavior over months.
A policy may create second-order effects after the first-order goal appears successful.
A workplace may become exhausted gradually, then seem to “suddenly” fail.
A platform may learn from engagement signals until the system becomes increasingly shaped around attention capture.
A customer habit may be nudged, reinforced, personalized, and normalized over time.
System Dynamics helps MNKY Math think beyond the moment of action and into the behavior pattern that emerges across repeated interactions.
It also helps explain why systems often surprise the people inside them. The effect may be delayed. The feedback may be distorted. The accumulation may be invisible. The correction may arrive after the condition has already hardened.
System Dynamics matters because it helps MNKY Math see how repeated behavior, feedback, delay, and accumulation turn isolated actions into system outcomes.
Where we overlap
System Dynamics and MNKY Math overlap around feedback loops, delays, system behavior, causality, outcomes, and unintended consequences.
Both are interested in what happens over time.
Both recognize that outcomes can emerge from relationships rather than from one isolated cause.
Both care about feedback: what returns to the system, how the system interprets it, and what future behavior it shapes.
Both are attentive to delay. A system may act now, but the consequence may arrive later, elsewhere, or in a form that is easy to misread.
System Dynamics is especially useful to MNKY Math because it gives language for patterns such as:
reinforcing loops, where behavior feeds more of itself
balancing loops, where the system tries to correct or stabilize
delays, where cause and effect are separated by time
accumulation, where small changes build into larger conditions
unintended consequences, where one intervention creates effects outside the intended frame
shifting burdens, where a short-term fix weakens the system’s ability to solve the deeper problem
policy resistance, where the system pushes back against an attempted change
These patterns sit very close to MNKY Math’s interest in how systems shape behavior and outcomes.
Where MNKY Math differs
System Dynamics often focuses on modeling system behavior over time through feedback structure, stocks, flows, delays, and causal relationships.
MNKY Math agrees with that focus, but extends the lens into measurement, incentives, agency, human interpretation, lived participation, second-order effects, and collateral effects.
The question is not only: What feedback structure produced this behavior over time?
MNKY Math also asks:
What did people inside the system notice as the pattern was forming?
What signals returned too late, too weakly, too loudly, or in distorted form?
What metric became part of the feedback loop?
What behavior did the system reward, punish, normalize, or ignore?
Who had agency to interrupt the loop?
Who absorbed the delay, burden, or downstream effect?
What second-order effects appeared after the initial intervention?
What collateral effects spread into nearby signals, behaviors, relationships, or trust conditions?
How did fear, fatigue, trust, habit, identity, or prior experience shape participation inside the loop?
What outcome became more likely because the loop kept teaching the system the same lesson?
System Dynamics helps show how system behavior changes over time.
MNKY Math asks how people experience, interpret, participate in, and are shaped by those dynamics — including what changes after the first intervention appears to work.
That distinction matters.
A system may respond to a signal by changing the immediate condition. But the second-order effect may reveal that the underlying system has not changed. The alert gets bigger, the worker responds briefly, and then the prior behavior returns because role clarity, false positives, workload, or signal trust remained unresolved.
A collateral effect may appear nearby. The worker does not only learn to discount that alert. They may begin to question other alerts, other signals, or the system’s judgment more broadly.
MNKY Math wants both views.
The model of the system.
And the human experience of living inside it.
How it shows up
System Dynamics shows up wherever behavior changes over time because of feedback, delay, accumulation, or reinforcing conditions.
- A company increases sales pressure to hit quarterly targets. The short-term numbers improve, but customer trust erodes, employee burnout rises, and future revenue quality weakens.
- A workplace understaffs to control labor costs. The savings appear quickly, while fatigue, mistakes, turnover, training burden, and service decline accumulate more slowly.
- A platform recommends more of what keeps users engaged. Engagement data feeds the algorithm, the algorithm feeds more similar content, and the user’s environment becomes increasingly shaped by prior attention.
- A school focuses heavily on test scores. Scores may rise at first, while curiosity, depth, teacher autonomy, and broader learning may narrow over time.
- A healthcare system tries to improve throughput. Shorter visits may increase capacity, but unresolved concerns, repeat visits, staff strain, and patient distrust may increase elsewhere in the system.
- A customer-service system reduces call time targets. Efficiency appears to improve, but unresolved issues generate repeat contacts, hidden frustration, and downstream workload.
- A team uses a short-term workaround to keep work moving. The workaround becomes normal, the root problem remains, and the system gradually forgets that the workaround was supposed to be temporary.
In each case, the system’s behavior cannot be understood only by looking at the first action.
The pattern appears over time.
MNKY Math lens
System Dynamics helps MNKY Math examine how systems behave across time, feedback, delay, and repetition.
MNKY Math extends the lens by asking:
- What behavior is repeating?
- What signal returns to the system?
- How does the system interpret that signal?
- What response does the signal trigger?
- Is the loop reinforcing, balancing, distorting, or delaying action?
- What is accumulating?
- What burden is shifting?
- What consequence arrives late?
- What metric is feeding the loop?
- Who has agency to interrupt, redesign, or redirect the loop?
- What does the loop teach people to repeat?
- What outcome becomes more likely over time?
This is where system modeling becomes behavior modeling.
System Dynamics helps reveal the movement of the system.
MNKY Math asks what that movement makes people notice, choose, avoid, repeat, protect, or accept as normal.
A loop is not only a diagram.
It is a teaching structure.
Over time, feedback loops teach the system what to become.
Relationship map
Closest twin: Systems Thinking Systems Thinking is the broader way of seeing relationships and interdependencies; System Dynamics gives more formal attention to how those relationships produce behavior over time.
Clarifying contrast: Root-Cause Analysis Root-Cause Analysis often looks for deeper causes behind a problem; System Dynamics examines how interacting causes, feedback loops, delays, and accumulations produce patterns over time.
Mostly shaped by: Feedback Loops System Dynamics depends on understanding how information, consequences, correction, reinforcement, and delay return to shape future system behavior.
Helps explain: Second-order Effect System Dynamics helps explain why actions can produce delayed, indirect, or unintended effects after feedback, accumulation, and interaction move through the system — including effects that return to the original behavior and effects that spread into nearby behaviors, signals, or trust conditions.