Here is a scene you might recognize. Your team has a kanban board. It looked great the day you set it up — neat columns, a satisfying row of cards to do. A few weeks later, the “In Progress” column has become a wall of sticky notes, half of them stalled, and somehow the work is slower than it was before you had a board at all.
The board isn’t the problem. The problem is that nobody put a ceiling on how much work can be in progress at once. That ceiling has a name — a WIP limit — and it is the single most underused feature in kanban. Get it right and your board stops being a to-do graveyard and starts pulling work through to done.
What a WIP limit actually is
WIP stands for “work in progress” — anything you’ve started but not finished. A WIP limit is simply a cap on how many cards are allowed in a given column at one time. You might decide that “In Progress” can hold at most three cards for your team, or even just one or two per person. Once the column is full, no new work moves in until something moves out.
It sounds almost too simple to matter. It matters enormously, because it changes the question your team asks every morning. Instead of “what should I start?” the question becomes “what can we finish?” — and finishing is the only thing that actually delivers value to a customer.
Why too much “in progress” quietly kills your pace
When everything is open at once, three things happen, and all of them are bad.
First, you multitask, and multitasking is a tax. Every time you switch from one half-done task to another, you pay to reload the context — where you were, what you were thinking, what’s left. A team juggling ten open cards can easily lose a third of its day just to switching.
Second, nothing finishes. A card that’s 90% done delivers exactly zero value until it crosses the finish line. Ten cards at 90% feel like enormous progress and produce nothing.
Third, problems hide. When work is spread thin across a dozen tasks, a blocker on any one of them is easy to ignore — you just go work on something else. The blocker sits there, quietly aging, while you feel busy.
How finishing beats starting
A WIP limit forces a healthier habit: stop starting, start finishing. When the “In Progress” column is capped and full, the only way to pull in something new is to complete something old. That single constraint pushes your team to swarm on whatever is closest to done, clear it, and only then reach for the next thing.
The payoff is counterintuitive. By deliberately doing less at once, you finish more over the week. Cards spend less time sitting idle, so the time from “started” to “done” — what teams call cycle time — drops. Clients notice, because things they asked for actually arrive.
Setting a sensible limit for your team
There’s no magic number, but there is a good starting point. A common rule of thumb is roughly one to two active cards per person. A three-person team, then, might cap “In Progress” at four or five. If you’re a solo owner or freelancer, try a limit of two: one thing you’re actively doing, one thing genuinely waiting on someone else.
Write the number right at the top of the column so it’s impossible to ignore. Then treat it as a hypothesis, not a law carved in stone. If your board is constantly jammed and people are standing around, your limit may be too low. If cards still sprawl and stall, it’s too high. Adjust by one and watch what happens over a week or two.
What to do when you hit the limit
The first time your column fills up and someone can’t start a new task, it feels like the system is broken. It isn’t — that’s the system working exactly as designed. Hitting the limit is a signal, and the right response is a small, useful conversation:
- What’s blocking the oldest card? If a task has stalled, find out why and clear it before touching anything new.
- Can two people finish something faster together? Swarming a near-done card is almost always better than each person opening a fresh one.
- Is a whole column always jammed? A column that’s perpetually at its limit is pointing straight at your bottleneck — the real constraint on your team’s output.
That last point is the quiet superpower of WIP limits: they don’t just speed you up, they show you where your process actually breaks.
Rolling it out without a rebellion
Don’t announce sweeping new rules on a Monday. Pick one column — usually “In Progress” — set a limit that feels slightly uncomfortable, and try it for two weeks. Talk about it in a short weekly check-in: did we finish more? Did anything feel stuck? Let the team adjust the number themselves; a limit they chose is a limit they’ll respect.
The goal is never to make people feel boxed in. It’s to give a busy team permission to do the most valuable thing they can do — finish what they’ve already started.
The takeaway
A kanban board without WIP limits is just a prettier to-do list. Add a cap to your busiest column, and the board starts doing real work: it protects focus, surfaces bottlenecks, and pulls tasks all the way to done instead of leaving them stranded at ninety percent.
Start small. Cap one column, watch what finishes, and tune the number to your team. If your current tool makes that hard to see, a simple kanban board with a visible limit at the top of each column — like the ones you can build in KanbanBlocks — makes the whole thing click into place. Less work in progress, more work actually done.
Sources & further reading: