Day 282 of the Daily · Operations

The Service Level

5 min read · 4 principles · apply it by lunch

Morning. Two prices decide this, and neither of them is the forecast.

The question

How much do you hold of the thing you can run out of — the stock, the spare seat, the standby shift — and could you say, in dollars, what one stockout costs you and what one unsold unit costs you? Until you can, that quantity is a matter of opinion, and the loudest opinion in the room is the one setting it.

The idea

Every argument about how much to hold is really an argument about a forecast, and a forecast is the one thing in the room nobody can settle. Kenneth Arrow, then a young economist at Stanford and later a Nobel laureate, moved the question somewhere it could be settled, in a 1951 Econometrica paper written with Theodore Harris and Jacob Marschak called Optimal Inventory Policy. The problem is older still: F. Y. Edgeworth had used probability to set a bank’s cash reserve as far back as 1888. Textbooks call it the newsvendor, after the seller who buys his papers before he knows how many he’ll sell, and the shape recurs everywhere. Commit too low and you pay the underage cost — the lost margin, the expedite fee, the customer who quietly goes elsewhere. Commit too high and you pay the overage cost — the write-down, the wage for the idle hour, the capital sitting still. The right service level is the first divided by the sum of both. If running out costs forty dollars and one too many costs five, the ratio is forty over forty-five, and you cover demand to the eighty-ninth percentile. The trap is treating this as a forecasting problem. It’s a pricing problem, and both prices are already yours.

In the Daily · 4 principles and a template

The Service Level is Day 282 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 291 · Operations

Pooling

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.

See the framework →
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 →