Standard : Flow Load

Description

Flow Load refers to the total number of work items currently in progress across the value stream. It provides a system-level view of how much work is being handled at once, offering insight into team and system capacity, potential overburden, and delivery predictability.

Flow Load is a real-time health indicator: too high, and flow efficiency suffers; too low, and teams may be underutilised. Maintaining an optimal flow load helps sustain throughput while avoiding burnout.

How to Use

What to Measure

  • Count the number of work items in an active state (e.g. “In Progress”, “In Review”, “Testing”) at any given time.
  • Break down by team, service, or workflow stage for more granular insights.
  • Optional: track flow load over time as a trend or against WIP limits.

Formula

Flow Load = Total Number of Active Work Items

You can also monitor:

  • Flow Load per Person: Average WIP per team member.
  • Flow Load by Work Type: Feature, tech debt, bug, enabler, etc.

Instrumentation Tips

  • Use your work management tool to define and query “in progress” states.
  • Automate snapshots of flow load per team daily or weekly.
  • Visualise flow load alongside throughput and cycle time for richer insight.
  • Use dashboards to show flow load trends and alert when thresholds are breached.

Why It Matters

  • Optimises delivery flow: Too much WIP causes delays and inefficiency; too little reduces value creation.
  • Improves team focus: Encourages limiting multitasking and context switching.
  • Reveals bottlenecks: Sudden increases in flow load can indicate upstream overproduction or downstream delays.
  • Supports sustainable pace: Helps manage workload to reduce stress and improve wellbeing.

Best Practices

  • Set and honour WIP limits across workflows or swimlanes.
  • Monitor spikes in flow load during planning and delivery execution.
  • Encourage swarming to reduce work-in-progress when flow load grows.
  • Pair flow load with cycle time to spot emerging risks before deadlines slip.
  • Review flow load in retrospectives to explore root causes of delivery slowdowns.

Common Pitfalls

  • Counting “in progress” too broadly (e.g. including backlog or paused work).
  • Ignoring the impact of multitasking and partial attention on real capacity.
  • Relying only on average numbers rather than ranges and spikes.
  • Setting arbitrary WIP limits without considering team size or context.

Signals of Success

  • Teams maintain a healthy, stable flow load across delivery cycles.
  • Work moves consistently through the system without large build-ups.
  • Delivery feels focused and predictable, not frantic or chaotic.
  • Engineers report fewer interruptions and less task switching.
  • [[Cycle Time]]
  • [[Flow Efficiency]]
  • [[Throughput]]
  • [[Work Item Age]]
  • [[WIP Limit Adherence]]