Little's Law is a foundational relationship in operations management stating that the average number of items in a process (work in progress, or WIP) equals the average rate at which items exit the process (throughput) multiplied by the average time each item spends inside it (lead time). Written as an equation, it is WIP = Throughput x Lead Time, and rearranged it becomes Lead Time = WIP / Throughput. For a factory floor, that single formula explains why a line clogged with half-finished parts takes longer to deliver orders, and why cutting inventory on the floor almost always shortens delivery time.
Little's Law only works if you define its three variables consistently, using the same items and the same time units across the board.
The law holds for any stable system over a long enough window, regardless of the order in which jobs are processed, the variability of arrivals, or the number of machines. That generality is what makes it so useful.
Imagine a mid-sized assembly cell. At any given moment there are, on average, 120 units of work in progress on the floor. The cell completes 30 units per hour. How long does an average unit take to travel from start to finish?
Apply the rearranged formula:
So the average part sits in the system for 4 hours, even if the actual hands-on work is only 30 minutes. The other 3.5 hours are queueing, a direct symptom of excess WIP. Now suppose a continuous-improvement team halves the floor inventory to 60 units while keeping throughput at 30 units per hour. The new lead time is 60 / 30 = 2 hours. Same output rate, half the delivery time, purely by draining the queue.
The example above is not a coincidence. Because lead time equals WIP divided by throughput, if throughput stays constant then lead time is directly proportional to WIP. Halve the WIP and you halve the lead time. This is the mathematical backbone behind the lean instinct to reduce inventory on the floor.
Excess WIP is one of the classic seven wastes. It hides quality problems, ties up cash, and lengthens the feedback loop between a defect being made and being caught. Every extra part waiting in a queue adds time to every part behind it. Shrinking WIP does not just cut cost, it makes the whole line more responsive.
Little's Law is the reason pull-based production works. In a push system, work is released whenever an upstream station is free, so WIP piles up wherever the line is slowest. In a Kanban-driven pull system, a fixed number of cards caps the WIP allowed in each zone. Because WIP is capped, lead time is capped too, and it becomes predictable rather than drifting upward whenever demand spikes.
This is why teams set explicit WIP limits: they are effectively setting a target lead time. If you know your throughput and you want a two-hour lead time, Little's Law tells you exactly how much WIP to allow. Combined with total productive maintenance to keep the bottleneck running, capping WIP produces the smooth, steady flow that lean manufacturing is built around.
The law is powerful precisely because it is simple, but that simplicity has limits. It gives you averages, not distributions, so it will not tell you the worst-case lead time or how much variability to expect. It assumes the system is stable, meaning arrivals and departures balance over the measurement window; a line that is filling up faster than it empties violates that assumption. And it does not explain why throughput is what it is. To raise the completion rate you still need to attack constraints, reduce unplanned downtime, and improve overall equipment effectiveness. Little's Law tells you the shape of the relationship, not the levers to pull.
The formula is only as trustworthy as the numbers you feed it, and the hardest of the three to measure honestly is WIP. Counting parts on the floor at one moment is a snapshot, not an average, and manual counts drift out of date within a shift. Throughput and lead time also need real, timestamped production events rather than estimates.
This is where a real-time monitoring foundation matters. Fabrico continuously tracks production events so throughput and WIP are measured, not guessed. Its real-time OEE and production monitoring captures completion counts as they happen, including through camera and computer-vision monitoring on machines that have no PLC to read from. When those live numbers feed Little's Law, your calculated lead time reflects the floor as it actually is, so you can act on it with confidence.
To use Little's Law as an everyday tool, follow a short loop:
Repeat as demand and product mix change. The law will keep pointing you toward the same conclusion: less clutter on the floor, faster delivery to the customer.
Yes. Little's Law holds for any process boundary you choose, whether that is a single machine, a full cell, or an entire plant. You simply measure WIP, throughput, and lead time for the whole system inside that boundary. It also applies to each sub-step, which is why you can nest it: the sum of the sub-step lead times equals the overall lead time when the boundaries line up.
Little's Law describes averages over a stable window, so short-term swings are fine as long as the system is not permanently filling up or emptying out. If throughput shifts to a new steady level, recompute using the new average. When throughput is genuinely erratic, pair the law with tools like statistical process control to understand the variation before you trust a single average number.
Reducing WIP shortens lead time, but cutting it too far can starve a bottleneck and lower throughput, which would raise lead time again. The goal is the smallest WIP that keeps your constraint fully fed. Find that level experimentally, protect the bottleneck with strong maintenance and proactive maintenance practices, then hold the line there.
Ready to base your WIP, throughput, and lead-time decisions on live shop-floor data instead of stale counts? Book a Fabrico demo and see how real-time OEE and computer-vision monitoring turn Little's Law from a whiteboard formula into a daily operating tool.
Zaloguj
Blog