Task management · Practical guide
WIP Limits: Finish Work Before Starting More
By My First Task editorial team
Updated
The short answer
How to approach the work
A WIP limit applies to active work, not the entire backlog. Define where work starts and finishes, then decide whether the limit covers one column, several stages or the whole flow. When a stage is full, investigate waiting reviews, missing decisions or oversized items. A limit is a policy the team must follow; a visual board alone does not enforce it or guarantee a shorter cycle time.
A practical sequence
- Define the start and finish boundaries of the workflow.
- Measure how many items are usually active and how long they wait.
- Agree an initial limit the team can experiment with.
- When the limit is reached, help finish or unblock an existing item.
- Make any emergency exception visible and temporary.
- Review throughput and elapsed cycle time before adjusting the limit.
Illustrative scenario · not customer research
Worked example
A team has twelve items in progress and finishes about three comparable items each day. Under stable average conditions, Little's Law suggests about four days of average cycle time. This is a relationship between averages, not proof that changing the board limit from twelve to six will immediately halve delivery time. The team first notices that review work is waiting, agrees to clear the review queue before starting new development, and measures the resulting flow.
Common mistakes to avoid
- Setting a limit but allowing invisible work outside the board.
- Moving blocked items out of active work solely to bypass the limit.
- Applying a long-run formula to a single unstable snapshot.
Try the method with your own inputs
Questions answered
What WIP limit should my team use?
Should blocked tasks count as WIP?
Does My First Task enforce WIP limits?
Apply it in a shared workspace
Keep the agreed owner, completion criteria and important decisions with the work. Explore the relevant My First Task feature.
Research context is available in our source library. The worked example above is an editorial illustration.
Continue learning
Cycle Time vs. Lead Time: Boundaries and Worked Examples
Lead time measures elapsed time from a defined request or commitment to completion. Cycle time measures elapsed time from work starting to completion. The difference commonly includes waiting before active work begins.
ExploreKanban Metrics: WIP, Throughput, Cycle Time and Work Item Age
Four useful Kanban flow measures are work in progress, throughput, cycle time and work item age. Together they show how much work is active, how much finishes, how long finished work took and how long unfinished work has been active.
ExploreHow to Write a Task Description: Template and Examples
A useful task description states the result, why it matters, who owns it and how completion will be checked. Add the inputs, constraints and relevant links so the next person can act without reconstructing the request from chat.
ExploreMethod references
Turn the plan into shared work
Give each next action an owner, a completion condition and a realistic date. My First Task brings tasks, boards, project workflows and issue tracking into one workspace.