Day 185 of the Daily · Operations

Little’s Law

5 min read · 3 principles · apply it by lunch

Morning. Three numbers describe every queue you’ve ever stood in, and you already hold two of them.

The question

How many pieces of work are sitting open in your business this morning — live deals, unbilled projects, unanswered tickets, orders not yet shipped — and how many new ones arrived in an average week? Divide the first by the second before you read any further.

The idea

John Little trained as a physicist at MIT and became one of the founding figures of operations research there. In 1961 he published a short paper in Operations Research under the flattest title in the literature: A Proof for the Queuing Formula: L = λW. The formula wasn’t new. What Little supplied was the proof, and the proof is what makes it usable, because it holds under conditions almost nothing else in queueing theory survives. The average amount of work in a system equals the average rate at which work arrives, multiplied by the average time each piece stays. It doesn’t care whether arrivals are steady or lumpy, whether you serve first-come-first-served or by whoever shouts loudest, or how many people are working the queue. It asks one thing only: that the system is roughly stable across the window you measure, meaning about as much came out as went in. Grant it that and you never have to measure all three numbers. Count what’s open, count what arrives, and the time a customer waits falls out of the arithmetic — no stopwatch, no survey, no argument about whose estimate is fairer.

In the Daily · 3 principles and a template

Little’s Law is Day 185 of 365.

In the Daily, each of its three principles is explained in full, with a one-page template to apply it the same day. A new framework arrives every morning at 7am for a year, across all fifteen courses of the FutureMBA curriculum.

$29 a month · cancel any time · 7-day money-back guarantee

More from Operations

The next four in the course.

All 24 Operations frameworks
Day 194 · Operations

The Value-Add Ratio

Take the last job you delivered and separate the hours somebody was genuinely working on it from the days it spent waiting on a desk, in an inbox, or behind something more urgent — which of those two numbers is bigger? The waiting. It always is.

See the framework →
Day 203 · Operations

The Service Blueprint

Think of the last complaint that reached you personally — the thing that arrived late, or wrong, or twice. Was the failure inside a step somebody owns, or in the handover between two people who’d each done their own part correctly? If it’s the handover, it belongs to nobody. Nothing in your business is currently pointed at it, and it will happen again this month.

See the framework →
Day 212 · Operations

The Seven Wastes

Take the busiest hour of your week — the floor, the inbox, the board, wherever the work actually happens. Of everything going on in it, how much would survive if the customer had to approve each item separately, knowing they were paying for it? You already know it isn’t most of it. The useful question is which of seven kinds the rest turns out to be.

See the framework →
Day 220 · Operations

Utilisation and Variability

Take your most loaded person or team — the one absorbing something like ninety per cent of everything they can handle. There’s a queue sitting in front of them right now. If you handed back a fifth of their capacity, how much of that queue would clear? Far more than a fifth. The relationship isn’t linear, and no amount of effort from them is going to make it so.

See the framework →