Little's Law: The Math of Flow
The fundamental equation that explains why limiting WIP works.
1The Queue Theory Foundation
Little's Law is a mathematical relationship discovered by John Little in 1961. It's not an approximation or a rule of thumb—it's proven mathematics that applies to any stable system.
The law states:
Lead Time = Work in Progress / Throughput
Or rearranged:
WIP = Throughput × Lead Time
Where:
- Lead Time: How long an item takes from start to finish
- WIP (Work in Progress): Items currently in the system
- Throughput: Items completed per unit time
This relationship is always true for stable systems. It's not a Kanban idea—it's physics.
The Core Insight
If you want shorter lead times without increasing throughput (capacity), you must reduce WIP. There's no other way. Little's Law guarantees it.
2Why This Matters for Teams
Let's make this concrete.
Example: Your team completes 10 items per week (throughput). You currently have 40 items in progress (WIP).
Lead Time = 40 / 10 = 4 weeks
Now imagine you limit WIP to 20 items:
Lead Time = 20 / 10 = 2 weeks
Same team. Same throughput. Half the lead time. You didn't work faster. You just stopped starting so many things.
This is why WIP limits work. They directly reduce lead time by reducing the queue of work waiting for attention.
A highway has fixed capacity (throughput). When too many cars enter (high WIP), traffic slows to a crawl and commute times skyrocket. Metering lights at on-ramps limit WIP to keep traffic flowing.
An ER that accepts unlimited patients ends up with people waiting for hours. ERs that limit intake (via triage and diversion) get patients treated faster, even though they see the same number overall.
3Throughput, Not Speed
A common misconception: "If we start more things, we'll finish more things."
This seems intuitive but is wrong. Here's why:
Context switching has costs:
- Remembering where you left off
- Rebuilding mental models
- Communication overhead
- Merge conflicts from parallel work
When WIP is too high, these costs multiply. People spend more time switching than working. Throughput actually decreases.
The counterintuitive truth: By limiting WIP, you often increase throughput while definitely reducing lead time.
The factory analogy: A factory that starts making 1000 cars simultaneously finishes 0 cars for months. A factory that limits WIP to 10 cars finishes 10 cars quickly, then 10 more.
The Utilization Trap
100% utilization of people actually decreases throughput. Some slack is necessary for flow. We'll cover this in detail later.
4Stability Matters
Little's Law requires a stable system—one where the average arrival rate roughly matches the completion rate over time.
Unstable systems (where work piles up faster than it's completed) break the relationship. Lead times grow unbounded.
Signs of instability:
- Backlog grows continuously
- "In Progress" column fills up
- Old items age out without ever being started
- Team feels increasingly overwhelmed
What to do:
- Stop accepting more work than you can complete
- Reduce WIP to bring the system back to stability
- Address the root cause (capacity vs. demand mismatch)
Kanban doesn't magically fix a demand > capacity problem. It makes the problem visible so you can address it.
- Little's Law: Lead Time = WIP / Throughput (always true for stable systems)
- Reducing WIP directly reduces lead time without changing throughput
- High WIP causes context switching that reduces throughput
- Stable systems require demand to roughly match capacity