Little's Law is an equation that links three variables in any system: items, arrival rate, and cycle time. Learn how the formula works and how to apply it.
![[Featured image]: Employees working on a line in a warehouse use Little's Law to calculate how many boxes they must move per hour.](https://d3njjcbhbojbot.cloudfront.net/api/utilities/v1/imageproxy/https://images.ctfassets.net/wp1lcwdav1p1/3NARFAk6AZKgWXT8zsGAEm/c92c934e5c862643502afec18f72b162/GettyImages-1460478775-converted-from-jpg.webp?w=1500&h=680&q=60&fit=fill&f=faces&fm=jpg&fl=progressive&auto=format%2Ccompress&dpr=1&w=1000)
Little's Law is an equation you can use to identify how much work is accumulating in a system.
Little's Law links three variables: the number of items in a system, the rate at which they arrive, and the time they spend in it.
Kanban and Agile teams use Little's Law to set work-in-progress limits and predict delivery times.
You can apply Little's Law to your own work by counting tasks in progress and estimating how long each one typically takes.
If you're ready to start building workflow management and systems thinking skills, enroll in the Google Project Management Professional Certificate. You'll have the opportunity to learn Agile methodologies, Kanban frameworks, and practical tools for managing workflows. In as little as six months, you can earn a career certificate with completed hands-on projects that demonstrate your skills to employers.
Little's Law is a theorem you can use to figure out how many items or people are sitting in a stable system at a given moment. For example, a busy urgent care clinic might have 20 patients in the building at one time. A new patient walks in the door every 15 minutes, and each one spends about five hours in the building, from check-in to discharge. Those three numbers are linked, and changing one of them changes the others.
The theorem gets its name from MIT professor John Little, who developed the concept in 1954. In his 1961 proof, Little demonstrated that the relationship is true in almost every queuing scenario [1]. The math works regardless of how complex the system is.
Little built the law around a single equation: L = λ x W. In this equation, L is the number of items (or work) in a system. Lambda (λ) indicates how fast new items enter the system. W refers to how long it takes each item to move through the system.
Using the clinic example, imagine the staff members start taking lunch breaks, and the average length of time patients spend in the clinic goes up to six hours. Plug the new numbers into the formula:
L = 4 x 6
L = 24
Now the clinic has 24 patients in the building instead of 20. If the arrival rate slows to three per hour, the workload falls to 18, reducing pressure on staff.
Little's Law says that at any point in time, the amount of work in a system equals its arrival rate multiplied by the time each item spends moving through it.
In Kanban, one of the core rules is limiting the number of tasks in progress at any given time. Little's Law is the math behind the rule.
Say a software development team resolves 20 bugs per week and has 60 bugs actively being worked on. That means each bug takes an average of three weeks to fix. To cut that to one week, the team doesn't necessarily need to work faster. It could reduce the number of active bugs to 20 at a time.
Agile teams apply similar logic during sprint planning. A team that completes 15 tasks per week commits to 30 tasks for a two-week sprint. Little's Law predicts each task will take an average of two weeks to complete. This means everything finishes at the last possible moment with no buffer for delays. With a commitment of 20 tasks, the average cycle time drops to about 10 days.
In both cases, Little's Law shifts the conversation from effort to system design. Instead of asking the team to work harder, managers can adjust the structure of the work itself and predict the outcome before making any changes.
Learn more: Kanban vs. Scrum: What's the Difference?
Little's Law shows you the consequences of change in a system. Say your team completes 10 tasks per week and each task takes about two weeks from start to finish. That means you have about 20 tasks in progress at any given time (L = 10 x 2).
If leadership wants to cut that number in half, you have two options: finish tasks faster or take on fewer. Reduce your average cycle time to one week, and the work-in-progress (WIP) drops to 10. Take on five tasks per week instead of 10, and you get the same result.
Little's Law is a useful tool for planning and diagnostics. You can model the effect of a higher arrival rate, a staffing change, or a new WIP limit without touching your actual system first.
Professionals across a wide range of roles, from a coffee shop manager tracking the morning rush to a factory supervisor coordinating hundreds of production steps, can apply Little's Law. If your work involves managing the flow of tasks, people, or products through a system, it's likely relevant to what you do. Common applications include:
Project managers: Use Little's Law to manage workload, set WIP limits, and predict delivery times.
Operations managers: Apply it to optimize production lines, identify bottlenecks, and plan capacity.
Software developers: Use it within Agile and Kanban frameworks to manage backlogs and improve delivery predictability.
Health care administrators: Apply it to analyze patient flow, reduce wait times, and make staffing decisions.
Supply chain managers: Use it to understand inventory levels and improve order fulfillment times.
What sets Little's Law apart from other analytical tools is how much it can tell you with just three numbers. Usually, two of them are easy to find, and that simplicity is what has made it a lasting tool across so many fields.
Simplicity: Little's Law works with three variables and one equation. As long as you can count items and track time, you can apply it without specialized software or advanced math.
Versatility: The same formula applies whether you're managing a hospital emergency room or a production line. If an emergency room sees 10 patients per hour and each patient spends an average of three hours in the department, Little's Law predicts 30 are in the system. This is the same math a factory uses to calculate WIP.
Predictive power: Little's Law lets you model the effect of a change before you make it. If your emergency room wants to reduce average patient time from five hours to four, you can calculate exactly how that affects the number of patients in the building.
Flexibility: Statistical models often assume you know whether items enter your system in clusters or on a schedule. Little's Law works regardless. The relationship between the workload, arrival rate, and cycle time holds no matter how the system behaves.
In a 2008 MIT analysis, researchers used Little's Law to evaluate traffic flow through the Ted Williams Tunnel in Boston. They calculated how long each driver waited at the toll booths and how many toll booths they needed to open to keep traffic moving [2].
A study published in 2014 applied the same math to a McDonald's restaurant in Kuala Lumpur. On a day when the restaurant handed out limited-edition toys, the average queue jumped from seven customers to nearly 18. Little's Law identified the cause: a slow kitchen, not the number of customers [3].
Start with a system you already know well. If you count tasks, monitor timelines, or measure output in any form, you already have the data you need. Little's Law gives that information a new purpose.
If you manage a team, look at your current task list. Count how many items are in progress and estimate how long each one typically takes to complete. Those two numbers give you L and W. From there, you can calculate your arrival rate or use the formula to ask "what if" questions about your workload.
If you work in a service environment, the same approach applies. A typical week of customer support tickets, a month of patient appointments, a production line, or a similar stable system with measurable inputs and outputs works with Little's Law.
Start small, with one queue you understand, and let the numbers tell you something you didn't already know.
If you're interested in expert guidance and no-fluff tips to help you build your skills, subscribe to our YouTube channel. You can also explore free career resources to learn new topics, explore emerging industries, and discover new opportunities.
Bookmark this page: Project Management Terms & Definitions
Read this article: Kanban vs. Scrum: What they are + when to use them
Hear from an expert: The Ultimate Course on Problem-Solving: Professor Sriram Sankaranarayanan Talks Algorithms
With Coursera Plus, you can learn and earn credentials at your own pace from over 350 leading companies and universities. With a monthly or annual subscription, you’ll gain access to over 10,000 programs—just check the course page to confirm your selection is included.
Corporate Finance Institute. "Little's Law, https://corporatefinanceinstitute.com/resources/data-science/littles-law/." Accessed March 19, 2026.
University of California San Diego. "Chapter 5: Little's Law, http://web.eng.ucsd.edu/~massimo/ECE158A/Handouts_files/Little.pdf/." Accessed March 19, 2026.
ResearchGate. "Improving Queuing Service at McDonald's, https://www.researchgate.net/publication/278099553_Improving_Queuing_Service_at_McDonald's/." Accessed March 19, 2026.
Editorial Team
Coursera’s editorial team is comprised of highly experienced professional editors, writers, and fact...
This content has been made available for informational purposes only. Learners are advised to conduct additional research to ensure that courses and other credentials pursued meet their personal, professional, and financial goals.