Little's Law: the formula every ops manager should know

Little's Law is one of those rare mathematical results that is both rigorously proved and genuinely useful in practice. It's a law in the formal sense — not a rule of thumb or a best practice — and it holds for any stable system, from a hospital ward to a semiconductor fab to a small assembly cell.

If you manage production, this formula will change how you think about WIP, lead time, and throughput.

The formula

In plain English: WIP = Throughput × Lead Time. Given any two of these three variables, you can calculate the third. That's the power of it — it makes an otherwise invisible relationship between WIP, speed, and time visible and quantifiable.

A worked example

A production cell processes 40 units per day. On average there are 120 units in process at any given time (waiting, being worked on, in transit between stations). What's the average lead time?

Now the manager implements a WIP cap — no more than 80 units in process at any time. Throughput stays at 40 units/day. What happens to lead time?

W = 80 ÷ 40 = 2 days. Lead time drops by a third — without changing a single process step, cycle time, or staffing level. Just by limiting WIP.

You don't need to make any process faster to reduce lead time. You just need less WIP in the system at any given time.

Why this matters practically

Most managers try to improve lead time by speeding up processes — reducing cycle times, adding operators, buying faster equipment. Little's Law reveals a cheaper lever: reduce WIP. The relationship is direct and proportional. Half the WIP, half the lead time, at the same throughput rate.

This is why lean manufacturing puts so much emphasis on WIP reduction. It's not just about floor space or inventory cost — it's about lead time. And lead time is what the customer experiences.

The three forms of the law

You can rearrange Little's Law to solve for whichever variable you need:

The Little's Law calculator lets you solve for any of the three variables — enter two and it calculates the third, with a what-if scenario table showing how changes in each variable affect the result.

Little's Law and kanban

Kanban systems are essentially an implementation of Little's Law. Each kanban card represents one unit of WIP. When you set the number of kanban cards, you're setting a WIP cap — and by Little's Law, that cap directly determines lead time at a given throughput rate.

This is why kanban sizing isn't arbitrary. The number of cards = maximum WIP = maximum lead time ÷ cycle time. Get it wrong and you either starve the downstream process (too few cards) or allow lead time to balloon (too many).

It also connects to takt time. If your takt time is 2 minutes per unit and you want a maximum lead time of 4 hours (240 minutes), Little's Law tells you the maximum WIP should be 240 ÷ 2 = 120 units. That's the number of kanban cards you need.

Important constraints

Little's Law holds only for stable systems in steady state. This means:

• Average inflow must equal average outflow over the measurement period
• The system isn't in a ramp-up or ramp-down phase
• You're measuring averages, not instantaneous values

In practice, most production environments are close enough to steady state for Little's Law to give useful directional guidance. It's most reliable for planning and design decisions — less so for real-time operational decisions where variability matters more than averages.

Little's Law is one of the few analytical tools in operations management that is both mathematically exact and immediately actionable. Learn it, internalise it, and you'll see WIP, throughput, and lead time differently — not as three separate things to manage, but as three faces of the same constraint.