Standard : Time in Queue

Description

Time in Queue measures how long a work item spends waiting in a non-active state between stages of the delivery process. It captures invisible delays that increase lead time and reduce flow efficiency.

This metric helps teams identify bottlenecks, handoff issues, and systemic delays—key sources of waste in Lean delivery systems. Reducing queue times accelerates feedback loops and overall time to value.

How to Use

What to Measure

  • Time spent in inactive states (e.g. “To Do”, “Ready for Dev”, “Waiting for Review”) before the next action begins.
  • Optional: measure queue time between each stage or cumulatively across the process.
  • Segment by work item type to detect patterns (e.g. tech debt vs features).

Formula

Time in Queue = Timestamp of Next Stage Start – Timestamp of Prior Stage Completion

You can also calculate:

  • Average Time in Queue per stage
  • Total Queue Time per Work Item
  • Queue Time Ratio = Time in Queue ÷ Total Cycle Time

Instrumentation Tips

  • Ensure workflow tools capture state transitions with timestamps.
  • Define clearly what counts as “waiting” in your context.
  • Visualise time in queue per stage using cumulative flow diagrams or ageing charts.
  • Use alerting when queue times exceed team-defined thresholds.

Why It Matters

  • Reveals hidden delays: Most delivery friction happens in wait states, not active work.
  • Enables better flow control: Helps teams unblock handoffs and overloaded stages.
  • Improves lead time: Reducing queues directly shortens time to value.
  • Supports sustainable delivery: Minimising queues reduces stress and firefighting.

Best Practices

  • Regularly review queue time in retrospectives to identify process inefficiencies.
  • Swarm on ageing or long-waiting work during stand-ups.
  • Address root causes of bottlenecks (e.g. review load, shared resource constraints).
  • Pair this metric with WIP limits and service-level expectations (SLEs).
  • Make queue time part of forecasting conversations, not just execution metrics.

Common Pitfalls

  • Ignoring queues between teams or across system boundaries.
  • Inconsistently tagging or transitioning items in workflow tools.
  • Overlooking systemic causes (e.g. unclear ownership or approval bottlenecks).
  • Focusing only on averages—outliers are where the risk lies.

Signals of Success

  • Queue time is visible and actively discussed in team rituals.
  • Teams know which stages commonly cause delay and have improvement experiments in play.
  • Overall lead time reduces as queues shrink and flow becomes smoother.
  • Work is picked up quickly once it reaches a ready state.
  • [[Cycle Time]]
  • [[Flow Efficiency]]
  • [[Work Item Age]]
  • [[Throughput]]
  • [[Blocked Work Duration]]