Skip to content

Stock-and-Flow Diagram

Structural model — instantiates Conserved Reservoir-Flux Balancing

Draws the conserved quantity as stocks (accumulations) connected by flows (rates), exposing the reservoir-and-pipe structure — and the feedback loops — behind a flow problem.

The Stock-and-Flow Diagram is the structural notation of system dynamics: rectangles are stocks (accumulations that persist and can only be changed by flows), valve symbols are flows (the rates that fill and drain them), clouds are the sources and sinks outside the boundary, and thin arrows are the information links that let a flow depend on a stock — the feedback. What makes it this mechanism is that it captures structure, not magnitude and not behaviour: it says what accumulates, what rate moves it, and what depends on what, but assigns no widths (that's the Sankey Flow Map) and runs no clock (that's the System Dynamics Simulation). Its defining discipline is forcing the stock-versus-flow distinction that ordinary flow-talk blurs — separating the thing that accumulates from the rate that changes it — which is exactly where feedback loops become visible.

Example

A fisheries team draws the structure of a fish population before touching any data. The biomass is a single stock — a rectangle. One inflow valve, recruitment and growth, whose rate depends on the current biomass (an information arrow loops from stock back to inflow). Two outflow valves, catch (its rate set by fishing effort) and natural mortality. Clouds sit at each end for the sea beyond the modelled population.

Merely drawing it exposes the trap. Catch is driven by effort, but recruitment is driven by the stock — so if catch outruns recruitment the biomass falls, which lowers recruitment, which lets the same catch drain it faster still: a reinforcing collapse loop, plain on the page before a single number is entered. A flow-only view — "we take X tonnes a year, the sea replaces X tonnes a year" — hides this entirely, because it never separates the stock from the rate that feeds on it. The diagram's whole value here is structural insight bought cheaply, ahead of any modelling.

How it works

  • Name the conserved quantity and its stocks. Draw each accumulation as a rectangle; these are the reservoirs that hold the quantity.
  • Add the flows as valves. Each inflow and outflow is a rate that moves the quantity across the boundary; sources and sinks beyond the boundary are clouds.
  • Draw the information links. Arrows show which stocks feed back to set which flow rates — this is where reinforcing and balancing loops appear.
  • Structure first, numbers later. The distinctive move is insisting on the stock/flow separation and the feedback wiring before any quantification.

Tuning parameters

  • Stock granularity — one aggregate reservoir or several sub-stocks; splitting reveals internal dynamics but multiplies the structure to maintain.
  • Boundary placement — what becomes a cloud versus a modelled stock; where you cut sets what the diagram can ever explain.
  • Feedback detail — how many information links to draw; too few miss the loops, too many make the page unreadable.
  • Level of abstraction — a conceptual sketch for shared understanding, or a simulation-ready structure with every rate specified.
  • Naming discipline — stocks as quantities (nouns), flows as rates (verbs); sloppy naming is how a stock gets mistaken for a flow.

When it helps, and when it misleads

Its strength is revealing feedback loops and the stock/flow distinction that flow-only reasoning misses, and doing it as a shared picture a team can argue over before committing to a model.

Its limit is that structure is not behaviour: the diagram shows what dynamics are possible, not what will happen — that needs the simulation — and drawn with the wrong boundaries or a mislabelled stock it can mislead confidently. The classic misuse is treating the drawing itself as proof that a dynamic exists, without ever running it. There is a documented cognitive trap underneath this: even highly educated people systematically misread how a flow accumulates into a stock.[1] The discipline is to use the diagram to fix the structure, then simulate before believing any behaviour it seems to imply.

How it implements the components

The Stock-and-Flow Diagram realises the archetype's structural-naming layer — the components a modelling notation defines:

  • conserved_quantity_definition — the diagram names the conserved thing the stocks hold and the flows move.
  • reservoir_inventory — the rectangles are the inventory of stocks: every reservoir in the system, drawn.
  • flux_channel_definition — the valves define the flows as rate-controlled structural channels (the Sankey Flow Map defines the same channels by magnitude instead of by structure).

It does NOT quantify or size the flows — that's the Mass-Balance Table and Sankey Flow Map — nor run the structure over time — that's the System Dynamics Simulation — nor define a specific resource's boundary and sources (Water or Resource Budget).

Notes

Three of this archetype's mechanisms are easily confused; the split is worth holding. The Stock-and-Flow Diagram gives structure and feedback (no numbers); the Sankey Flow Map gives magnitude (no feedback); the System Dynamics Simulation gives behaviour over time by running the diagram's structure. In practice the diagram is drawn first, then either measured into a Sankey or animated into a simulation.

References

[1] Stock-flow failure — the robust finding (Sterman; Booth Sweeney) that even numerate, well-educated people misjudge how a flow accumulates into a stock, as in the classic "bathtub" and "department-store" tasks. It is the everyday reason the stock/flow distinction has to be drawn explicitly rather than assumed. ↩