Kanban WIP limits: what they are and how to set them

By Equipo Onion 3 min read
In this article
  1. What counts as work in progress
  2. Why limit work in progress
  3. How to set your first WIP limit
  4. What to do when you hit the limit
  5. Common mistakes with WIP limits
  6. How to apply WIP limits in Onion

A WIP limit is the maximum number of tasks your team can have in progress at the same time. WIP stands for work in progress. It is one of the simplest rules in Kanban and one of the ones that changes a team's habits the most.

This article explains what work in progress is, why it pays to limit it, how to set a first limit and what to do when the team hits it.

What counts as work in progress

The Kanban Guide defines work in progress as the number of work items started but not finished. On a Kanban board, it is the total number of cards between the first active column and the done column.

The guide also asks teams to control this number explicitly: pull new work only when there is clear capacity, instead of starting everything that comes in.

Why limit work in progress

When a team has many open tasks at once, three things happen:

  • Each task takes longer to finish. Everyone's time is split across more tasks, so all of them move slowly.
  • Context switching goes up. Jumping between tasks means picking each one back up where it stopped, and that costs time.
  • Problems stay hidden. When a task gets stuck, the team starts another one instead of clearing the blocker.

This relationship has a well-known basis in Little's Law: at the same delivery rate, the more work in progress there is, the longer each task spends in the system. Reducing work in progress is the most direct way to get each task to done sooner.

How to set your first WIP limit

There is no single right number for every team. These steps give you a reasonable starting point.

  1. Count your current work in progress. Look at the board today and add up the cards in active columns.
  2. Compare it with your team size. If three people have twelve open tasks, each person is split across four things at once.
  3. Pick a slightly lower limit. One or two tasks per person is a good start. For a team of three, a total limit of four to six tasks usually works.
  4. Decide where to apply it. You can limit the whole board or each column. Column limits help you spot the stage where work piles up.
  5. Review the limit every few weeks. If the team never reaches it, lower it. If work is always waiting, find where tasks get stuck before raising it.

What to do when you hit the limit

Hitting the limit is a useful signal. It tells the team to finish something before starting something new. At that point, it helps to:

  • Help finish what is already open. If a task is waiting for review, a teammate can review it instead of starting something else.
  • Clear blockers. A card stuck for days deserves a team conversation.
  • Split large tasks. If a card has been in progress for weeks, it probably holds several tasks.

Common mistakes with WIP limits

  • Limits nobody follows. If the team ignores them, talk about why. Sometimes the limit is too low; other times urgent work has no clear rule.
  • Counting only one column. A task in review is still work in progress.
  • Changing the limit every day. Give it at least two or three weeks to show an effect.

How to apply WIP limits in Onion

Onion shows the number of cards in each column next to its name, so you see work in progress without counting by hand. To keep the limit visible, include it in the column name, for example "In progress (max 4)". The My tasks page gathers the in-progress cards from your boards, so you can tell at a glance whether you are opening more work than you can finish.

If you are building your board from scratch, read what a Kanban board is and how to design its columns first. When you are ready, create your free board at app.getonion.app.