Standard : Flow Efficiency

Description

Flow Efficiency measures the proportion of time that a work item is actively being worked on compared to the total time it spends in the system (from start to finish). It highlights how much of the delivery process is productive (value-adding) versus idle (waste).

This metric helps teams identify delays, bottlenecks, and systemic inefficiencies in their value stream. High flow efficiency means teams are spending most of their time moving work forward, not waiting.

How to Use

What to Measure

  • The amount of time a work item is actively in progress (hands-on work).
  • The total elapsed time the work item spends in the system (start to finish).
  • Calculate at the team, workflow stage, or initiative level.

Formula

Flow Efficiency (%) = (Active Time / Total Time) × 100

For example, if a work item takes 10 days from start to finish, but is actively worked on for 2 of those days, the flow efficiency is 20%.

Instrumentation Tips

  • Use value stream mapping or workflow analytics to classify active vs. waiting time.
  • Digital boards (e.g. Jira, Azure DevOps, Linear) can help timestamp transitions.
  • Automate logging of status changes where possible.
  • Use analytics tools that calculate flow efficiency directly from state transitions.

Why It Matters

  • Reveals delivery waste: Highlights where delays and inefficiencies are hiding.
  • Focuses improvement: Targets effort on removing wait time, not just increasing effort.
  • Improves predictability: Reduces cycle time variability by managing system flow.
  • Enables sustainable delivery: Encourages smooth, less stressful work patterns.

Best Practices

  • Visualise blocked and idle work explicitly on boards.
  • Run flow-based retrospectives to explore long queue or wait times.
  • Limit WIP to avoid overloading teams and stages in the process.
  • Break work into smaller increments to reduce wait time between dependencies.
  • Analyse and address systemic delays, not just individual behaviour.

Common Pitfalls

  • Treating all active time equally (e.g. not distinguishing between effort and context switching).
  • Ignoring the effect of dependencies or external approvals on wait time.
  • Overemphasising flow efficiency without considering value or quality.
  • Using tools that don’t support accurate time-in-state tracking.

Signals of Success

  • Teams identify and eliminate common causes of waiting (e.g. unclear handoffs, slow reviews).
  • Cycle time improves without increasing effort or team size.
  • Teams sustain a smooth and steady delivery pace over time.
  • Value flows predictably and consistently through the system.
  • [[Lead Time and Cycle Time]]
  • [[Time in Queue]]
  • [[Throughput]]
  • [[Flow Load]]
  • [[Blocked Work Age]]