Day 257 of the Daily · Operations

Batch Size and Changeover

5 min read · 4 principles · apply it by lunch

Morning. Nobody sat down and chose your batch sizes. Your setup times chose them.

The question

Pick the thing your operation does in batches — the Thursday invoice run, the fortnightly release, the print run, the monthly board pack — and ask why it’s that size rather than half of it: can you give a reason that isn’t simply that switching over is a nuisance nobody wants to do twice? If not, you’ve been paying for that nuisance in flow time every week since, and never once priced it.

The idea

Ford Whitman Harris was a production engineer who had spent eight years at Westinghouse when he published How Many Parts to Make at Once in Factory: The Magazine of Management in 1913 — three pages that gave the world the economic order quantity. His formula balances the cost of setting up against the cost of holding what you’ve made, and it carries a consequence people rarely follow through: the economic batch moves with the square root of the setup cost. Halve the changeover and the batch falls by about twenty-nine per cent. Quarter it and the batch halves. So batch size isn’t a scheduling decision at all; it’s a setup decision wearing a scheduling decision’s clothes. Shigeo Shingo, the Japanese industrial engineer who began consulting to Toyota in the 1950s, is the one who took that seriously. Asked in 1969 to fix a thousand-ton press whose changeover ran to four hours, he got it — by his own account, and in under a year — down to three minutes. He published the method as SMED, single-minute exchange of die, in A Revolution in Manufacturing, which reached English in 1985. Which is why the schedule meeting is the wrong meeting. Teams spend years negotiating run lengths and release windows, defending a batch size that a few days spent on the changeover would have made indefensible.

In the Daily · 4 principles and a template

Batch Size and Changeover is Day 257 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 266 · Operations

Pull and the WIP Limit

Count the pieces of work your team has open right now — the half-drafted, the in-review, the waiting-on-a-client, the one you’d have to check the board to remember — then count the people, and ask whether the first number is more than double the second. If it is, you already know why everything takes so long. The queue isn’t in front of your team; it’s inside it.

See the framework →
Day 273 · Operations

The Buffer Choice

When demand for your business spikes next month — the week everyone calls at once, the order that lands at three times the usual size — which of the three absorbs it: stock you’re already holding, capacity you’ve deliberately left idle, or your customer’s patience? For most businesses it’s the third, and nobody chose it; it simply happened, and the customer paid the bill.

See the framework →
Day 282 · Operations

The Service Level

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.

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