Work in Queue
Work in queue is work that has arrived at a process step but has not started yet — it is waiting its turn. In Lean production it is the part of work in progress (WIP) that is sitting still: orders in an inbox, parts on a rack in front of a machine, tickets in a backlog.
Work in queue adds lead time but no value, so reducing it is one of the fastest ways to shorten delivery without making anyone work faster.
Little’s Law: the cost of a queue
Little’s Law links the amount of work in the system to how long it takes: lead time = WIP ÷ throughput. If a team finishes 20 orders a day and 200 orders are waiting or in progress, a new order will take about 10 days to come out, even if the actual work on it takes an hour. Cutting the queue to 60 orders brings that down to about 3 days with the same people and the same throughput.
What causes long queues?
- Batching: work is released or moved in large lots, so each unit waits for the rest of its batch.
- Unbalanced steps: a slow step (the bottleneck) gets work faster than it can finish it; see line balancing and the theory of constraints.
- Very high utilization: queueing theory shows that waiting time rises sharply as a resource gets close to 100% busy, especially when arrivals and task times vary.
- Push scheduling: starting work because it is available rather than because the next step can take it. A pull system or kanban limits that.
How do you reduce work in queue?
- Map the process and count what is waiting in front of each step (a value stream map does this).
- Set a WIP limit for each queue and stop releasing new work when it is full.
- Cut batch sizes and move work as soon as each unit is done.
- Add capacity or offload work only at the bottleneck; elsewhere it just moves the queue.
Frequently asked questions
What is the difference between work in queue and work in progress?
Work in progress is everything that has started and is not finished. Work in queue is the part of it that is waiting for the next step. Work being actively processed is the rest.
Is a queue always waste?
A small, deliberate buffer in front of the bottleneck protects throughput, so it can be useful. Anything beyond that buffer is the Lean waste of waiting and excess inventory; see the 8 wastes.
See also: work in progress (WIP), touch time, and throughput.
Related line-balancing and flow topics in this guide: Yamazumi charts.
Last updated: · Published by Lean Six Sigma Training Guide (sixsigmatrainingfree.com) · How this guide is written