WIP Limit

A WIP (Work-In-Progress) limit is a numeric cap on how many tasks a person, a column, or a board can have in active status at once. In a Kanban setup, the most common pattern is to cap each “In Progress” column at twice the team size plus one — six engineers gives you a cap of thirteen.

The point isn’t to enforce productivity. The point is that when the limit is hit, the next task can’t enter the column until something leaves it — which forces the team to confront the bottleneck (usually QA review or stakeholder feedback) instead of routing around it by piling up more half-finished work.

Concrete example

A marketing team has five people. They cap the “In Production” column at eight items. On Wednesday, the column hits eight: three blog posts being written, two design briefs in progress, two landing pages being coded, one email being reviewed.

A new task comes in: “Write campaign brief for Q3 launch.” Without a WIP limit, it goes into “In Production” — now at nine items, spread thin across five people. With a WIP limit enforced, the new task sits in “Ready” and the conversation becomes: “What do we finish today to make room?” Usually that conversation surfaces a blocked task — something waiting for feedback from a stakeholder who hasn’t responded. Forcing the team to see the blockage is the mechanism.

Why it matters

Most teams don’t have a throughput problem — they have a concurrency problem. Starting ten tasks and finishing three is not 30% efficiency; it’s 100% context-switching overhead and zero shipped value until something reaches “Done.” WIP limits make the cost of context-switching visible before it has already happened.

The practical result: teams with enforced WIP limits typically reduce their average cycle time by 20–40% within the first quarter. The mechanism isn’t magic — it’s that WIP limits force you to have the conversations about blocked work that you were previously deferring.

Tools that enforce WIP limits properly

• Jira (free) — native column WIP limits in Kanban boards; blocks the column when the limit is reached
• ClickUp Business (£10/seat) — Kanban view supports WIP limits per column with a visual indicator
• Linear (£8/seat) — cycle limits enforce WIP at the team level, not just per-column

Tools that pretend to enforce but don’t

• Trello — the WIP Limit Power-Up adds a soft warning badge but does not block adding cards to an over-limit column; the team member can dismiss the warning with one click
• monday.com — no native WIP limit enforcement; the closest approximation is building an automation that fires when a column exceeds a threshold, which is a workaround, not enforcement. The automation fires after the limit is breached, not before.
• Asana — no native WIP limits at any tier; the list and board views don’t have a column-limit concept

Related concepts you’ll likely click next

• Kanban Board — the visual pull system that WIP limits are applied to
• Cumulative Flow Diagram — the visualisation that shows whether your WIP limits are having the expected effect on flow
• Throughput — the metric (items completed per time window) that WIP limits are designed to improve