Calculate throughput, work in progress, or cycle time with Little’s Law. Learn what the formula means, why it matters, and how to use the calculator.

If you have ever looked at a Kanban board cluttered with half-finished tasks and wondered why nothing seems to get done, the answer is often hiding in plain sight. The Little’s Law Calculator is a simple tool that exposes a uncomfortable truth: starting more work does not make you faster; it makes you slower.

Built on a mathematical theorem from queueing theory, this calculator translates three everyday Kanban metrics—Work in Progress (WIP), Cycle Time, and Throughput—into a clear picture of your system’s actual delivery capability. This article explains what the tool is, why it matters, how to use it, and the practical questions it answers.

What Is the Little’s Law Calculator?

The Little’s Law Calculator is a lightweight web-based tool that applies Little’s Law to knowledge work and manufacturing workflows. Little’s Law states that the average number of items in a system (WIP) equals the average rate at which items leave the system (Throughput) multiplied by the average time each item spends in the system (Cycle Time) .

In its most useful Kanban formulation, the law is rearranged as:

Average Cycle Time = Average WIP ÷ Average Throughput

The calculator you have built takes three inputs—Cycle Time per item, WIP Limit, and Resource Capacity—and computes the effective system throughput, effective cycle time, and the time required to clear current WIP. Crucially, it identifies the limiting factor: whether your process is constrained by the WIP limit you have set or by the raw capacity of your resources.

This distinction matters. A team that sets a WIP limit of 5 but only has the capacity to process 0.2 items per minute will find that capacity, not WIP, is the real bottleneck. The calculator makes that visible.

Why Does It Matter?

It Explains the Productivity Paradox

Most teams intuitively believe that starting more work earlier will lead to finishing more work sooner. Little’s Law proves the opposite. If throughput remains constant, doubling WIP doubles Cycle Time . The work does not move faster; it simply sits in the system longer.

This is not a metaphor. It is a mechanical relationship derived from queueing theory. As the Project Management Institute notes, “as the WIP limit goes above capacity, the throughput of the system will decline” . The calculator quantifies this trade-off.

It Shifts the Conversation from Estimates to Evidence

Traditional velocity-based planning relies on story point estimates that are subjective, team-specific, and notoriously gameable. Throughput—the count of items completed per unit time—is objective and factual . The Little’s Law Calculator produces a throughput figure that can be used for probabilistic forecasting, such as answering “how many items can we realistically deliver in the next four weeks?” with a data-informed range rather than a guess.

It Reveals Where the Real Constraint Lies

The calculator’s “limiting factor” output tells you whether you are WIP-constrained or capacity-constrained. These require completely different interventions. If you are WIP-constrained, you need to finish work before starting new work. If you are capacity-constrained, you need more resources or better tooling. Confusing the two leads to wasted effort—typically, adding people to a problem that is actually caused by too much work in flight.

How to Use the Calculator

The tool requires three inputs. Here is what each one means and how to provide a sensible value.

Cycle Time (minutes per item): This is the time it takes for one work item to move from the moment active work begins to the moment it is done . Measure this from your historical data, not from estimates. If your team typically completes a small feature in two days of active work, and you are working in minutes, that would be roughly 960 minutes (assuming an 8-hour workday). For most knowledge-work settings, it is easier to work in days or hours rather than minutes.

WIP Limit (items in progress): This is the maximum number of items your team allows into the active workflow at any one time. A practical starting point is team size plus a small buffer, then tighten over time as the team matures . If you do not currently have a WIP limit, use your current average WIP as a baseline.

Resource Capacity (items per minute): This represents the maximum throughput your resources can physically achieve if unconstrained by WIP. For a team of five developers each capable of completing one item per week, that would be five items per week, or approximately 0.017 items per minute (assuming a 40-hour week). The calculator uses this to determine whether your WIP limit or your capacity is the binding constraint.

Once you click “Calculate Throughput,” the tool displays the Little’s Law throughput, the resource-limited throughput, the effective system throughput (the minimum of the two), the effective cycle time, the time to clear current WIP, and the limiting factor.

Questions the Calculator Answers

“Why does our cycle time keep increasing even though we are working harder?”
The calculator will likely show that your WIP has grown beyond what your throughput can support. Little’s Law makes the relationship visible: more WIP, same throughput, longer cycle time .

“How long will it take to clear our current backlog?”
By dividing your current WIP by the effective throughput, the calculator provides an estimate of the time required to work through everything currently in progress. This is useful for setting realistic expectations with stakeholders.

“Should we focus on limiting WIP or adding capacity?”
The limiting factor output answers this directly. If Little’s Law throughput is lower than resource capacity, your WIP limit is the constraint—tighten it. If resource capacity is lower, you need more people, better tools, or smaller work items.

“What throughput can we realistically promise to the business?”
The effective throughput figure is a grounded, data-derived number that can replace optimistic estimates. It tells you what the system can actually deliver given its current configuration, not what you hope it will deliver.

“Is our Kanban system actually working?”
If you have set WIP limits but your average WIP consistently exceeds them, the system is not functioning as intended. The calculator’s emphasis on actual WIP versus WIP limit highlights this gap . A well-functioning Kanban system keeps actual WIP at or below the limit, and the calculator shows what throughput that configuration produces.

A Final Caveat

Little’s Law holds reliably only in a steady state—when arrival rate roughly equals departure rate over the measurement period. Software development is rarely perfectly steady. Use the calculator as a guide for understanding system behavior and setting policy, not as a deterministic prediction engine. Its greatest value is in making the relationship between WIP, throughput, and cycle time tangible, so that teams can make deliberate choices about how much work to start and when to finish it.

The calculator does not replace judgment. It informs it.