Limit Work in Progress (WIP)
Category: Flow & Delivery Dynamics
Principle Intent
Limit the amount of work in progress to reduce overload, improve flow, and increase predictability. Finishing work faster requires starting less work at the same time.
Warning Signs — When This Principle Is Being Violated
These observable signals indicate the principle is not operating effectively in your delivery system:
- Many items are in progress while few are completed
- People frequently switch contexts throughout the day
- High priority loses meaning because everything is urgent
- Cycle times grow longer and more unpredictable
- Individuals carry hidden queues of unfinished work
- Automation or AI enables rapid task creation without limits on execution or review
Systemic Consequences if Ignored
When this principle is absent or routinely violated, the following patterns tend to emerge over time:
- Lead time and cycle time increase across the system
- Quality degrades due to fragmented attention
- Predictability collapses because work competes rather than flows
- Burnout rises as effort increases without visible progress
- In agentic systems, unlimited parallelism overwhelms human review and validation capacity
Over time, starting work becomes easier than finishing it.
Left unaddressed, these patterns can potentially form following Unintended System Conditions (USC): Workload Saturation (Primary), Batch Amplification (Contributing)
Workload Saturation is precisely what happens when WIP is not limited. Queues build, capacity fills, and delay amplifies. This principle is the direct structural response to Workload Saturation. High WIP also correlates with large batches moving through the system together.
Coaching Lens — Questions to Surface the Violation
Use these questions to diagnose whether this principle is being violated in your current situation:
- How much work is actually in progress right now?
- Where is work piling up but not moving?
- What would finish sooner if we stopped starting new items?
- Which constraints are being hidden by multitasking?
- As execution becomes cheaper, where must limits tighten to preserve flow?
Anti-Patterns — What Not to Do
Common mistakes leaders make when trying to apply or restore this principle:
- Treating WIP limits as utilization or productivity targets
- Setting arbitrary limits without observing system behavior
- Applying limits only at the team level while demand remains unconstrained
- Forcing people to manage overload instead of reducing it
- Allowing AI systems to create work without corresponding WIP constraints
Recommended Practices
Actions and approaches that help make this principle a real system property:
- Make all work in progress visible, including individual and hidden queues
- Apply WIP limits at the system boundary, not just within teams
- Require finishing work before starting new items
- Use WIP limits to surface constraints and bottlenecks
- Explicitly cap concurrent work, reviews, and validations in agentic systems
These practices shift the system from maximizing activity to maximizing flow.
Apply This Principle with the PPA Method
When this principle is violated in your delivery system, use the PPA Method to respond deliberately:
- Problem: Diagnose the system-level behavior producing recurring symptoms. Use the warning signs above to confirm the violation.
- Principle: Identify that this principle—Limit Work in Progress (WIP)—is the root explanation for why the behavior persists. The coaching lens questions above help surface this.
- Action: Choose deliberate actions from the recommended practices above that reinforce this principle within your real constraints.