A WIP limit controls how many work items can be active in a Kanban stage at one time. It keeps a column from filling with half-finished tasks and makes bottlenecks visible before they become normal. A useful first limit is small enough to expose waiting work, but realistic for the people doing it.
WIP means work in progress. The limit applies to active work, not to every card on the board. Backlog items can wait. Completed items can stay in Done. The limit concerns the part of the workflow where work is being started, built, reviewed, or finished.
What is a WIP limit in Kanban?
A WIP limit is a rule that caps the number of cards allowed in a column or group of columns. For example, a board might use:
Backlog | Doing (3) | Review (2) | Done
The number in parentheses is the limit. If three cards are already in Doing, the next item should not enter until one of those cards moves forward.
The purpose is not to keep everyone busy. The purpose is to improve flow. When fewer items are active, people spend less time switching between tasks, blocked work is easier to see, and finished work can reach the next stage sooner.
A WIP limit does not mean that work must stop forever when a column is full. It changes the next decision. Instead of starting something new, the team might finish an existing card, help with a blocked item, review a teammate's work, or clarify what is preventing progress.
Why do WIP limits matter?
Without a limit, the easiest response to a new request is often to start another card. The board grows, but completion does not necessarily improve. The team has more activity and less finished work.
A limit creates a visible constraint. When the limit is reached, the board shows that the system needs attention. This is useful information, not a failure state.
WIP limits help with several recurring problems:
- Too many tasks started at once
- Long review queues
- Frequent context switching
- Blocked cards hidden among active work
- Unclear priorities
- Work arriving faster than it can be completed
The limit also changes conversations. Instead of asking why somebody is not starting the next task, the team can ask what would help the current work move forward.
How do you choose a first WIP limit?
Start with a limit that is easy to explain and easy to observe. Do not try to calculate a perfect number before using the board.
For a solo board, a limit of one or two active cards is a reasonable experiment. If you work on several unrelated projects, you may need a slightly higher limit, but keep it low enough that unfinished work remains visible.
For a small team, begin with roughly one active card per person in the main Doing column. That is a starting point, not a universal formula. Pair work, specialist roles, and review capacity can change the right number.
For a Review column, use the capacity of the person or group doing the review. A review limit of two means the team should help clear those reviews before adding more work to the queue.
A first experiment can look like this:
Doing: 3
Review: 2
Run it for one or two weeks. Watch where cards wait, how often the limit is reached, and whether work is finishing more smoothly. Then adjust based on what the board shows.
Where should you put WIP limits?
The best place for a limit is usually a stage where work accumulates or where too much parallel work creates delays. Common candidates include:
The Doing column
This is the obvious starting point. Limiting active work discourages starting new cards before current cards are close to finished.
The Review column
A review queue can become a hidden bottleneck. Developers or writers keep producing work, while one reviewer receives more items than they can process. A Review limit makes that imbalance visible.
Testing or verification
Technical teams may limit cards waiting for tests, release checks, or approval. This helps the team prioritize clearing verification rather than adding more unverified work.
A shared workflow
Some teams use a limit across several columns. For example, Doing and Review together might have a limit of five. This can work when both stages use the same people or when the boundary between them is flexible.
Keep the first version simple. A limit on every column can turn a small board into a rulebook that nobody wants to maintain.
What should you do when a column reaches its limit?
When a column is full, do not move another card into it automatically. Check the work already there.
First, look for a card that is almost complete. Finishing it may be faster than starting something new. Next, look for blocked work. The best action may be to answer a question, fix an environment problem, or make a decision that is holding up the card.
Then check the next column. If Review is full, someone who normally starts work may be able to review or pair with the reviewer. If a card cannot move because the next stage is blocked, help clear that stage first.
Sometimes a card is too large. Split it into smaller pieces if the work can be delivered in useful increments. Do not split cards only to make the board appear less full. The smaller cards should still represent meaningful outcomes.
A full column is a prompt to improve flow. It is not a reason to quietly raise the limit.
How do WIP limits affect priorities?
A WIP limit makes priorities more honest. If every card is active, the board cannot show what matters most. A limit forces the team to decide which work deserves one of the available slots.
This is especially useful when requests arrive from different directions. New work can remain in the backlog until there is capacity. The team can then compare it with existing priorities instead of interrupting everything already in progress.
For a personal board, the same idea applies. A small Doing limit protects attention. It also makes it easier to explain why a new task is waiting: the available work slots are already occupied.
What are common WIP limit mistakes?
Setting the limit too high
A limit of ten may technically constrain a team, but it may not change behavior. If the board still looks like a task list, lower the limit until waiting work becomes visible.
Treating the limit as a quota
A limit is a ceiling, not a target. You do not need to keep exactly three cards in Doing. Empty capacity can be useful when the next work item is unclear or when finishing deserves attention.
Ignoring blocked work
A blocked card still counts as work in progress. Removing it from the count hides the problem and makes the system look healthier than it is.
Raising the limit whenever it hurts
Sometimes a limit reveals a real capacity problem. Raising it may feel like relief, but it often brings the same queue back later. First understand why work is waiting.
Using limits without changing behavior
A number on a column does not improve flow by itself. The team must use the signal to finish, review, unblock, or reprioritize work.
How should you review a WIP limit?
Review the limit after the board has collected enough real observations. Look at:
- How often the limit was reached
- How long cards waited in the column
- Whether the next stage became a bottleneck
- How often work was blocked
- Whether cards became smaller and easier to finish
If the limit is reached constantly and the next stage has capacity, the limit may be too low or the column may be too broad. If the limit is never reached, it may be too high or the workflow may not have enough active work to test it.
Change one limit at a time where possible. Otherwise, you will not know which change affected the flow.
Can a solo maker use WIP limits?
Yes. A solo maker can use a very small limit to protect focus. Try one card in Doing and one card in Review. When Review is full, review before starting another draft. When Doing is full, finish or unblock the current card.
You can start with a kanban board without registration and experiment with a simple limit before deciding whether you need more columns or a larger workflow. For a broader introduction, see what Kanban is. The Kanban guide from Atlassian also explains the relationship between WIP limits and flow.
Frequently asked questions
What does WIP stand for in Kanban?
WIP stands for work in progress. It refers to tasks that have started but are not finished. A WIP limit controls how many such tasks can occupy a workflow stage at the same time. Backlog and completed items normally do not count toward the active-work limit.
What is a good WIP limit for a team of five?
There is no fixed answer, but a small team can begin with about one active card per person in the main Doing stage. Review capacity may require a separate, lower limit. Run the experiment for a week or two and adjust based on waiting time and blocked work.
Should blocked cards count toward WIP?
Yes. A blocked card is still active work and should count toward the limit. Excluding it hides a constraint that the team needs to address. Keeping blocked cards visible encourages the team to remove the blocker or decide whether the item still deserves attention.
Can WIP limits be used on a personal Kanban board?
Yes. Personal Kanban often benefits from a small Doing limit because it reduces context switching. Start with one or two active cards, then observe whether the limit helps you finish work. A limit should protect attention, not create guilt when capacity changes.
What happens when a WIP limit is reached?
Do not start another card automatically. Finish or unblock existing work, review a waiting item, split an oversized card, or clarify priorities. The full column is a signal about flow. It tells you where attention may help the system move again.
Related reading
- Kanban for developers: sprint planning, bug triage, and releases
- The no-bloat Kanban workflow for small teams
- Personal Kanban for goals, habits, and daily focus
- A simple Kanban system to reduce overwhelm
WIP limits work best as small experiments. Start with one visible constraint, watch where work waits, and change the system based on what the board reveals.