Work In Progress Limiting¶
Limit active work so the system completes existing commitments instead of spreading capacity across too many simultaneous items.
The Diagnostic Story¶
Symptom: The board is covered in sticky notes, every item is marked in progress, and nothing is finishing. People spend more time context-switching and status-reporting than completing work. High-priority items sit waiting because a dozen lower-value items are already occupying the active slots. Adding more work to the active pile has stopped increasing output.
Pivot: Define what counts as active work and enforce a hard limit. New work may only start when a slot opens or when a governed exception applies. Completion is treated as the primary goal, not the appearance of responsiveness through new starts.
Resolution: Cycle time drops because work moves through instead of queuing behind other active work. Bottlenecks become visible instead of hidden inside a sea of in-progress items. Completion events become frequent, capacity is honest, and blocked work is explicitly governed rather than silently stacked.
Reach for this when you hear…¶
[software team lead] “Everyone is busy and nothing is shipping because we have forty things in flight and no one can actually finish any of them.”
[hospital operations] “We keep pulling new patients into beds before the discharges happen, and now nothing flows.”
[creative production] “We started twelve campaigns this quarter and wrapped zero, so the client thinks we are moving but nothing has landed.”
Mechanisms / Implementations¶
- Kanban WIP Limit: A Kanban WIP limit implements the archetype by putting maximum counts on board columns, lanes, people, or stages.
- Active Case Cap: An active case cap implements the archetype in case-based systems such as support, care coordination, legal review, investigations, or public administration.
- Concurrency Limit: A concurrency limit implements the archetype in technical systems.
- Team Workload Cap: A team workload cap applies WIP limiting at team scope.
- Project Portfolio Limit: A project portfolio limit applies the archetype to initiatives and programs.
- Sprint Capacity Rule: A sprint capacity rule can support WIP limiting when it constrains active commitments during an iteration.
- Pull Replenishment Signal: A pull replenishment signal starts work when a downstream slot opens.
- Work Slot Token: A work slot token makes active capacity tangible.
- Blocked Work Swarming: Implements the completion-bias side of the archetype.
- Throughput-Based Limit Review: A throughput-based review ritual compares the WIP limit against cycle time, throughput, backlog growth, blockage, exception frequency, and quality.
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (4)
- Concurrency: Manage simultaneous processes.
- Constraint: Limits possibilities to guide outcomes.
- Queueing: Organizes tasks into a waiting line based on arrival and service rates.
- Resource Management: Allocation of finite assets.
Also references 7 related abstractions
- Boundedness: Values remain within limits.
- Feedback: Outputs influence inputs.
- Flow: Structured movement of energy, matter, or information.
- Observability: Infer internal state externally.
- Order: Defines ranking or sequencing relationships.
- Scheduling: Organizing tasks over time.
- Threshold: Safe vs harmful levels.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Stage WIP Limiting · subtype · recognized
Applies explicit active-work caps to particular workflow stages or service points rather than to the whole system.
Class-Based WIP Limiting · governance variant · recognized
Sets different WIP limits for different classes of work, risk, customer, case, service, or priority.
Portfolio WIP Limiting · scale variant · candidate
Limits the number of simultaneously active projects, initiatives, programs, or strategic efforts.
Technical Concurrency WIP Limiting · implementation variant · recognized
Limits the number of simultaneous technical operations, jobs, workflows, threads, requests, or tasks that may be active.