Definition
Little's Law
Little's Law is a foundational result from queueing theory stating that, on average, the number of items in a system equals the rate items arrive (or complete) multiplied by the average time each spends in the system. For teams: average work in progress equals throughput times cycle time — which is why limiting WIP directly shortens cycle time.
Key takeaways
- Little's Law is a foundational result from queueing theory stating that, on average, the number of items in a system equals the rate items arrive (or complete) multiplied by the average time each spends in the system. For teams: average work in progress equals throughput times cycle time — which is why limiting WIP directly shortens cycle time.
- Stated for product teams, Little's Law reads: WIP = throughput × cycle time.
- The law also keeps forecasting honest.
Stated for product teams, Little's Law reads: WIP = throughput × cycle time. The average amount of work in progress equals how fast work completes multiplied by how long each item takes to get through. It holds over the long run for any stable system regardless of the details — it does not care how work is prioritized or who does it — which is what makes it such a reliable lens on flow.
Rearranged, the law becomes a lever. Cycle time = WIP ÷ throughput. If a team's completion rate is roughly fixed by its capacity, then the most direct way to shorten how long each item takes is to reduce how much is in progress at once. This is the mathematical justification for WIP limits: less concurrent work means faster individual cycle times, even though it feels counterintuitive to start fewer things in order to finish sooner.
The law also keeps forecasting honest. If WIP keeps growing while throughput stays flat, cycle times must be lengthening — the backlog of in-flight work is quietly stretching delivery. Spotting that relationship early, often via a cumulative flow diagram, lets a team intervene by capping WIP before lead times balloon.
Related terms
- Cycle TimeCycle time is how long an issue takes from the moment work actively starts on it to the moment it is done. Measured in hours or days, it captures the team's hands-on flow efficiency. Shorter, more consistent cycle times mean a more predictable system — the core flow metric Kanban teams optimize.
- ThroughputThroughput is the number of work items a team completes in a given period — issues finished per week, for example. It is the simplest flow metric: a direct count of output over time. Tracked across periods, throughput reveals a team's real delivery capacity and is the basis for probabilistic, estimate-free forecasting.
- WIP LimitA WIP (work-in-progress) limit is a cap on how many items may be active in a given workflow stage at once. By forcing a team to finish work before starting more, WIP limits expose bottlenecks, reduce context-switching, and shorten cycle time. They are the core mechanism that makes Kanban flow rather than pile up.
- Cumulative Flow DiagramA cumulative flow diagram (CFD) is a stacked area chart showing how many items sit in each workflow state over time. The colored bands reveal flow health at a glance: a widening band means work is piling up in that stage, a steady set of parallel bands means smooth flow. It is Kanban's richest single picture of a system's behavior.