Checklist
Measure arrival rate, work in progress, and cycle time together
Flow variables constrain one another.
Before you use it
- Use when
- When teams argue about speed using only one flow metric.
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.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Checklist
- Fix one process boundary.
- Measure average completed rate.
- Measure average WIP.
- Measure average elapsed time and check consistency.
Why it matters
Track throughput or arrival rate, average work in process and average time in system on the same boundary. Use Little's Law as a consistency check when assumptions are approximately appropriate.
An example
A workstream reports ten items finished per week, twenty items active and roughly two weeks average elapsed time; the three measures tell a coherent story.
Check your result
The three quantities use the same boundary and time basis and gross inconsistencies are investigated.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingMeasure arrival rate, work in progress, and cycle time together
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaTurn the causal map into a testable model question
Evidence and sources
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
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.