Kanban WIP limits are a simple rule that caps how many tasks can sit in each stage of your workflow at once. When a column is full, nobody starts anything new in it until something moves on. It sounds restrictive, but for small teams juggling client work, admin and sales, it is one of the most reliable ways to finish more and start less. This guide explains how kanban WIP limits work, how to set them for a small business, and what to do when the limit pinches.

Who this guide is for

This guide is for small business owners, founders and team leads who already track work on a board, whether that is a whiteboard, Trello, Asana, Jira or a spreadsheet, and still feel that everything is “in progress” and nothing is getting done. You do not need to adopt a full agile method to use WIP limits; they work on almost any board.

The basics: what a kanban board is

Atlassian’s guide to kanban boards describes a kanban board as a visual tool built on two principles: making work visible and limiting work in progress. A board usually has:

• Cards, each representing one piece of work.
• Columns, each representing a stage. The simplest board runs from To Do to In Progress to Done.
• WIP limits, the maximum number of cards allowed in a column at one time.
• A commitment point, where the team picks up work from the backlog, and a delivery point, where the work is finished.

Atlassian notes that the time between the commitment point and the delivery point is called lead time. That is the number customers and clients actually feel.

What kanban WIP limits actually do

Atlassian’s guide to WIP limits explains that they set the maximum amount of work that can exist in each status of a workflow, so inefficiencies become visible before they turn into a crisis. In practice, a limit does three things for a small team:

• It exposes bottlenecks. When the “Waiting for client feedback” column hits its limit, the problem is obvious to everyone, not hidden in one person’s inbox.
• It reduces context switching. People finish what they started instead of opening a fifth task because the fourth got awkward.
• It shortens delivery. Work that is started and finished in a steady flow reaches the customer sooner than work that waits in a pile.

How to set kanban WIP limits for a small team

There is no universal number. Atlassian recommends starting from what actually happens: watch how many cards typically sit in each column for a while, then set limits based on that.

1. Map your real stages. List the steps work actually goes through, for example: Backlog, Doing, Review, Waiting on client, Done. Keep it to the stages where work can get stuck.
2. Count for two weeks. Note how many cards sit in each column each day. This is your baseline.
3. Set limits slightly below the baseline. The point is to feel a little pressure, not to change nothing.
4. Set “Doing” below headcount. Atlassian suggests teams often set the in-progress limit below the number of people, leaving room to review and help each other rather than everyone working on their own card.
5. Skip limits on Done. Atlassian points out that nothing is left to do there. Keep the To Do column sized to just enough work to pull from.
6. Write the limit on the column. Most tools let you add it to the column header, so everyone can see it.

A worked example: a three-person studio

Picture a small design and marketing studio with a founder, a designer and an account manager. Their board has five columns: Backlog, Doing, Internal review, With client, Done.

• Doing: limit of two, so at least one person is always free to review or unblock.
• Internal review: limit of two, so finished drafts do not pile up waiting for the founder.
• With client: limit of four, because waiting on clients is normal but too much of it means chasing is overdue.
• Backlog and Done: no limit.

In the first week, Internal review hits its limit twice. Instead of starting new work, the designer and account manager ask the founder to block out review time each morning. The board did not create that bottleneck; it simply made it impossible to ignore.

What to do when you hit a limit

• Swarm the blocker. Atlassian’s advice is to help clear blocked work rather than let people sit idle or start something new. Ask “what can I do to move a card out of this column?”
• Do not raise the limit straight away. The guide warns that the first weeks feel awkward, and that discomfort usually points to a real process problem. Fix the cause before changing the number.
• Break big tasks down. Atlassian recommends keeping tasks small so one large card does not clog a column for days.
• Match limits to skills. If only one person can do a certain step, that column’s limit should reflect their capacity, not the whole team’s.

Common mistakes with kanban WIP limits

• Setting limits nobody follows. A limit only works if the team agrees to stop starting when it is reached. Agree the rule out loud.
• Hiding work off the board. If urgent requests go straight into someone’s inbox, the board stops telling the truth. Every piece of work gets a card.
• Ignoring waiting states. Many small teams lose the most time in “waiting for approval” or “waiting for client”. Give those stages their own column and limit.
• Never reviewing the numbers. Revisit limits every month or so, especially after the team or the type of work changes.

How to tell whether your WIP limits are working

You do not need a dashboard to judge the effect. Three simple signals, checked in a short weekly review, are enough for most small teams:

• Lead time. Note the date each card crosses the commitment point and the date it reaches Done. If the gap shrinks over a few weeks, flow is improving. This is the same lead time Atlassian describes for kanban boards.
• Cards stuck in one column. Count how many cards have not moved since the last review. A falling number means fewer things are being parked.
• Unplanned starts. Ask how often someone started a new task because they were blocked on the old one. If that happens less, the limits are doing their job.

Write the three observations down each week. After a month you will have a clear picture of whether to tighten a limit, loosen one, or split a column that is hiding two different kinds of waiting.

Where WIP limits fit in your business systems

WIP limits work best alongside a few other simple habits: a single board everyone uses, clear ownership for each card, and a short weekly review of what is stuck. If you are setting up those foundations, our business systems articles cover task ownership, SOPs and team routines that support a calmer flow of work.

Key takeaways

Kanban WIP limits cap how many cards can sit in each column, which exposes bottlenecks, cuts context switching and gets work to customers sooner. Start by counting what really sits in each stage, set limits a little below that, keep the in-progress limit below headcount, and leave Done unlimited. When a column fills up, help clear it instead of starting something new, keep tasks small, and review the limits regularly as your team changes.

Written by the Design Productive Editorial desk. Disclosure: this guide contains no affiliate or sponsored links.