Everything is started, but very little reaches the client. A work-in-progress limit controls how much work a stage or team actively handles at once. Use it to expose queues and capacity choices, with clear rules for blocked work and genuine urgent requests.
Photo by Jakub Żerdzicki on Unsplash.
Define what counts as started and finished
Choose a workflow boundary such as preparing, reviewing and ready for client acceptance. Agree the completion condition for each stage. Work should not disappear from the view simply because it is waiting for a response or a decision.
Start with an observable limit
Choose a small, explicit limit based on the team's current capacity and work types. Treat it as a trial. When a stage reaches its limit, discuss finishing, unblocking or reprioritising existing work before pulling in another item. Do not solve every breach by raising the number.
Agree exception rules
Who can authorise urgent work?
Which existing commitment changes when it enters?
How are blocked items shown?
Which role can help finish constrained work?
When will the trial be reviewed?
An illustrative review queue
An agency limits active editorial reviews so the senior reviewer can finish a manageable number before more drafts arrive. The team records a missing-client-input case as blocked and assigns the follow-up. It does not pretend the case is complete to free a slot.
Agree whether blocked work occupies the active-stage limit or sits in a separately visible waiting state. Either choice needs a rule for returning it to active work. A sudden batch of client replies can otherwise exceed review capacity even when the board appeared within its limit the previous day.
Related guidance: practical process-mapping guide.
Compare completed work, waiting, quality and user experience during the trial. A limit should support better flow, not pressure staff to hide unfinished tasks. Hili Consulting can help test an operating rule that makes overload visible early.
