WIP Limits in Kanban: How to Set Them and Make Them Stick

Most kanban boards fail the same way: not from too little work, but from too much of it started at once. WIP limits— work-in-progress limits — are the kanban rule that caps how many cards a column can hold at a time. They feel restrictive the first week, and they're the single most effective change you can make to how fast work actually finishes. Here's what they are, the math behind why they work, how to pick your first number, and the mistakes that make teams abandon them.

What are WIP limits in kanban?

A WIP limit is a number attached to a column: “In Progress, max 4.” Once four cards sit there, nobody starts a fifth — instead, the team helps finish something already in flight. That's the whole rule. If you're new to the method itself, our primer on the kanban method covers the foundations; WIP limits are the part that turns a passive status board into a system that actively manages flow.

The counterintuitive bit is that limiting work in progress makes you finish more, not less. Every half-done card costs you context switching, stale details, waiting reviewers. Fewer open cards means each one moves faster — and the math backs this up.

Why Little's Law makes them work

This isn't a productivity vibe; it's queueing theory. Little's Law says that for any reasonably stable system:

average cycle time = average WIP / average throughput

Cycle time is how long a card takes from started to done. Throughput is how many cards you finish per week. WIP is how many are open at once. The law holds for supermarket queues, network routers and hospital wards alike — it doesn't care what kind of work is on your board.

Read it as a lever. If your team finishes 10 cards a week and keeps 20 open, the average card takes two weeks. Keep 5 open at the same throughput and it takes half a week. Nobody worked faster — the cards simply waited less.You can't decree higher throughput, but you can directly control WIP. Lower it and cycle time falls almost mechanically. That's the entire trick.

How to pick the number: team size + 1

Don't model it. Start with a simple heuristic: number of people who work in that column, plus one. Five developers pulling from “In Progress” means a limit of 6 — one card per person, plus a single slot of slack for the card that gets blocked or handed over. Then adjust based on what you observe over the next couple of weeks:

• The limit never binds?It's too high to change behavior. Lower it by one and watch again.
• People are idle with nothing to pull? Too low, or your columns are too fine-grained. Raise it by one.
• Cards pile up in “Review” instead? The bottleneck moved. Put a limit on that column too — limits work best on every column between backlog and done.

Change one number at a time and give each change a week or two. The goal isn't a perfect number; it's a number tight enough that the team regularly feels it.

What to do when a column turns red

A limit only earns its keep at the moment it's hit. When the column goes over and turns red, that's not an error to silence — it's the system telling you to change behavior right now:

1. Finish before you start. The default response: pick an in-flight card and help push it to done — review it, test it, unblock it. Two people finishing one card beats two cards half-open.
2. Hunt the blocker. Often the column is full because something is stuck waiting on a decision or another team. Make the dependency visible and chase it instead of starting fresh work around it.
3. If something truly urgent arrives, swap — don't stack. Pull the urgent card in and push a started card back. Painful, but honest. If everything feels urgent, the problem is upstream — see how to prioritize when everything is urgent.

Common mistakes with WIP limits

• Putting a limit on the backlog. The backlog is a queue of options, not work in progress. Capping it just hides demand. Limit the columns where work is actively happening.
• Ignoring the limit under pressure.“Just this once” is how limits die. Deadline crunch is precisely when starting less matters most — a limit you only respect on calm weeks is decoration.
• Setting it so high it never triggers.A limit of 15 for four people is a wish, not a policy. If the column never turns red, the number isn't doing anything.
• Treating it as a personal quota. WIP limits belong to the column, not to individuals. The point is team flow, not policing who has how many cards.

Doing this in Decknote

In Decknote you can set a WIP limit on any list (a Pro feature), and the supporting pieces are built in: card relations mark dependencies with a red Blocked badge right on the board, filters by assignee or label show whose work is clogging a column, and bulk actions let you move a batch of cards back to the backlog when you decide to swap instead of stack.

One honest pricing note: because Decknote's Pro planis $5/month flat per board owner — not per user — one subscription turns on WIP limits for every member of your boards. With per-seat tools, process features like this multiply by head count. There's a 14-day free trial, and the free plan already covers boards, checklists and filters if you want to practice the habit before enforcing the number.

Start with team size + 1, keep the limit visible, and treat every red column as a conversation. Two weeks in, check your cycle time — Little's Law will have done its part.

Create your free Decknote account and try all of this on your own board — no credit card required.