Day 300 of the Daily · Operations

The Bullwhip Effect

5 min read · 4 principles · apply it by lunch

Good morning. Your customers didn’t change their minds. The chain between you changed the story.

The question

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.

The idea

In 1997 Hau Lee, a Stanford operations professor, published a paper in Sloan Management Review with V. Padmanabhan and Seungjin Whang that analysed something Jay Forrester had modelled at MIT decades earlier in Industrial Dynamics (1961): demand variability grows at every step back up a supply chain. Their opening example was Procter & Gamble’s nappies — about as steady as consumer demand gets, since babies don’t buy in bursts — where orders arriving from distributors swung far more than shop sales did, and the orders the company placed on its own suppliers swung more again. P&G’s own executives had christened it the bullwhip. Nobody in the chain was behaving irrationally. Each tier forecasts from the orders it receives rather than from what anyone actually bought, adds a margin of safety on top, batches its purchasing to save on ordering, buys ahead when there’s a promotion, and inflates its order when supply looks tight. Every one of those is sensible locally. Stacked, they manufacture a swing no customer ever asked for, and the further you sit from the shelf the more of it you absorb as inventory, overtime and idle capacity. The tier that pays most for the swing is the one furthest from anyone who caused it.

In the Daily · 4 principles and a template

The Bullwhip Effect is Day 300 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 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 →
Day 336 · Operations

Standard Work

Take the process your business runs most often — the onboarding, the client handover, the monthly close — and ask whether two of your people, working it on the same day, would produce the same thing in the same order. If the honest answer is no, you haven’t got a process; you’ve got several, and you’re paying to run all of them.

See the framework →