Kanban WIP Limits: The One Rule That Makes Teams Finish More
It sounds backwards: to get more done, start less. But that's exactly what work-in-progress (WIP) limits do. A WIP limit caps how many cards can sit in a column at the same time. When the column is full, nobody starts new work — they help finish what's already there. It's the most powerful and most ignored rule in kanban.
- A WIP limit is the maximum number of cards allowed in a column at once.
- Fewer tasks in progress means less context switching and shorter cycle times.
- A good starting point: two cards in progress per person, and a small limit on "In review".
- When a limit is hit, the rule is "stop starting, start finishing".
Why limiting work speeds things up
Imagine a person with five tasks in progress. Each task gets a fifth of their attention, every switch costs time to refocus, and all five finish late. With two tasks in progress, each finishes sooner — and the first one can be reviewed and delivered while the second is still underway.
The same holds for a team. When "In progress" is overloaded, work sits half-done. When "In review" is overloaded, finished work waits for someone to check it. WIP limits make those queues visible and force the team to clear them.
This relationship is described by Little's Law from queueing theory: for a stable system, average time in the system equals average work in progress divided by throughput. If you keep throughput the same and reduce work in progress, each item gets through faster.
How to set your first limits
| Column | Starting limit | Why |
|---|---|---|
| Assigned | No limit (or a soft one) | It's the queue of upcoming work |
| In progress | 2 × number of people | One main task plus one waiting on something |
| In review | Half the team size, minimum 2 | Reviews should happen quickly |
| Done | No limit | Archive regularly |
For a team of four: in progress ≤ 8, in review ≤ 2–3. Adjust after two weeks based on what you observe.
What to do when a limit is hit
When a column is full, the question changes from "what should I start?" to "what can I help finish?"
- Review someone else's card if "In review" is full.
- Unblock a stuck card — answer the question, get the file, call the client.
- Pair up on the oldest card in progress.
- Only if none of that is possible, raise it in the team chat — the limit might be too low, or the process has a real bottleneck.
Signs your limits are wrong
- Limits are never hit — they're too high to matter. Lower them.
- Limits are hit constantly and people ignore them — either the limit is unrealistic or the team isn't bought in. Discuss it in the weekly review.
- Cards bounce between columns to dodge the limit — the limit has become a game. Revisit why you have it.
WIP limits and time tracking
Tracking time per card makes the effect of WIP limits measurable. Compare the average actual time from "In progress" to "Done" before and after introducing limits. In our experience the tracked hours per task often stay similar, while calendar time shrinks — because less work sits waiting. In Teamflows, the timer on every card gives you the working time, and the activity log shows when cards moved.
Frequently asked questions
What is a WIP limit in kanban?
A WIP (work in progress) limit is the maximum number of cards allowed in a column at the same time. It prevents overload and keeps work flowing.
What's a good WIP limit for one person?
One to two tasks in progress. One is ideal for deep work; two gives room for a task that's waiting on someone else.
Do tools need to enforce WIP limits?
It helps but isn't necessary. A team agreement and a visible count per column are enough for small teams. Teamflows shows the number of cards in each column on the board.
Do WIP limits work outside software teams?
Yes. Agencies, marketing teams, operations and support all benefit, because the underlying problem — too much started, too little finished — is universal.
We build Teamflows — a free kanban board with a timer inside every task — and use it every day at the Digital Plus studio to run dozens of client projects. Our guides come from that practice. Questions or corrections: mail@dp8.kz