---
name: Systems Dynamics (Structural)
status: draft
territory: process-and-system-analysis
msi_territory: process-and-systems
sources:
  - title: Forrester, Jay W. (1961), Industrial Dynamics, MIT Press
    url: https://openlibrary.org/works/OL4504423W
  - title: "Meadows, Donella H. (2008), Thinking in Systems: A Primer, Chelsea Green Publishing"
    url: https://openlibrary.org/works/OL3737036W
  - title: "Sterman, John D. (2000), Business Dynamics: Systems Thinking and Modeling for a Complex World, Irwin/McGraw-Hill"
    url: https://openlibrary.org/works/OL7914257W
  - title: "Senge, Peter M. (1990), The Fifth Discipline: The Art and Practice of the Learning Organization, Doubleday/Currency"
    url: https://openlibrary.org/works/OL4440692W
---

# Systems Dynamics (Structural)

## Why it matters

Before you can fix a system that surprises you, you have to be able to draw it — not as a list of parts, but as a working machine: what accumulates, what fills and drains those accumulations, and how the whole thing wires back on itself. Most explanations of a complicated system are really just stories about events ("subscribers fell last quarter because of the price change"). Systems Dynamics (Structural) does something different and more durable: it maps the *structure* that generates the behavior — the stocks that hold the system's state, the flows that change them, and the feedback loops that connect them — so you can see why the system behaves as it does and where the real leverage sits, before you touch a single lever.

For example: a newsroom watches its subscriber count and panics every time the number dips. But the count is a *stock* — a reservoir — and what actually moves it are two *flows*: people signing up and people churning out. Draw it that way and a confusing picture turns simple. The reservoir can keep rising for months even as sign-ups slow, as long as sign-ups still outrun churn; and it can be quietly hollowing out — sign-ups and churn both high — while the headline number looks flat. The dip everyone fears might just be a normal wobble in a healthy tub, or the first visible sign that the drain has been wide open all along. You cannot tell from the level. You can only tell from the structure.

- **What it reveals.** The system's working anatomy — its **stocks** (what accumulates), its **flows** (the rates that fill and drain them), and the **feedback loops** wiring them together — so that the behavior you see over time is explained by a structure you can point to, not by a string of one-off events.
- **How it changes the read.** You stop asking *"what is the number doing?"* and start asking *"what structure of stocks, flows, and loops would produce this behavior — and which part of it could I actually move?"* A level tells you where you are; the structure tells you where you are headed and why.
- **When to foreground it.** You want a clear, current-state picture of how a system with feedback actually works — a map to orient by or to argue from — *before* committing to a change, especially when the system has reservoirs that fill and drain and the visible numbers keep misleading you.
- **What you'd miss without it.** That a stock and its flows are not the same thing, and confusing them is how careful people reach exactly wrong conclusions — cutting an inflow and expecting the reservoir to fall immediately, when a still-open drain or a long delay means it keeps right on rising.
- **Where it misleads.** Pushed too far it tips into "everything connects to everything," an unfalsifiable web with no boundary and no leverage; and a clean structural map is a *description*, not a simulation — it shows you the machine's wiring, not the exact numbers it will print next quarter.

## Realtime examples

