Stocks & Flows

In Feedback Loops you met the bathtub for a few minutes — just long enough to learn that a stock is a level that piles up and a flow is the rate that fills or drains it, so you could go on to study the loops that wrap around a stock. This course goes back and drains the tub completely. Stocks and flows are the grammar of accumulation — the single most-confused, most-leveraged distinction in all of systems thinking — and they deserve a course of their own.

Here is the whole problem in one sentence: a rate is not a level, and almost everyone treats them as if they were. “The deficit is shrinking” sounds like “the debt is shrinking.” “Emissions have flattened” sounds like “the carbon in the sky has flattened.” “I ate less today” sounds like “I lost weight.” Every one of those is a statement about a flow quietly dressed up as a statement about a stock — and the swap is wrong every single time. A falling inflow that still exceeds the outflow leaves the stock rising. Slowing the fill is not draining the tub.

You will learn to never make that mistake again, and a good deal more. We’ll nail the two-second test that sorts any quantity into stock or flow; the one accumulation rule that governs every system that has ever existed (change in the stock = inflow − outflow, piled up over time); why a stock is the running total — the integral — of its flows, which is why it smooths, lags, and remembers; why that memory gives systems inertia, so they respond slowly and overshoot; and how to wield the stock-flow distinction as a debugging tool that makes you measurably harder to fool about debt, climate, hiring pipelines, warehouses, and your own savings.

Threaded through it is the interactive bathtub — two independent taps and a time slider — so you can watch a level integrate a flow, freeze at any height when the taps match, and refuse to empty in a hurry. By the end, “stock” and “flow” will stop being vocabulary and start being a reflex: the first cut you make on any problem where something builds up over time. This is the floor the rest of systems thinking is built on — and most people never actually pour it.