Day 266 of the Daily · Operations

Pull and the WIP Limit

5 min read · 4 principles · apply it by lunch

Nothing on your team’s list is stuck. Everything on it is started — and that’s the same problem.

The question

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.

The idea

The card travels backwards. That is the whole inversion. In a pull system no step produces because it can; each step produces only what the step after it has just taken, and the signal that it was taken is a card — a kanban — moving upstream while the work moves down. The same Ohno who sorted waste into seven kinds took the image from an American supermarket: the shelf gets refilled by what customers removed, not by what the warehouse felt like sending. What makes that more than a metaphor is that the cards are finite. Print forty and forty is the most that can ever be in progress, because nothing starts without one — so the cap isn’t a target anyone has to remember or a rule anyone has to police, it’s built into the stock of cards. And the arithmetic from the Little’s Law morning says what that cap buys: cut the work sitting in the system and the wait falls with it, without anyone working faster or anything new being bought. The hardest instruction here is also the shortest. When something finishes, start something. When nothing finishes, start nothing.

In the Daily · 4 principles and a template

Pull and the WIP Limit is Day 266 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 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 →
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 →