Sample frameDay 266·Operations · Pull

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

Operations.

Pull and the WIP Limit

5 min read·Apply by lunch

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.

The framework

01
The count comes first.
You can't set a limit until you know the current number, and almost every team is shocked by it. Take one team, one board, one week, and list everything that has been started and not finished — including the items nobody would call work in progress: the reply half-written, the decision sitting with one person, the project paused before the summer that nobody has formally killed. Count them. Divide by the number of people. Four or five open items each isn't dedication; it's a queue with your team's name on it.
02
Set the limit low enough that it hurts.
A WIP limit only does its job when it binds. Start at roughly one and a half items per person, write the number where the work is visible, and hold it — because a limit that never blocks anyone isn't a limit, it's a description. Expect the first week to feel wrong: people will have spare hands and be forbidden to start. That is the system working as designed. Idle hands are cheap. Half-finished work is not, because it carries every hour already spent into next month without earning anything back.
03
What happens when someone can't start anything?
This is the moment the method earns its keep. Under a cap a blocked person can't reach for a fresh task, which leaves exactly one option — go and help finish something already in flight: review the draft, unblock the approval, chase the client sitting on the answer. That swarm isn't a workaround, it's the mechanism. A team without limits routes around its problems by starting more work, which hides them; a team with a limit has to route through them, which is roughly the only way they ever get fixed.
04
Finished has to mean finished, not handed on.
A pull system needs an honest definition of done, or the cap leaks. Work that has left your desk and sits unread in someone else's inbox has not left the system; it has only changed location, and if the board counts it as complete then your WIP number is fiction and your flow time won't move. Agree what completion means at each stage — accepted, published, paid, live — and count anything short of that as still open. A limit is only ever as good as the word sitting at the end of it.

Members only · 4 principles + template + AI mentor

364 more frameworks are waiting.

Pull and the WIP Limit is Day 1 of 365. One framework every morning for a year — across strategy, sales, negotiation, leadership, and more.

$1 /day

Billed $365/yr · cancel any time

365 frameworks

12 topics · templates · AI mentor

Reserve your place — $365/yr →

One payment a year · the whole library · no auto-renewal.

More Operations frameworks

All 24 operations frameworks →