Contents
Use this when you need to understand why something keeps growing, shrinking, or stubbornly refusing to change — and your spreadsheet shows you the snapshots but not the plumbing. Stock and flow diagrams force you to distinguish between accumulations (the stuff that piles up) and the rates that fill or drain them, revealing the dynamic structure that drives every system you care about.
Section 1
What This Tool Does
Your SaaS dashboard says you have 14,000 customers. That number went up by 800 this quarter. Good news? Depends entirely on questions the dashboard doesn't answer. How many new customers signed up? How many churned? Is the 800 net figure the result of 1,200 in and 400 out, or 3,000 in and 2,200 out? Those two scenarios describe radically different businesses — one healthy, one hemorrhaging — yet they produce the identical headline number. The stock is the same. The flows are not.
This is the central confusion that stock and flow diagrams exist to resolve. Jay Forrester, an MIT electrical engineer turned management theorist, developed the notation in the early 1960s as part of his system dynamics work. He'd been modelling industrial supply chains and urban systems, and he kept encountering the same pattern: smart people — executives, policymakers, engineers — made catastrophically wrong decisions because they confused levels with rates. They'd see inventory rising and cut production, not realising that the rise was caused by a temporary dip in shipping that was about to reverse. They'd see a city's population growing and build housing, not realising that the growth rate was already declining and the housing would sit empty. The errors weren't random. They were systematic, and they stemmed from a single cognitive failure: the inability to intuitively track accumulations over time.
Forrester's insight was that every dynamic system can be decomposed into just two types of elements. Stocks are accumulations — things that pile up and can be measured at a point in time. Cash in the bank. Employees on the payroll. Carbon in the atmosphere. Reputation in the market. Flows are rates — things that change stocks over time. Revenue per month. Hires per quarter. Emissions per year. Positive press mentions per week. A stock is a bathtub. Flows are the faucet and the drain. The water level at any moment is the stock. The rate of water coming in minus the rate going out determines whether the level rises, falls, or holds steady. That's the whole model.
The reason this matters — the reason it's worth formalising something that sounds obvious — is that human intuition is reliably terrible at tracking accumulations. Decades of research by John Sterman at MIT have demonstrated that even highly educated professionals fail basic stock-and-flow reasoning tasks. Show people a graph of inflows and outflows and ask them to sketch the resulting stock level, and the majority get it wrong. They confuse the flow with the stock. They assume that when inflow drops, the stock drops — when in fact the stock keeps rising as long as inflow exceeds outflow, just more slowly. This isn't a minor cognitive wrinkle. It's a fundamental bug in human reasoning about dynamic systems, and it explains why companies overshoot on hiring, why governments undershoot on infrastructure, and why individuals consistently misjudge how long it takes to build — or destroy — anything that accumulates.
The diagram itself is the intervention. Drawing the stocks as rectangles, the flows as pipes with valves, and the connections between them as arrows forces you to make the structure explicit. Once it's on paper, the bathtub logic becomes obvious. You can see that customer count is a stock fed by acquisition and drained by churn. You can see that brand equity accumulates slowly through consistent delivery and drains quickly through scandal. You can see that technical debt is a stock that grows with every shortcut and shrinks only through deliberate refactoring. The diagram doesn't tell you what to do. It tells you what's actually happening — which turns out to be the harder problem.
Section 2
How to Use It — Step by Step
Instructions on the left. Worked example — "Why is our engineering team's velocity declining despite continuous hiring?" — on the right.
Step 1 — Identify
Name the key stocks in your system
Start with the accumulation you care about most — the thing whose level you're trying to understand or influence. Then ask: what other accumulations feed into or constrain this one? Stocks are nouns. They're measurable at a point in time. If you can say "right now we have X of this," it's a stock. Cash balance, headcount, active users, technical debt, trained employees, open bugs — all stocks. List 2–5 that are central to the behaviour you're trying to explain. Resist the temptation to list everything. Start with the minimum set that captures the dynamic you're puzzling over.
Worked example
Engineering velocity decline
The team identifies three stocks: Experienced Engineers (those with >6 months tenure who are fully productive), New Engineers (those in their first 6 months, still ramping), and Technical Debt (accumulated shortcuts, outdated code, and unresolved architectural issues measured in estimated remediation hours). Velocity — the thing leadership is watching — is an output of how these three stocks interact, not a stock itself.
Step 2 — Map
Draw the flows that change each stock
For every stock, ask two questions: What makes this go up? What makes this go down? These are your inflows and outflows. Flows are verbs — hiring, quitting, accumulating, resolving, onboarding, graduating. Draw them as pipes with arrows showing direction. Every flow has a rate (units per time period). Be specific about the time unit: per week, per month, per quarter. A stock with no outflow only grows. A stock with no inflow only shrinks. If you find a stock with neither, it's not a stock — it's a constant. Remove it.
Worked example
Mapping the flows
New Engineers stock: Inflow = hiring rate (engineers per month). Outflow = onboarding completion rate (engineers who become experienced per month) + early attrition rate (new hires who leave before completing onboarding). Experienced Engineers stock: Inflow = onboarding completion rate (from New Engineers). Outflow = attrition rate (experienced engineers leaving per month). Technical Debt stock: Inflow = debt accumulation rate (hours of new debt created per sprint). Outflow = debt remediation rate (hours of debt resolved per sprint).
Step 3 — Connect
Identify what influences each flow rate
This is where the diagram becomes powerful. Flow rates aren't constants — they're influenced by stocks, by other flows, and by external factors. Draw arrows from the influencing element to the flow it affects, marking each with a "+" (same direction) or "−" (opposite direction). These connections reveal the feedback loops that drive system behaviour. A stock that influences its own inflow or outflow creates a feedback loop — and feedback loops are where all interesting dynamics live.
Worked example
Revealing the hidden feedback
Here's what the connections expose: As New Engineers increases, experienced engineers spend more time mentoring and less time coding, which reduces their effective velocity and increases the debt accumulation rate (because mentoring time means more shortcuts elsewhere). As Technical Debt rises, all engineers spend more time navigating bad code, which reduces velocity further and increases attrition among experienced engineers (who are most frustrated by working in degraded codebases). And as Experienced Engineers decreases through attrition, the onboarding completion rate slows (fewer mentors), which means new hires stay in the "New" stock longer, which means more mentoring burden on the remaining experienced engineers. A vicious cycle. Three reinforcing feedback loops, all invisible in the headcount spreadsheet.
Step 4 — Quantify
Estimate the magnitudes and check the arithmetic
Assign rough numbers to each stock level and flow rate. You don't need precision — order of magnitude is enough to reveal whether the system is in equilibrium, growing, or declining. Then do the bathtub check: for each stock, subtract total outflow from total inflow. Is the stock rising, falling, or stable? Does that match what you're actually observing? If not, you've missed a flow or misjudged a rate. This arithmetic step catches structural errors in your model before you act on it.
Worked example
Running the numbers
Current state: Experienced Engineers = 30. New Engineers = 18. Technical Debt = ~2,400 remediation hours. Flows: Hiring rate = 6/month. Onboarding completion = 3/month (half the rate it should be — mentoring bottleneck). Early attrition = 1/month. Experienced attrition = 4/month. Net change in Experienced Engineers: +3 (from onboarding) − 4 (attrition) = −1 per month. The experienced engineer stock is shrinking despite aggressive hiring. Technical debt: accumulating at ~200 hours/sprint, remediated at ~80 hours/sprint. Net: +120 hours/sprint. Both critical stocks are moving in the wrong direction. Hiring faster won't fix this — it will make it worse by increasing the mentoring burden on a shrinking pool of experienced engineers.
Step 5 — Intervene
Identify the highest-leverage flow to change
Look at the feedback loops you've mapped. Which flow, if changed, would shift the system's trajectory most? The highest-leverage intervention is rarely the most obvious one. In systems with reinforcing loops, small changes to the right flow can cascade. Large changes to the wrong flow get absorbed. Use the diagram to simulate: "If we changed this flow rate by X, what happens to each stock over the next 3–6 months?" Trace it through. The diagram makes this tracing possible in a way that intuition alone cannot.
Worked example
Finding the lever
The obvious intervention — hire even faster — would increase the New Engineers stock, increase mentoring burden, accelerate experienced engineer attrition, and worsen the spiral. The diagram reveals three higher-leverage moves: (1) Reduce experienced attrition by addressing the technical debt that's driving frustration — even a reduction from 4/month to 2/month flips the experienced stock from shrinking to growing. (2) Slow hiring temporarily to reduce mentoring load, freeing experienced engineers to remediate debt. (3) Create a dedicated onboarding programme that doesn't rely on 1:1 mentoring from senior engineers, decoupling the onboarding flow from the experienced engineer stock. The counterintuitive answer: hire fewer people, fix the codebase, and velocity will recover within two quarters.
Section 3
When It Works Best
✓
Ideal Conditions for Stock and Flow Diagrams
| Dimension | Best fit |
|---|---|
| Problem type | Situations where something is accumulating or depleting in ways that surprise you. The tool is built for "why does this keep getting worse despite our efforts?" problems — the ones where the intervention seems correct but the outcome doesn't improve, or where a metric moves in the opposite direction from what the action should produce. |
| Time horizon | Medium to long-term dynamics where delays matter. Stocks change slowly relative to flows. If you're making a decision that plays out over weeks or months — hiring plans, product roadmaps, market entry timing, debt management — stock-and-flow thinking reveals dynamics that snapshot metrics hide. |
| Complexity profile | Systems with 2–6 interacting stocks and feedback loops. Below two stocks, the dynamics are usually intuitive enough to reason about without a diagram. Above six, the model becomes unwieldy and you need simulation software. The sweet spot is the 3–5 stock system where the interactions are non-obvious but still traceable by hand. |
| Stakeholder alignment | Situations where different people in the room have different mental models of how the system works. The diagram externalises assumptions. When the VP of Engineering says "we need to hire faster" and the CTO says "we need to slow down and fix the codebase," the stock-and-flow diagram reveals that both are describing the same system but focusing on different flows. It makes the disagreement structural rather than personal. |
| Decision type | Resource allocation and timing decisions. How fast to hire. When to invest in infrastructure versus growth. How much to spend on acquisition versus retention. These are all questions about flow rates, and the right answer depends on the current state of the stocks — which the diagram makes visible. |
| Data availability | Works even with rough estimates. You don't need precise flow rates to get value — directional accuracy ("attrition is higher than onboarding completion") is enough to reveal structural problems. Precision helps for simulation, but the qualitative diagram alone often surfaces the critical insight. |
Section 4
When It Breaks Down
⚠
Failure Modes
| Failure pattern | What goes wrong | What to use instead |
|---|---|---|
| Overcomplication | The modeller tries to capture every stock and flow in the system, producing a diagram with 15 stocks and 30 flows that nobody can read or reason about. The diagram becomes a monument to thoroughness rather than a tool for insight. Complexity in the model doesn't equal understanding of the system. | Start with the minimum viable model — 2–3 stocks. Add complexity only when the simple model can't explain the observed behaviour. |
| False precision | Teams assign exact numbers to flow rates they don't actually know, then treat the model's output as a forecast rather than a structural hypothesis. A stock-and-flow diagram with made-up numbers is a fiction engine. The model's value is in its structure (which flows connect to which stocks), not in its numerical output. | Use ranges instead of point estimates. Label uncertain rates explicitly. Treat the model as a thinking tool, not a calculator. |
| Missing delays | The diagram shows flows affecting stocks instantly, but real systems have delays — it takes 6 months for a new hire to become productive, 2 years for brand investment to show up in pricing power, a generation for educational policy to affect workforce quality. Ignoring delays makes the model predict faster responses than reality delivers, leading to premature abandonment of correct strategies. | Mark delays explicitly on the diagram with a double line or time annotation. Ask "how long before this flow actually changes this stock?" for every connection. |
| Static snapshot thinking | The team draws the diagram, identifies the current state, and designs an intervention — but doesn't trace the intervention forward through time. Stocks and flows are inherently dynamic. A policy that works when the stock is at level X may backfire when the stock reaches level Y because the feedback loops change character. The diagram is a map, not a photograph. | Simulate forward: "If we implement this change, what happens to each stock in month 1, month 3, month 6?" Trace it through by hand or use system dynamics software like Vensim or Stella. |
| Intangible stock confusion | Teams try to model things like "trust," "morale," or "culture" as stocks. These are real phenomena, but they're extremely difficult to measure, their flow rates are nearly impossible to estimate, and the connections between them and other stocks are speculative. The diagram looks rigorous but rests on unmeasurable foundations. | Use intangible stocks sparingly and only when they're the central dynamic you're investigating. For peripheral intangibles, use Causal Loop Diagrams instead — they capture the directional relationships without requiring quantification. |
| Ignoring external shocks | The model assumes smooth, continuous flows. But real systems experience discontinuities — a competitor launches, a regulation changes, a pandemic hits. Stock-and-flow models handle gradual change well and sudden disruption poorly. If your strategic question is "what happens if the market shifts overnight," this tool won't help. | Scenario Planning for discontinuous futures; Pre-Mortem for identifying potential shocks before they occur. |
The most dangerous failure mode is overcomplication, because it's driven by conscientiousness rather than laziness. The person who builds a 20-stock model isn't being sloppy — they're being thorough. But thoroughness in system dynamics modelling produces the opposite of its intended effect. A model you can't hold in your head is a model you can't reason about. And reasoning — not computation — is the point. Forrester himself was emphatic on this: the value of a stock-and-flow diagram is that it makes the structure of a system visible to human cognition. The moment the diagram exceeds cognitive capacity, it stops being a thinking tool and becomes a black box. Protect against this by enforcing a hard constraint: no more than five stocks in your first diagram. If five stocks can't explain the behaviour you're observing, the problem might be that you've chosen the wrong stocks, not that you need more of them.
Section 5
Visual Explanation
Stock and flow diagram — engineering velocity worked example. Rectangles are stocks, pipe-and-valve symbols are flows, dashed arrows show causal influences. The reinforcing feedback loop (R1) is the 'mentoring trap' that accelerates decline.
Section 6
Pairs With
Stock and flow diagrams reveal the accumulation structure of a system. They don't tell you what caused the structure, what to do about it, or how to communicate it. The tools below fill those gaps.
Use before
Iceberg Model
The Iceberg Model moves from visible events ("velocity is declining") to patterns, structures, and mental models. Stock and flow diagrams are the tool for making the "structure" layer explicit. Use the Iceberg to identify which structural layer to model; then use stocks and flows to build the model.
Use before
[5 Whys](/mental-models/5-whys)
Before drawing the diagram, use 5 Whys to identify which accumulations actually matter. "Why is velocity declining?" → "Because we're spending time mentoring." → "Why so much mentoring?" → "Because we hired 18 people in three months." Now you know that the New Engineers stock belongs in your model.
Use after
Causal Loop Diagrams
Once you've identified the stocks and flows, Causal Loop Diagrams let you zoom out and map the full feedback structure — including loops that don't involve measurable stocks. The stock-and-flow diagram is the quantitative core; the causal loop diagram is the qualitative context around it.
Use after
Second-Order Thinking
The diagram shows you the first-order effects of an intervention (change a flow rate, watch the stock respond). Second-Order Thinking pushes you to trace the consequences further: what happens when that stock level changes other flows? What happens to the system in month 6, not just month 1?
Mental model
Reinforcing [Feedback](/mental-models/feedback) Loop
Every stock-and-flow diagram contains feedback loops, and the reinforcing ones drive exponential growth or collapse. Understanding reinforcing loops as a mental model helps you spot them in your diagram — and recognise that they're the structures most likely to produce surprising, nonlinear behaviour.
Mental model
Balancing Feedback Loop
Balancing loops are the system's brakes — they push stocks toward equilibrium. If your diagram shows a stock that should be growing but isn't, look for a hidden balancing loop. If it shows a stock that's oscillating, you've likely got a balancing loop with a delay.
Section 7
Real-World Application
Amazon — the flywheel as a stock-and-flow system
The scenario
Jeff Bezos famously sketched Amazon's growth flywheel on a napkin in 2001. The drawing — lower prices → more customers → more sellers → better selection → better customer experience → more traffic → lower cost structure → lower prices — has been reproduced in thousands of strategy presentations. What's less commonly understood is that the flywheel is, structurally, a stock-and-flow diagram with the stocks left implicit. Each node in the flywheel is actually a stock (number of customers, number of sellers, breadth of selection, cumulative cost efficiency), and each arrow is a flow that fills or drains those stocks. Bezos's genius wasn't the circular diagram. It was the recognition that Amazon's competitive advantage was an accumulation problem.
How the tool appliedAmazon's operational decisions throughout the 2000s and 2010s become legible as stock-and-flow interventions. The decision to launch Amazon Prime in 2005 was a flow-rate intervention: by converting casual buyers into subscribers, Prime increased the purchase frequency flow into the customer lifetime value stock. The decision to open the marketplace to third-party sellers was a flow-rate intervention on the selection stock: instead of Amazon sourcing every product (a slow inflow), millions of sellers could add products simultaneously (a massive inflow). The decision to build AWS and invest in fulfilment infrastructure was a flow-rate intervention on the cost structure stock: fixed costs accumulated, but the cost-per-unit outflow decreased as volume grew, creating an accumulating cost advantage that competitors couldn't replicate without matching the stock of infrastructure investment.
What it surfacedThe stock-and-flow lens reveals why Amazon's strategy was so difficult to compete against. Each stock in the system — customer base, seller base, selection breadth, infrastructure scale, cost efficiency — accumulated over years. Competitors could match any individual flow rate (offer lower prices, recruit sellers, build warehouses), but they couldn't match the stock levels that Amazon had accumulated over a decade. The stocks created the moat. A new entrant in 2015 could match Amazon's current flow rates but would still be a decade behind on stock levels. This is the fundamental insight that stock-and-flow thinking provides: competitive advantage lives in stocks, not flows. Anyone can copy a flow. Nobody can copy a stock without time.
The non-obvious factorWhat made Amazon's application of this thinking distinctive was Bezos's willingness to sacrifice short-term flow metrics (quarterly profit, a flow) to build long-term stocks (infrastructure, customer trust, seller ecosystem). Wall Street analysts who focused on the flows — revenue growth rate, margin percentage — consistently undervalued Amazon because they couldn't see the stocks accumulating beneath the surface. The stock-and-flow framework explains both Amazon's strategy and why that strategy was systematically misunderstood by observers who thought in flows rather than stocks. Bezos was filling bathtubs while everyone else was measuring the faucet.
Section 8
Analyst's Take
Faster Than Normal — Editorial View
Stock and flow diagrams are the most underused tool in the founder's toolkit — and the most overused in the academic's. In university system dynamics courses, students build 50-stock models with simulation software and lose the forest for the trees. In boardrooms, executives stare at dashboards full of flow metrics (monthly revenue, quarterly growth rate, weekly active users) and never once ask about the stocks those flows are filling or draining. The tool's power sits precisely between these two failure modes: a 3–5 stock diagram, sketched on a whiteboard in 30 minutes, that makes the accumulation structure of your business visible for the first time. That's the version that changes decisions.
The failure I see most often is what I'd call flow fixation — the tendency to manage flow rates while ignoring stock levels. A startup celebrates hitting 10,000 new signups per month (a flow) without noticing that the active user stock has been flat for six months because churn equals acquisition. A company hires aggressively (a flow) without tracking the experienced-employee stock, which is actually shrinking because attrition outpaces onboarding. A product team ships features rapidly (a flow) without measuring the technical debt stock, which is accumulating faster than it's being resolved. In every case, the flow metric looks healthy while the stock metric — the one that actually determines the company's trajectory — deteriorates. Drawing even a crude stock-and-flow diagram would surface the problem instantly. The bathtub is draining as fast as it's filling. You just can't see it because you're only watching the faucet.
The highest-leverage modification: draw your company's three most important stocks and ask "what is the net change per quarter?" Not the gross inflow. Not the outflow. The net. Customer stock: net adds after churn. Talent stock: net experienced headcount after attrition and onboarding delays. Cash stock: net burn after revenue. Capital stock: net infrastructure after depreciation. If any critical stock is declining or flat despite active investment in its inflow, you have a structural problem that no amount of flow-rate optimisation will fix. You need to either increase the inflow, decrease the outflow, or — most often — address the feedback loop that's coupling the two in a way that makes your efforts self-defeating. The diagram is how you find that loop. Five minutes with a whiteboard marker. It's the cheapest strategic insight available.
Section 9
Top Resources
01
Industrial Dynamics — Jay Forrester (1961)
Primary sourceThe origin text. Forrester introduces stocks, flows, feedback loops, and delays as the fundamental building blocks of dynamic systems, then applies them to industrial supply chains, inventory management, and corporate growth. Dense and technical — this is an engineering text, not a business book — but the first 100 pages contain the clearest explanation of stock-and-flow logic ever written. Every subsequent treatment derives from this.
02
The Fifth [Discipline](/mental-models/discipline) — Peter Senge (1990)
BookSenge translated Forrester's system dynamics into language that managers could use. The book's treatment of stocks, flows, and system archetypes (the "fixes that fail" pattern, the "shifting the burden" pattern) remains the most accessible entry point for practitioners. Chapter 5 on "A Shift of Mind" explains why stock-and-flow thinking is a cognitive skill that must be developed, not just a diagramming technique.
03
Business Dynamics: Systems Thinking and Modeling for a Complex World — John Sterman (2000)
BookThe definitive textbook. Sterman — Forrester's intellectual heir at MIT — covers stock-and-flow modelling from first principles through advanced simulation. Chapter 5 on "Causal Loop Diagrams" and Chapter 6 on "Stocks and Flows" are the essential reference. The book also documents the experimental evidence that humans systematically fail at stock-and-flow reasoning, which is the best argument for why the tool is necessary.
04
Thinking in Systems: A Primer — Donella Meadows (2008)
BookThe most elegant short treatment of stocks, flows, and feedback. Meadows — a Forrester student and lead author of The Limits to Growth — writes with a clarity that makes the concepts feel intuitive rather than technical. Her chapter on "leverage points" (where to intervene in a system) is the practical payoff: once you've drawn the diagram, Meadows tells you where to push.
05
Essay
Collins's flywheel concept is stock-and-flow thinking applied to competitive strategy, even though he doesn't use the formal notation. This essay — and the accompanying monograph — shows how companies like Amazon, Intel, and Vanguard built accumulating advantages by identifying the key stocks in their business and relentlessly optimising the flows that filled them. Read it as a bridge between Forrester's engineering notation and real strategic decision-making.
Decision Tools Library — Browse by phase
Why this matters next
mental modelsSecond-Order Thinking
Iceberg Model applied the Second-Order Thinking mental model
mental modelsLeverage
Iceberg Model applied the Leverage mental model
mental modelsTechnical Debt
Iceberg Model applied the Technical Debt mental model
mental models5 Whys
Iceberg Model applied the 5 Whys mental model
mental modelsSystems Thinking
Iceberg Model applied the Systems Thinking mental model
mental modelsScale
Iceberg Model applied the Scale mental model
Continue exploring
CCCDRLBLCMSA
Decision tool
Connection Circles
Map the elements of a system and the relationships between them — the simplest s
Decision tool
Causal Loop Diagrams
Formally map cause-and-effect relationships with polarity to show how variables
Decision tool
Reinforcing Feedback Loop
Understand the mechanism behind exponential growth and vicious/virtuous cycles
Decision tool
Balancing Feedback Loop
Understand the mechanism that pushes back against change to create stability or
Decision tool
Concept Map
Visualise relationships between entities in a concept or domain to build shared
Decision tool
System Archetypes
Recognise recurring structural patterns — Fixes that Fail, Shifting the Burden,
More like this, in your inbox
I send a newsletter every week — free, no spam, unsubscribe anytime.