Column Limits: Using WIP Caps to Keep Task Boards Honest
Most task boards fail in a quiet way. Cards pile up in the In Progress column, nothing seems to finish, and the team feels busy without shipping. A work-in-progress limit is one of the simplest ways to make that problem visible. Instead of asking people to try harder, you agree in advance on how many items a column or a person can hold at once. When the limit is reached, the board tells you something true: new work has to wait until something finishes. This article covers how to choose limits, how to apply them without turning the board into a bottleneck, and what questions to ask when the numbers stop adding up.
Why unlimited columns hide overload
An open-ended In Progress column is comfortable because it never says no. Every request can be accepted, labeled as started, and left to sit. Over a few weeks the column fills with cards that are technically active but have not moved in days. People stop trusting the board, and the real status of work lives in chat threads and memory instead.
A limit changes the conversation. When a column already holds its maximum number of cards, adding another one is a visible decision rather than a silent habit. The team can see the tradeoff: starting something new means something else has to be paused, reassigned, or finished first.
Choosing a starting number
Do not pick a limit from theory. Start by counting how many items your team has actually been carrying in a typical week, then look at how many of those finished. If a team of four regularly has fifteen open items and closes four a week, a reasonable first limit might be one or two items per person in the active column, with a total cap that matches what the team has historically finished in a comparable period.
Expect the first version to be wrong. Treat the limit as a hypothesis. Revisit it after two or three weeks and ask whether the limit caused waiting that was useful, or whether it caused idle time and blocked people who had nothing to do. Adjust in small steps rather than redesigning the whole board.
Applying limits without creating a bottleneck
The most common failure is a limit that stops work entirely. If a column is full and the people who could finish those cards are waiting on a review, the limit produces stalled capacity rather than focus. To prevent this, give every limited column a clear rule for what happens when it is full. Good options include: swap a card out of the column only when another finishes, escalate a blocked card to the owner, or split a large card into smaller pieces that can move independently.
Also distinguish between columns that represent real work and columns that represent waiting. A Review or Waiting on Customer column often needs its own separate limit or no limit at all, because cards there are not being actively worked on by the team.
A short checklist for reviewing your limits
Use these questions at the end of each week or sprint rather than at random moments:
First, how many items are in each limited column right now, and how many of them moved in the last three days? Second, which cards have been blocked the longest, and who owns the next action on each one? Third, did any new request get deferred because a limit was reached, and was that deferral the right call in hindsight? Fourth, are people waiting on work that is stuck in a column they cannot touch, and does the board show that dependency clearly?
If the answers show many untouched cards, lower the total limit. If the answers show people idle while cards wait for review, raise the limit on the active columns or add a review slot. If requests keep getting deferred without a clear reason, the problem may be priority rather than capacity, and that calls for a separate conversation about what the team is actually for.
Making limits a team habit
A limit only works if the team agrees to respect it. Write the rule where everyone can see it, state what happens when the limit is reached, and name who decides when to change it. Keep the board's configuration simple enough that people can remember it without looking. Over time, the team will notice that a full column prompts a useful question, such as what can we finish before we start something else? That question, asked consistently, does more for throughput than any single rule on the board.