Standard : Flow Efficiency (Active Time vs Wait Time)

Description

Flow Efficiency measures the proportion of time a work item spends in active progress compared to total time in the system (from start to finish). It reveals how much of the cycle time is spent on actual value-adding activity versus waiting, delays or handoffs.

Low flow efficiency typically indicates bottlenecks, blockers, queues or multitasking, all of which slow delivery and reduce throughput. This metric helps teams identify and reduce waste in their process.

How to Use

What to Measure

  • Active Time: Time spent actively working on the item (e.g. in development, testing, design).
  • Wait Time: Time spent waiting (e.g. in backlog queues, review columns, blocked states).
  • Total Cycle Time = Active Time + Wait Time

Measure across multiple items and track trends per team, work type or stage.

Formula

Flow Efficiency (%) = (Active Time / Total Cycle Time) x 100

Example: If an item spent 2 days being worked on and 8 days waiting, flow efficiency = (2 / 10) x 100 = 20%.

Instrumentation Tips

  • Use workflow states to distinguish active vs passive (e.g. “In Progress”, “Code Review” as active; “To Do”, “Waiting” as passive).
  • Use timestamps from ticketing systems or value stream tools to calculate time in each state.
  • Tag items when they become blocked or delayed to improve data accuracy.

Benchmarks

Flow efficiency varies significantly, but general guidance:

Flow Efficiency Interpretation
40–60% Very efficient (rare and advanced)
20–39% Healthy flow with minor delays
10–19% Moderate inefficiencies
<10% High friction and systemic waste

Most teams start with low flow efficiency (~10–15%) and improve through process optimisation.

Why It Matters

  • Visualises hidden delays
    Exposes queues, handoffs and blockers that elongate cycle time.

  • Supports lean thinking
    Encourages teams to reduce waste and improve value delivery speed.

  • Improves predictability
    Work flows more consistently when less time is spent in limbo.

  • Drives continuous improvement
    Creates a baseline to measure changes in process design or team behaviour.

Best Practices

  • Start by mapping your value stream to understand work states.
  • Regularly review cumulative flow diagrams and WIP ageing charts.
  • Focus improvement efforts on the longest wait stages first.
  • Use flow efficiency data in retrospectives to guide discussion.
  • Track improvements alongside cycle time and throughput.

Common Pitfalls

  • Misclassifying states as active when no real progress is occurring.
  • Tracking only averages and missing skew caused by outliers.
  • Ignoring work in blocked or paused states that distorts active time.
  • Focusing on efficiency alone and sacrificing quality or collaboration.

Signals of Success

  • Decrease in average wait time across key stages of the workflow.
  • Clear identification and removal of systemic blockers or bottlenecks.
  • Increased flow efficiency alongside consistent cycle times and delivery.
  • Teams using flow efficiency to guide conversations about process health.
  • [[Cycle Time per Work Item Type]]
  • [[Blocked Time per Work Item]]
  • [[Work in Progress per Team or Stream]]
  • [[Queue Time Between Workflow Stages]]

Aligned Industry Research

  • Lean Thinking (Womack & Jones)
    Focuses on removing waste from systems to maximise value delivery.

  • Kanban Method (David J. Anderson)
    Flow efficiency is a key signal of system health and process maturity.

  • Value Stream Management (Tasktop, Flow Framework)
    Emphasises measuring flow metrics (like efficiency) to optimise software delivery pipelines.