Day 248 of the Daily · Operations

The Level Schedule

5 min read · 4 principles · apply it by lunch

Good morning. Demand arrives in lumps. Nothing obliges you to pass them straight through.

The question

Look at what your team actually started in each of the last four weeks — not what was sold, what was released into the work — and how far apart are the biggest and the smallest of those weeks? If you don’t have the numbers to hand, the shape is almost certainly your order book’s, because that’s the default: whatever arrives gets released, and the swing gets paid for by everyone standing behind you.

The idea

On a Toyota line there’s a rack of pigeonholes on the wall — one column for each slice of the day, one row for each model, a card in every slot. Someone pulls the next card when the interval comes round, and that card, not the order book, decides what gets built. It’s called a heijunka box, and it’s the least glamorous instrument in the Toyota Production System and possibly the most load-bearing. Levelling means releasing work smoothed rather than in the shape the orders arrived: smoothed in volume, so roughly the same quantity goes in each day, and smoothed in mix, so a day’s output alternates between models in small repeating quantities instead of running one until lunchtime. It sounds like ignoring your customers and it’s very nearly the opposite — what gets smoothed is the release of work, never the promise made to the buyer, and the promise gets more reliable precisely because the operation stops lurching. The logic underneath it, which Yasuhiro Monden documented in detail, is that a peak passed straight through has to be paid for everywhere behind it: every station, every supplier and every shift roster ends up sized for the highest day it will ever see, then sits underused for the rest of the month. Absorb the peak once, at the point of release, and everything behind you gets to be steady.

In the Daily · 4 principles and a template

The Level Schedule is Day 248 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 257 · Operations

Batch Size and Changeover

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.

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