Define started and finished, count blocked jobs once and use capacity signals before pulling more client work.
The designer has six files open. The printer is waiting for an approved proof, and the account manager has started another urgent request. Everyone is busy, but the client still cannot collect a finished job.
A limit on work in progress makes that problem visible. It asks the team to define when work starts, when it is finished and how much unfinished work it will carry. For a Nepal service or production team, this can create a clearer conversation about flow than simply adding more tasks to everyone’s list.
Define the boundary around unfinished work
The Kanban Guide describes work in progress as items started but not finished, using the team’s defined workflow boundaries. It also calls for explicit control of that work. A board is useful when its states and rules mean something consistent to the people using it.
A hypothetical Lalitpur print studio chooses “production accepted” as its start and “finished job ready for collection” as its finish. Work waiting for client proof approval after the start remains unfinished. Moving it to a blocked column does not make it disappear from the studio’s total work in progress.
Illustrative planning scene with conceptual software screens; not real staff or client evidence.
Make the limit a decision rule
Choose a starting limit that reflects the actual constraint and review it. The number is a trial policy, not a universal formula or a target for keeping every employee occupied. Explain what the team does when the limit is reached: help finish work, resolve a blocker or negotiate which commitment changes.
| Policy |
Example decision to agree |
| Start boundary |
Production accepted |
| Finish boundary |
Finished job ready for collection |
| Whole-workflow limit |
Trial policy of three started unfinished jobs |
| Exception |
Named approval and displaced work recorded |
A limit without an exception rule can encourage hidden work. Let the team record an authorised exception and the reason. If every request is labelled exceptional, review the policy and incoming commitments instead of quietly expanding the limit each day.
Suggested decision flow. Review the actual software behaviour and approval rules before implementation.
Count blocked items once
Assume the studio has agreed a hypothetical whole-workflow limit of three jobs. At a review it has two jobs actively being worked and one started job waiting for the customer’s proof decision. Total work in progress is three, so there is no free slot under the agreed rule.
HYPOTHETICAL / three-job limit. A waiting unstarted fourth job is outside current WIP. No delivery-speed result is predicted.
A fourth job has been requested but not started. It belongs in the waiting queue, not in the three-job total. When one of the original jobs reaches the defined finish, two remain and one slot becomes available. None of this proves a particular delivery speed or guarantees that three is the right limit for another team.
Hypothetical workflow dashboard; not a live WorkSphere screenshot. P-12 still counts in WIP. P-14 is shown for queue visibility, not added to WIP.
The conceptual board makes the blocked job and its next action visible. It does not show it as complete or create a second card just to remind someone. If a job has several subtasks, define whether the limit counts the whole job or a different unit; mixing both makes the number unreliable.
Deal with the blocker before pulling more work
A blocked proof needs a specific owner and next action. Perhaps the account manager must ask the client to confirm a size. Perhaps the designer has not provided a readable preview. Identify the actual reason rather than blaming “client delay” without evidence.
Consider whether the team can safely work on another part of the same job. If not, the business may explicitly pause or cancel the commitment under a documented rule. Keep the history and customer agreement, rather than moving the item outside the boundary merely to create an apparent spare slot.
Conceptual illustration of the underlying decision; no measured outcomes or exact figures represented.
Review age as well as the number of cards
Two boards can each contain three unfinished jobs while facing very different problems. One may contain fresh work; the other may contain a job waiting for a decision for several days. Record when each job crossed the start boundary and inspect the oldest unfinished work.
The Kanban Guide distinguishes current work-item age from cycle time measured after a job finishes. The example below uses elapsed calendar days at one cut-off, not staff hours or a forecast of completion.
Nepal time, 2026. Age is not staff effort or a forecast of completion.
A longer age is a prompt to investigate. It is not evidence of an individual employee’s poor performance. Compare the reason, size and history of the work before drawing conclusions. Use the review to make a decision that helps the job progress.
Illustrative review scene; any screen shown is conceptual, not a live product screenshot.
Connect the rule to customer promises
The sales or CRM owner needs to know whether a new job has been accepted into production or is still waiting. A customer can receive an honest planned start date without staff pretending that the work is already underway. Inventory availability and equipment readiness may also affect admission to production.
If evaluating a task system or proposed WorkSphere workflow, ask for visible start and finish definitions, blocked reasons and exception history. Do not assume a drag-and-drop board enforces the limit or updates customer commitments automatically. Test the actual behaviour with one blocked job and one urgent new request.
The Kanban Guide May 2025