Little’s Law explains the relationship between:
• How much work is in the system
• How fast work gets done
• How long things take
• It can be simplified as:
Lead Time ≈ Work In Progress ÷ Throughput
That’s it.
No motivation speech.
No transformation program.
Just math.
If you increase the amount of work in progress,
lead time increases.
If you reduce work in progress,
lead time drops.
It doesn’t matter if you “feel productive”.
The system doesn’t care.
Little’s Law Is Why Your “Efficiency” Is a Lie
Most companies don’t have a capacity problem.
They have a WIP addiction.
They say things like:
• “We just need everyone fully utilized.”
• “Let’s start it now so we don’t waste time.”
• “We’ll finish it when things calm down.”
Little’s Law doesn’t care about your optimism.
If you increase work in progress, lead time increases.
Not because people are lazy.
Not because planning is weak.
Not because motivation is low.
Because physics.
Here’s the uncomfortable part
When you flood the system with work, you don’t increase output.
You increase:
• waiting
• switching
• confusion
• invisible queues
And then you blame:
• managers
• engineers
• operators
• “lack of ownership”
Instead of blaming the system design.
The real reason people resist WIP limits?
Because starting feels productive.
Finishing feels risky.
If you limit work, you’re forced to expose:
• bottlenecks
• bad prioritization
• unrealistic demand
• weak leadership
WIP hides dysfunction.
Flow exposes it.
And exposure is uncomfortable.
The Executive
At the top, this often shows up as:
“Why is everything late? Everyone is busy.”
Because being busy is not the same as flowing.
Little’s Law is the mathematical proof that:
You cannot optimize local activity and expect global speed.
But that’s exactly what most organizations reward.
The Psychological Impact
When everything is started but nothing is finished:
• morale drops
• stress rises
• context switching explodes
• burnout creeps in
Not because people are weak.
Because the system is overloaded.
🔗 Burnout
The Harsh Summary
If your lead times are long, one of three things is true:
You have too much WIP.
You have hidden queues.
You’re lying to yourself about both.
Little’s Law doesn’t fix your culture.
But it removes your excuses.
Example (Production)
You have:
• 100 units in the system
• You ship 10 per day
Lead time = 10 days.
Now you reduce WIP to 50 units.
Throughput stays 10 per day.
Lead time = 5 days.
You didn’t speed up.
You removed waiting.
Example (Project / Knowledge Work)
You have:
• 20 active tasks
• You finish 2 per week
Lead time = 10 weeks.
Reduce active tasks to 10.
Still finish 2 per week.
Lead time = 5 weeks.
Nothing magical happened.
You stopped starting everything at once.
Usually you won’t.
Because most companies don’t talk about system math.
You’ll hear:
“We need better prioritization.”
“We need more accountability.”
“We need ownership.”
What they often need is:
Less work in progress.
✅Yes — brutally.
If you:
• Wait on approvals
• Wait on materials
• Wait on feedback
• Wait on other teams
You are living inside Little’s Law.
It explains:
• Why projects drag
• Why delivery dates slip
• Why stress rises when workload increases
It also explains why reducing WIP can reduce burnout.
Less congestion = less cognitive overload.
🔗 Burnout
Little’s Law means “work less.”
Little’s Law only applies to factories.
Little’s Law is theoretical.
Reality:
It applies to any system where:
Work enters
Work flows
Work exits
That includes:
Factories.
Offices.
Product teams.
Email inboxes.
🚩 If people are rewarded for starting work instead of finishing it.
🚩 If every team optimizes for local efficiency instead of system flow.
🚩 If management increases WIP when delivery slows down.
🚩 If “we’re overloaded” is constant — but nothing gets deprioritized.
That’s not a motivation issue.
That’s system math being ignored.
5/5
Because once you see it,
you can’t unsee it.
The original idea
John Little formalized the relationship in 1961.
The law states:
L = λ × W
Where:
• L = average number of items in the system (WIP)
• λ = average throughput
• W = average time in system (Lead Time)
Rearranged:
Lead Time = WIP ÷ Throughput
That’s the engine behind Lean flow.
🔗 Lean
Why companies fight this law
Because reducing WIP feels dangerous.
It means:
• Saying no
• Stopping work
• Delaying starts
• Limiting multitasking
It exposes bottlenecks.
It removes buffers.
It forces trade-offs.
🔗 Bottleneck
🔗 Trade-off
That discomfort is exactly why Lean systems feel fragile at first.
They are no longer hiding problems.
The system effect
Little’s Law doesn’t promise faster workers.
It promises shorter queues.
Queues are invisible until they hurt.
Then people blame:
• Managers
• Priorities
• Motivation
• Culture
Sometimes it’s just math.
Why it links everything
Little’s Law connects directly to:
• WIP limits (Kanban)
• Flow
• Lead Time
• Bottlenecks
• Burnout
It’s not a tool.
It’s the rule underneath the tools.
The uncomfortable truth
If your organization has:
• High WIP
• Long lead times
• Constant urgency
It’s not chaotic.
It’s predictable.
The system is behaving exactly as designed.
Little’s Law isn’t motivational.
It’s mechanical.
Ignore it — and you’ll keep “optimizing” the wrong things.
Use it — and you start changing the system.
Found something wrong or misleading? Let us know — we want this site to stay fact-based (even when we joke).