Explain Little's Law and its application in Kanban

What's really being asked

Your ability to move beyond simple definitions. The interviewer wants to see if you understand that Little's Law is a tool for reasoning about system design and trade-offs in software delivery. It's not about memorizing a formula; it's about applying queueing theory to make a Kanban system more predictable. They are testing your understanding of flow metrics (WIP, Throughput, Lead Time) as levers you can pull to achieve a desired outcome, like faster or more reliable delivery.

The full answer

A strong answer has three parts. First, define Little's Law: Average Lead Time equals Average Work In Progress (WIP) divided by Average Throughput. Second, explain the practical trade-offs. For example, if you increase WIP without increasing throughput, lead time will inevitably go up. Conversely, to decrease lead time with a constant WIP, you must increase throughput. Third, describe a practical application, such as using the formula to set an appropriate WIP limit. If your team's throughput is 10 items per week and you want to achieve an average lead time of 1 week, your WIP limit should be around 10 items.

The mistakes people make

A major red flag is treating the law as an absolute truth without mentioning its key assumption: it only holds for stable systems. A stable system is one where the arrival rate of work roughly matches the completion rate. Candidates who ignore this nuance show a theoretical-only understanding. Another mistake is suggesting that the easiest way to improve throughput is to add more work (increase WIP). Little's Law shows this is counterproductive and will actually increase lead times, making the system less predictable.

What usually comes next

Expect questions like, "What do you do if your system isn't stable? How do you get it there?" or "How would you start collecting the data for these metrics on a team that doesn't track them?" Another common follow-up is, "Your team's lead time is too high. Using Little's Law, what are the two levers you can pull, and what are the pros and cons of each?"

A concrete example

Imagine a team has an average of 12 items in progress (WIP) and completes an average of 6 items per week (throughput). Using Little's Law, their average lead time is 12 / 6 = 2 weeks. If stakeholders want a 1-week lead time, the team has two options. They can either double their throughput to 12 items/week (which is often hard), or they can reduce their WIP to 6 items while maintaining the same throughput (6 WIP / 6 throughput = 1 week lead time). This shows how setting a WIP limit is a direct way to manage lead time.