What is Little's Law?
Little's Law links the average number of items in a system (work‑in‑progress) to how fast items are completed (throughput) and how long they take (lead time): WIP = Throughput × Lead Time. It’s a simple, practical rule from queueing theory used to predict flow in processes.
Little’s Law is a mathematical relationship from queueing theory that says, on average, the number of items in a stable system equals the arrival/completion rate multiplied by the average time each item spends in the system. In plain terms: how many tasks you’ve got in progress (WIP) = how many you finish per unit time (throughput) × how long each task takes from start to finish (lead time). It assumes the system is in a steady state (rates measured over the same time window and averaged) and that you’re working with comparable tasks or using averages to smooth variability. Though it originated in manufacturing and service operations, it’s often applied to personal and knowledge work to reason about backlog, focus, and flow.
Usage example
If you finish an average of 4 tasks per day (throughput) and tasks typically spend 2 days from start to finish (lead time), Little’s Law predicts about 8 tasks will be active at any time (WIP = 4 × 2 = 8). If you deliberately limit WIP to 4 tasks while maintaining the same throughput, average lead time should fall to about 1 day (lead time = WIP / throughput = 4 / 4 = 1).
Practical application
Why it matters: Little’s Law gives you a simple, quantitative way to reason about focus and flow. For busy people and neurodivergent workers, it’s a reminder that trying to juggle more tasks raises your average time to completion and increases mental clutter. Practical uses include: setting WIP limits to reduce overwhelm, estimating how long a backlog will take to clear, measuring the impact of process changes (e.g., batch size or time blocking) on throughput and lead time, and spotting when incoming work exceeds capacity so you can triage or defer. It’s not a magic fix—task variability, interruptions, and human factors matter—but Little’s Law helps turn intuition into numbers so you can make targeted changes. Tools that track completions and active tasks can make those numbers visible and actionable, helping you keep WIP within a manageable range.
FAQ
Does Little’s Law work for individual knowledge workers or just factories?
It applies to any system with flow—manufacturing lines, call centers, or personal task lists—as long as you measure average throughput and lead time over a stable period. For individual knowledge work, variability in task size and interruptions means you should interpret results as useful approximations rather than exact predictions.
How do I measure throughput and lead time for my tasks?
Throughput = number of completed tasks divided by the time window (e.g., tasks per day or week). Lead time = average elapsed time from when you start a task to when you finish it. Use the same unit (days, hours, weeks) for both. Track a representative sample, smooth short-term spikes, and keep definitions consistent (what counts as a task or completion).
If I reduce WIP will everything finish faster?
Generally, yes—fewer concurrent tasks tend to reduce average lead time because you reduce context switching and queueing. But there are limits: extremely low WIP can leave capacity underused, and improvements may be constrained by bottlenecks or large, variable tasks. Combine WIP limits with efforts to reduce interruptions and break large work into smaller, uniform pieces.
What are common pitfalls when applying Little’s Law to personal productivity?
Common mistakes include using inconsistent time windows (mixing days and hours), comparing dissimilar tasks without normalizing for size, assuming steady state during chaotic periods, and ignoring human factors like motivation, priorities, and interruptions. Treat the law as a diagnostic tool, not a rigid rule.