WIP Limits (Work in Progress Limits)

Why It Matters

The human instinct when facing a large backlog is to start more work. This feels productive but is counterproductive. Research on multitasking consistently shows that juggling more than two or three cognitively demanding tasks simultaneously reduces productivity by up to 40%. Each additional task in progress creates context-switching costs, increases the time to completion for every item, and makes it harder to identify what is genuinely blocked versus what is simply waiting for attention.

How It Works

WIP limits, drawn from Lean and Kanban methodology, set an explicit maximum on concurrent work. When a team or individual hits their WIP limit, no new work can begin until something currently in progress is finished, handed off, or explicitly deprioritized. This creates a pull-based system: work is pulled into the active queue only when capacity exists, rather than pushed in based on demand or urgency.

The Benefits

WIP limits produce three measurable effects. First, faster cycle time: counterintuitively, limiting work in progress means individual items finish faster because they receive sustained attention. Second, better visibility: with fewer active items, it is easier to see what is stuck and where bottlenecks exist. Third, forced prioritization: when the team cannot start everything, they must decide what matters most, which surfaces priority conflicts early rather than late.

• Set WIP limits per person (typically two to three active tasks) and per team (based on capacity)
• Make WIP limits visible on your task board or project tracker
• When the limit is reached, the team focuses on finishing existing work before starting anything new
• Treat WIP limit violations as a signal, not a failure: they reveal where demand exceeds capacity
• Adjust limits based on observed flow, not theoretical estimates

Common Resistance

Teams resist WIP limits because they feel constraining. Stakeholders want their work started now, and saying "we are at our limit" feels like refusing to help. The key reframe is that WIP limits protect completion, not just activity. Starting work without capacity to finish it is worse than waiting, because it creates the illusion of progress while slowing down everything in the queue.