See real, dated analyses where this mode maps the structure — stocks, flows, and feedback — behind a system in the news → **[Systems Dynamics (Structural) on Main Street Independent](https://mainstreetindependent.com/analyses/technique/process-and-systems/systems-dynamics-structural)**

## How to invoke it in Ora

You want a structural picture of a system with feedback dynamics — its stocks, flows, and loops drawn as a working whole — before you decide what to change.

Name the reservoirs and the rates, and ask:

> "Draw the feedback structure for our [system]. Show me the stocks (the things that accumulate), the flows (the rates that fill and drain them), and a structural diagram with the feedback dynamics. I want a structural picture before deciding what to change."

The phrases *draw the feedback structure*, *show me the stocks and flows*, and *structural picture before deciding what to change* are what route you here. Bring candidate stocks if you can — "subscribers, churned-but-recoverable, content backlog" gives the mode far more to build on than "our subscription business" — because naming the reservoirs up front is what keeps the stock-versus-flow distinction crisp instead of blurry.

Two boundaries worth knowing. This mode *maps* the system as it currently is; it deliberately does not recommend interventions, so if what you actually want is "why does our fix keep failing, and what should we change," that is a diagnosis, and the causal sibling fits better. And if the system has no real feedback — a straight-through workflow of steps with no loops — then a structural feedback map is the wrong instrument; a process map is. This mode draws the machine at rest so you can see it whole; it does not pick the lever to pull.

## How it works

The whole method rests on one distinction, and the clearest place to see it is a bathtub. The water already *in* the tub is a **stock** — an accumulation, a quantity that just sits there and persists. The faucet and the drain are **flows** — rates, measured in gallons per minute, that change how much is in the tub. That is the entire vocabulary. A stock is a noun you could photograph at an instant; a flow is a verb you can only measure over a stretch of time. Money in a bank account is a stock; deposits and withdrawals are flows. People in a city is a stock; births, deaths, people moving in and people moving out are flows. Once you start seeing the world this way, you cannot unsee it: every system that behaves over time is some set of reservoirs being filled and drained.

Here is why the distinction is not pedantic but load-bearing. The level of a stock depends only on the *difference* between its inflow and its outflow — and that single fact defeats most people's intuition. Picture the tub half-full, faucet wide open, drain wide open, water pouring in faster than it leaves. Now you start closing the faucet. The inflow is *falling* the whole time — and yet, as long as it still exceeds the drain, **the water keeps rising**. The level goes up while the inflow goes down. People get this wrong constantly, and not because they are careless. In a now-famous study at MIT, highly educated graduate students were shown a graph of a stock filling and draining and asked simple questions about it; most got them wrong, reasoning as if the stock should track its inflow. It does not. A stock integrates its flows over time, and our heads are bad at integration.

That same confusion runs underneath one of the most consequential public arguments of our era. Carbon dioxide *emissions* are a flow — the rate we pour CO2 into the air each year. The CO2 *concentration* in the atmosphere is the stock — the accumulated total up there now. Because the drain (the rate the oceans and biosphere pull carbon back down) is far smaller than the inflow, merely *slowing the growth* of emissions — turning the faucet down a little — still leaves inflow above outflow, so the concentration keeps climbing. To actually stabilize the stock you have to bring the inflow down to meet the drain. People reason about it as if leveling off emissions would level off concentration; the bathtub says otherwise, and the bathtub is right. Getting the stock-and-flow structure straight is the difference between a policy that works and one that feels like it should.

Now wire the flows back to the stock and you have **feedback** — the last piece, and the one that makes a system more than a tub. Imagine the drain widens as the tub gets fuller (more water, more pressure, faster drain): that is a *balancing* loop, a connection that pushes back toward steadiness, the reason so many systems hold a level. Imagine instead that a fuller tub somehow opened the faucet wider: that is a *reinforcing* loop, the engine of runaway growth or collapse — a bank account where the interest is itself deposited grows faster the bigger it gets. Real systems are stocks and flows laced together by loops like these, and the behavior you observe — steady, growing, oscillating, collapsing — falls out of that wiring. Map the stocks, the flows, and the loops honestly, with an explicit boundary around what you are and are not including, and you have a picture you can reason from: you can see why the level moves as it does, and you can see which connection, if it changed, would change everything downstream.

That last point is where structural mapping earns its keep. Donella Meadows, who spent a career on these systems, observed that the places to intervene are almost never the obvious knobs. People reach for the *numbers* — the size of a tax, the level of a target — which is where the least leverage lives. The real power sits deeper in the structure: in the strength of a feedback loop, in the delays inside it, in the rules and goals that set the whole thing up. You cannot find those high-leverage places by staring at the level in the tub. You find them by having drawn the machine.

## Framework & implementation

*This section uses Ora's own terms for the parts of an analysis, so that if you open the actual mode file they line up. Each is glossed in plain language on first use.*

### Pipeline execution

Systems Dynamics (Structural) is an **atomic mode** in the **process-and-system-analysis** territory — a single mapping pass, not a composite of sub-analyses. It runs at **Gear 4**, Ora's most thorough setting: a **Depth analyst** and a **Breadth analyst** build the structural map in parallel and then critique each other (**cross-adversarial evaluation**) before a consolidator integrates the result — depth pressure-testing each loop's closure and polarity, breadth surveying the archetype catalog and guarding the system boundary against silently swallowing every adjacent variable.

The pass does five things in order. It **states the system boundary** — what is inside the map and what is deliberately left outside as exogenous, each exclusion given a reason, because an honest map is defined as much by what it leaves out as by what it includes. It **inventories the variables**, tagging each with its **role** — **stock** (it accumulates), **flow** (it changes a stock's level per unit time), **auxiliary** (a helper quantity), or **exogenous** (driven from outside the boundary) — and its unit of change, so the stock-versus-flow distinction never blurs. It **walks each feedback loop** from a starting variable around to its closing edge, recording the members in order, the polarity of every edge, and an explicit **polarity-parity check** (an even number of negative edges makes a loop **reinforcing**; an odd number makes it **balancing**) that must match the loop's declared type. It **surfaces delays** — where a lag sits on which edge, its magnitude, and what that lag implies for the system's behavior. And it **surveys the system archetypes**, naming one only when the matching loop topology actually appears in the declared loops.

The mode's reasoning tools ride in its **`ANALYTICAL PERSPECTIVES`** block — the lenses it loads as it works. Two are required: the **feedback-loops** lens (find the reinforcing-versus-balancing structure and trace polarity around each loop until it closes) and the **Senge system-archetypes** lens (match the loop topology against the recurring named patterns). Three are optional and pulled in when the material calls for them: **Sterman's system-dynamics modeling** (for quantitative stock-and-flow), **Forrester's industrial dynamics** (the founding source-tradition lens), and **Meadows' twelve leverage points** (loaded only if the map is being used to open an intervention discussion). A **bias-catalog** lens sits underneath as a foundational check on the analyst's own reading.

### Output contract

The deliverable is a fixed set of sections, so the map is auditable rather than a narrative: **System Boundary** (what is inside, and what is deliberately excluded as exogenous, each exclusion with a rationale), **Variables and Stocks** (each variable named with its role — **stock**, **flow**, **auxiliary**, or **exogenous** — its unit, and a plain-language label), **Feedback Loops with Polarity** (each loop typed reinforcing or balancing, its members listed in order with edge polarities, and a parity check confirming the polarities match the declared type), **Delays** (where a lag sits on which edge or loop, its magnitude, and its structural implication), **System Archetypes Present** (which archetypes the declared loop topology actually matches — or an explicit statement that none do), **Structural Observations** (descriptive features of the system as-it-is: which loops dominate at which timescales, where stocks accumulate, where flows are throttled, where the system is in tension with itself — each grounded in a specific loop or flow), and **Confidence and Boundary Caveats** (how strong each claim is and where an excluded variable could change the picture). The contract is **descriptive by design**: a leverage-point recommendation or an "the system should…" sentence is treated as **prescriptive drift**, reshaped out of the map and handed sideways to the causal sibling, where intervention design lives.

### Origin and evidence

The apparatus comes from the systems-dynamics tradition founded at MIT. Jay Forrester established the field — and the stock-and-flow structure at the heart of this mode — in *Industrial Dynamics* (1961), showing that the behavior of a system over time follows from its internal structure of accumulations and rates wired by feedback, not from external events. Donella Meadows distilled the discipline for working analysts in *Thinking in Systems: A Primer* (2008), the clearest modern statement of stocks, flows, and loops; her widely circulated 1999 essay "Leverage Points: Places to Intervene in a System" (Sustainability Institute) supplied the twelve-point ranking of *where* in a structure a change carries the most force, deepest-first — used by this mode only when a map opens onto intervention. John Sterman's *Business Dynamics* (2000) is the field's rigorous modern treatment and the quantitative companion that sits downstream of this mode's qualitative map; it also reports the experiments showing how reliably people misread stock-and-flow accumulation. Peter Senge carried the structure into organizational diagnosis in *The Fifth Discipline* (1990), popularizing the **system archetypes** — recurring loop structures — that this mode matches against, but only when the topology genuinely fits.

### Applications and common uses

- **Business and subscription dynamics.** A subscriber base mapped as a stock with acquisition and churn flows, plus the content-production and amortization flows that feed it — the structure behind a number that keeps misleading.
- **Urban and housing systems.** Housing units, vacancies, and households mapped as stocks, with construction, demolition, and migration flows and the loops linking price, supply, and demand.
- **Operations and workload.** Accounts at risk, healthy accounts, open tickets, and team bandwidth as stocks, with escalation, resolution, and new-workload flows — a current-state picture of where load accumulates.
- **Public systems and social services.** Caseloads such as children in care, families available, and children awaiting placement mapped as stocks, with intake, placement, reunification, and attrition flows.
- **Ecology and resources.** A renewable stock with its regeneration inflow and harvest outflow, and the balancing and reinforcing loops that govern whether it holds, grows, or is drawn down.

### Failure modes and when not to use it

- **Stock/flow conflation.** Treating an accumulation as if it were a rate (or vice versa) collapses the whole structural distinction and produces exactly the wrong intuitions. The mode tags every variable's role and unit precisely, and reshapes a map that blurs the two.
- **Everything-connects holism.** Drawing a web in which every variable touches every other, with no boundary and no specific mechanism per link, yields an unfalsifiable picture with no leverage. The mode forces an explicit boundary with named, reasoned exclusions and a stated mechanism on each edge.
- **Archetype name-dropping.** Invoking a famous pattern ("this is Limits to Growth") in prose without the matching loop topology actually present is a real temptation. The mode names an archetype only when its characteristic loops appear in the declared structure, and says so plainly when none do.
- **Prescriptive drift.** Because a good map makes a leverage point look obvious, the analysis can slide into recommending one — which is a different mode's job. The mode holds a strictly descriptive posture and routes intervention design to the causal sibling.

**When not to reach for it.** When the real question is **why a recurring behavior persists and what to change about it** — the causal-loop story behind a behavior, and the leverage to break it — route to **systems-dynamics-causal**, the diagnostic sibling that uses the same lenses in a prescriptive posture. When the failure is a **one-way chain** with a single condition to remove rather than a structure of loops — "it broke because the filter was missing" — route to **root-cause-analysis**. And when the thing you actually want is a **process's step-by-step flow** — a straight-through workflow with no significant feedback — route to **process-mapping**; a stock-and-flow feedback map is the wrong instrument for a system that has no loops.

## Related

- **Systems Dynamics (Causal)** — the diagnostic sibling that uses the same stock-flow-and-loop apparatus to ask *why* a recurring behavior persists and *what* to change — where this descriptive map hands off when the question turns to intervention.
- **Process Mapping** — the mode for a straight-through workflow with no significant feedback: when the system is a sequence of steps rather than reservoirs and loops, map the flow, not the stocks.
- **Causal DAG** — the formal-graph sibling for *acyclic* causal structure: when the job is to expose confounders and mediators in a directed graph that, by definition, contains no feedback loops.
- **Feedback Loops** and **System Archetypes** — the two required lenses this mode loads: find the reinforcing-versus-balancing structure and trace polarity around each loop, then match the topology against the recurring named patterns — but only when the structure genuinely fits.

## Sources

- [Forrester, Jay W. (1961), Industrial Dynamics, MIT Press](https://openlibrary.org/works/OL4504423W)
- [Meadows, Donella H. (2008), Thinking in Systems: A Primer, Chelsea Green Publishing](https://openlibrary.org/works/OL3737036W)
- [Sterman, John D. (2000), Business Dynamics: Systems Thinking and Modeling for a Complex World, Irwin/McGraw-Hill](https://openlibrary.org/works/OL7914257W)
- [Senge, Peter M. (1990), The Fifth Discipline: The Art and Practice of the Learning Organization, Doubleday/Currency](https://openlibrary.org/works/OL4440692W)