Learn & Understand

Little's Law: Why Doing Fewer Things Finishes Them Faster

The task completion estimator divides remaining work by your velocity to project a finish date, borrowing agile's burn-rate logic. Underneath that division lies one of the most useful and least intuitive results in all of operations research, Little's law, which reveals something surprising: the amount of work you have started but not finished is a hidden dial that controls how fast anything gets done. Understanding it explains why a person or team drowning in half-done tasks feels slow even while working hard.

A Law About Queues

Little's law is a simple, ironclad relationship for any stable system where work arrives, waits, and leaves. It states that the average time an item spends in the system equals the average number of items in progress divided by the rate at which items are completed. In plain terms: how long something takes to finish depends not just on how fast you work, but on how many things are in flight at once. The more you have started, the longer each one waits in the queue behind the others.

Work in Progress Is the Villain

This exposes why velocity alone does not determine your finish date. Your completion rate can be respectable while individual tasks still crawl to the finish, because they are stuck behind a pile of other started-but-unfinished work. Every task you begin without finishing lengthens the effective queue for everything else. A desk with fifteen open tabs of half-done work is not fifteen times productive; it is one worker feeding a long internal queue.

The Counterintuitive Fix

Little's law implies a remedy that feels wrong: to finish things faster, start fewer of them. By deliberately limiting work in progress, refusing to open a new task until an existing one is done, you shrink the queue, and each remaining task flows to completion more quickly. This is the entire logic behind the "limit WIP" rule in modern workflow systems. Your velocity need not increase at all; simply carrying less unfinished work makes the finish line arrive sooner for whatever you are actually working on.

Reading Your Estimate Through This Lens

So when the calculator projects a completion time from your velocity, remember the assumption hiding inside it: that velocity was measured while you carried a certain load of unfinished work. Pile on more parallel tasks and your effective per-task finish time stretches even if the raw rate looks the same. The most reliable way to hit the projected date is often not to work faster but to keep fewer balls in the air, honoring the law that governs every queue.

To convert a per-day rate into that velocity figure, use the Daily Output Calculator; to track whether you are hitting the plan along the way, the Productivity Tracker.