Day 291 of the Daily · Operations

Pooling

5 min read · 4 principles · apply it by lunch

Keeping things separate has a price. Almost nobody has ever calculated it.

The question

Count the places you hold the same thing separately — stock split across three sites, cover split across four teams, a queue forming in front of each person rather than in front of all of them — and ask what it costs to keep them apart. Nobody invoices you for that number. Which is exactly why it has survived every budget you’ve ever run.

The idea

Every queue that feeds several counters at once — the bank, the airport, the passport hall — is a piece of arithmetic made physical, and it’s the same arithmetic that sets how much stock you hold. Pool a set of uncertain demands and the average adds in full, but the variability adds far more slowly, because it’s the variances that add rather than the swings themselves. So the cushion you need per unit of demand shrinks as the pool grows. Gary Eppen, a professor at the University of Chicago’s business school, put a number on that in Management Science in 1979, in a paper with a title nobody quotes and a result everybody uses: Effects of Centralization on Expected Costs in a Multi-Location Newsboy Problem. Take a set of locations, each holding its own buffer against its own uncertain demand, and merge them into one. Where those demands are of equal size and genuinely independent, the expected cost of holding and running short falls by a factor of the square root of the number of locations. Four depots become one and the buffer cost halves. Nine become one and it falls to a third. The size of the prize isn’t set by how big your buffers are. It’s set by how many separate piles you’re keeping them in.

In the Daily · 4 principles and a template

Pooling is Day 291 of 365.

In the Daily, each of its four 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 300 · Operations

The Bullwhip Effect

When your orders to a supplier last swung hard — the panic buy, the sudden pause, the month you took twelve weeks of cover — how much had really changed in the demand underneath, and how much of that swing did you manufacture on the way? Most of it. That has been the answer for almost everyone who went back and checked.

See the framework →
Day 310 · Operations

Common Cause, Special Cause

The last time a weekly number moved the wrong way, did anyone check whether that figure had ever sat outside its ordinary range before you changed something — or did you adjust, watch the next week land back where it always lands, and quietly credit the change you’d made?

See the framework →
Day 318 · Operations

The Cause Map

When something last went wrong badly enough to need a written explanation — the missed shipment, the wrong invoice, the error a client found before you did — how many candidate causes were on the table before the room settled on one, and how many questions deep did the settled one go? If the honest answers are one and three, you didn’t investigate. You confirmed the first idea that fitted.

See the framework →
Day 327 · Operations

Poka-Yoke

When the same small mistake turned up for the third time — the blank field, the wrong file attached, the discount applied to the wrong line — did you change the step so it couldn’t happen again, or send a message asking everyone to take more care? The message has already worn off.

See the framework →