Explain Little's Law and its practical application in Kanban

WHAT THIS TESTS: This question probes whether you understand Little's Law as an operational tool rather than just a textbook formula. The interviewer wants to see if you can connect queueing theory to team-level decisions in Kanban, specifically how WIP limits, throughput, and lead time interact in a real delivery system. They are looking for systems thinking and the ability to reason about stability, flow optimization, and predictable delivery without resorting to gut feel.

A GOOD ANSWER COVERS: First, state the formula clearly as Lead Time equals Work In Progress divided by Throughput. Second, explain the three levers: if WIP rises while throughput stays flat, lead time must increase; if you reduce WIP while holding throughput steady, lead time drops; if you raise throughput without increasing WIP, lead time also drops. Third, stress the stability assumption: the law applies when arrival rates match completion rates and the system is not chronically overloaded or firefighting. Fourth, connect this to Kanban practice by mentioning WIP limits as the control knob and throughput measurement as the feedback loop. Fifth, note that optimizing flow by removing blockers and dependencies is the sustainable way to improve throughput, not by pushing more work into the system.

COMMON WRONG ANSWERS: Claiming that adding more WIP will increase throughput without consequence is the biggest red flag because it violates the formula and leads to queue bloat. Another mistake is reciting the formula without mentioning the stability prerequisite, which makes the answer sound theoretical. Some candidates also conflate throughput with utilization or assume that multitasking improves flow, both of which reveal a shallow understanding of queueing dynamics. Finally, ignoring the role of WIP limits entirely and talking only about working harder shows you miss the systems-design aspect of Kanban.

LIKELY FOLLOW-UPS: The interviewer may ask how you would calculate a WIP limit given a target lead time and measured throughput, which is simply WIP equals Lead Time multiplied by Throughput. They might also ask what to do when the system is unstable, where you should discuss stabilizing arrival rates before using the formula. Another angle is asking how Little's Law applies at scale across multiple teams or whether it works for knowledge work with high variability in task size.

ONE CONCRETE EXAMPLE: Suppose a software team completes ten features per week and wants to maintain a one-week average lead time. Little's Law says WIP should stay at roughly ten items. If the business pushes fifteen items into the system, lead time inflates to one and a half weeks unless the team somehow raises throughput to fifteen per week. Instead of overloading the team, you would set a WIP limit near ten, focus on unblocking work in progress, and measure whether throughput improves before adjusting expectations.

Source: Agileseekers Limited (agileseekers.com)