Catalog
concept#Architecture#Software Engineering#Analytics#Product

Stocks and Flows

A systems-thinking model that distinguishes accumulations (stocks) from rates of change (flows) to understand dynamic behavior and feedback.

Stocks and flows is a systems-thinking concept distinguishing accumulations (stocks) from rates of change (flows).
Established
Medium

Classification

  • Medium
  • Organizational
  • Architectural
  • Intermediate

Technical context

Data platforms for time series deliveryModeling tools (e.g., PySD, Vensim)Dashboards for visualization and monitoring

Principles & goals

Distinguish stocks from flows to make dynamics explicit.Account for delays and feedback when planning interventions.Use simple models first before increasing complexity.
Discovery
Domain, Team

Use cases & scenarios

Compromises

  • Oversimplification yields unusable recommendations.
  • Wrong assumptions about feedback can worsen decisions.
  • Overreliance on model-based forecasts.
  • Start with clear, bounded questions.
  • Validate models against historical data where possible.
  • Use visualizations to make feedback loops understandable.

I/O & resources

  • Time series of inflow and outflow rates
  • Initial stock levels
  • Descriptions of feedback mechanisms
  • Simulation runs with scenario results
  • Visualized stock-and-flow diagrams
  • Recommendations for control measures

Description

Stocks and flows is a systems-thinking concept distinguishing accumulations (stocks) from rates of change (flows). It helps model dynamic behavior of systems, identify delays and feedback, and predict long-term effects of interventions. Useful for system dynamics modeling, architectural reasoning, and cross-disciplinary decision making.

✔

  • Improved understanding of cause-effect relationships in systems.
  • Enables prediction of long-term consequences of decisions.
  • Helps systematically identify bottlenecks and levers.

✖

  • Models can be misleading with inaccurate parameters.
  • Not suitable for fine-grained, single-transaction analyses.
  • Requires data for calibration and validation.

  • Throughput

    Number of processed units per time; indicator of flow performance.

  • Stock size

    Current accumulation of units; shows congestions or buffers.

  • Lead time

    Time from arrival to completion; measure of delays in the system.

Use in product growth models

Product teams model user stocks and flows to prioritize marketing levers.

System dynamics in supply chains

Modeling inventories and ordering rates to avoid bullwhip effects.

Service operations and queue management

Analysis of throughput and backlog to stabilize SLAs.

1

Define scope and stocks to be modeled.

2

Identify flows, feedbacks, and delays.

3

Build a simple model, simulate, and iteratively validate.

⚠️ Technical debt & bottlenecks

  • Unmaintained assumptions list and parameter documentation
  • Outdated data interfaces for flow metrics
  • Lack of tests for reproducibility of simulation results
Data quality and availabilityUnclear assumptions about feedback pathsLack of modeling expertise
  • Using it for short-term KPI optimization without considering long-term effects.
  • Releasing models based on unvalidated assumptions.
  • Introducing complex models in organizations lacking modeling competence.
  • Missing calibration leads to false decision support.
  • Confusing correlation with causal flow behavior.
  • Scaling the model too quickly without stakeholder review.
Basics of system dynamicsAbility to interpret dynamic modelsKnowledge in data analysis and time series
Understandability of dynamic effectsPredictability of long-term system statesAbility to identify bottlenecks
  • • Limited data for calibration
  • • Time budget for modeling and validation
  • • Organizational readiness for systemic perspectives