Protocol
Limit parallel starts when completion is the goal
Reducing starts can expose capacity and shorten queues.
When it fits
- When individuals or teams carry many concurrent items and completion dates drift.
When to avoid it
- Queueing equations have specific assumptions. Use them for directional reasoning and measurement design, not as exact forecasts for arbitrary multi-stage knowledge work.
Why it matters
Set a temporary WIP limit at the relevant boundary, finish or explicitly stop work before starting another item, and compare cycle time and blocked-work patterns.
Steps
- Choose the boundary and current WIP.
- Set a conservative temporary limit.
- Define exceptions for urgent work.
- Measure completion time and blockage after the change.
An example
A consultant keeps two assessment-prep deliverables active instead of six half-finished drafts and measures whether finished artifacts appear faster.
Check your result
The experiment changes active WIP and checks completion behavior rather than assuming fewer starts are always better.
Keep this limit in mind
- Queueing equations have specific assumptions. Use them for directional reasoning and measurement design, not as exact forecasts for arbitrary multi-stage knowledge work.
Connected ideas
Use beforeFind the bottleneck from waiting, not busyness
Evidence and sources
Supports
Little's Law relates long-run average work in a stable system to arrival/throughput rate and average time in system as L = λW under stated mathematical conditions.
The relation does not identify root cause, queue discipline or the correct intervention; workplace applications must respect the assumptions.
A Proof for the Queuing Formula: L = λW · Abstract