Systems-Thinking-Stocks-Flows-Feedback

Systems thinking provides a vocabulary for understanding how engineering organisations actually behave over time. Will Larson draws directly from Donella Meadows’ Thinking in Systems and applies it to management, arguing that most management frustration stems from misunderstanding how stocks, flows, and delays interact.

Core Vocabulary

• Stock: Any measurable quantity that accumulates or depletes over time.

  • Management examples: team headcount, technical debt, employee morale, open bug count, backlog size, institutional knowledge.
  • Stocks change slowly — they cannot jump instantly, even when flows change dramatically.

• Flow: The rate of change of a stock. Inflows increase it; outflows decrease it.

  • Examples: hiring rate (inflow to headcount), attrition rate (outflow), bug-introduction rate (inflow to bug count), fix rate (outflow).

• Information link: How one part of the system observes another and adjusts behaviour.

  • Example: deployment failure rate feeds back to change how frequently the team deploys.

• Feedback loop: A circular causal path where a change in a stock influences its own future change via flows. Two types:

  • Reinforcing (positive): Amplifies change in one direction — growth or collapse.
    • Example: high morale → quality work → recognition → higher morale.
    • Danger: technical debt can self-amplify. More debt → slower velocity → less capacity to repay debt → more debt.
  • Balancing (negative): Resists change, seeks equilibrium.
    • Example: growing backlog → manager hires engineers → backlog shrinks → hiring slows.

• Delays: Time lags between a flow change and the resulting stock change.

  • Hiring takes 3–6 months; a new hire takes additional months to become fully productive.
  • Delays cause managers to overcorrect: if a fix doesn’t appear quickly, the instinct is to intervene again — adding more engineers, cutting more scope — which overshoots equilibrium once the original intervention finally takes effect.

Why This Matters for Managers

Most management interventions act on flows (hiring, firing, prioritisation decisions), but success is judged by stock changes (team performance, product quality, morale). The disconnect — bridged by delays — is the structural source of most management frustration and thrashing.

Practical diagnosis questions:

• What are the key stocks in this situation? (What accumulates?)
• What flows are driving them? (What are the inflow/outflow rates?)
• Where are the delays? (How long before an intervention takes effect?)
• Which feedback loops are active? (Reinforcing or balancing? What is being amplified?)

Related Concepts

• Larson-2019-An-Elegant-Puzzle
• Four-States-of-a-Team
• Systems-Thinking
• Feedback-Loops-in-Systems
• Organizational-Debt
• Technical-Migrations-De-risk-Enable-Finish

Sources

• Meadows, Donella H. (2008). Thinking in Systems: A Primer. Chelsea Green Publishing. ISBN: 978-1-60358-055-7.

  • Chapters 1–2: foundational definitions of stocks, flows, feedback loops, and delays; the primary source Larson draws from.

• Larson, Will (2019). An Elegant Puzzle: Systems of Engineering Management. Stripe Press. ISBN: 978-1-7322651-8-9.

  • Chapter 3.1: application of systems thinking vocabulary to engineering management and team capacity problems.

• Forrester, Jay W. (1961). Industrial Dynamics. MIT Press.

  • Original formalisation of system dynamics: stocks, flows, feedback, and delays in organisational systems. Foundation of the entire discipline.

• Senge, Peter M. (1990). The Fifth Discipline: The Art and Practice of the Learning Organization. Doubleday. ISBN: 978-0-385-26094-7.

  • Chapter 5: systems archetypes including reinforcing and balancing loops; applied to organisational learning and management. Popularised Forrester’s ideas for mainstream management audiences.

• Sterman, John D. (2000). Business Dynamics: Systems Thinking and Modeling for a Complex World. McGraw-Hill. ISBN: 978-0-07-231135-8.

  • Chapter 2: stocks, flows, and feedback in business systems; empirical evidence for delay-driven overcorrection and oscillation in management contexts.

Note

This content was drafted with assistance from AI tools for research, organization, and initial content generation. All final content has been reviewed, fact-checked, and edited by the author to ensure accuracy and alignment with the author’s intentions and perspective.