Work Completion Before New Work

Work Completion Before New Work is the flow-control principle that directs individuals and teams to prioritize finishing items that are already in progress over starting additional new items, even when starting something new feels productive or is readily available. It is one of the most direct behavioral expressions of limiting work in progress, translating the abstract idea of a WIP limit into a personal and team-level decision rule applied moment to moment.

The Underlying Rationale

Reducing Task-Switching Cost

Every time a person shifts attention from one item to a different, unrelated item, mental context must be rebuilt, and this rebuilding consumes time and cognitive effort that produces no direct output. Prioritizing completion of existing work over starting new work reduces the frequency of these switches and the hidden cost they impose.

Shortening Cycle Time

An item's cycle time includes any period during which it sits untouched while attention is diverted elsewhere. Choosing to finish existing work before beginning new work directly shortens these idle periods, which in turn shortens overall cycle time for items already committed to the workflow.

Reducing Inventory of Unfinished Work

Work that has been started but not finished represents inventory — invested effort that has not yet produced value. Favoring completion over new starts keeps this inventory from growing indefinitely, which in Agile flow terms keeps the system healthier and more predictable.

How the Principle Is Applied

At the Individual Level

An individual practicing this principle checks, before picking up a new task, whether any of their own currently active items could be advanced toward completion instead, and only starts new work once existing commitments have been finished or handed off appropriately.

At the Team Level

Teams apply the principle collectively by treating an accumulation of near-finished items as higher priority than the initiation of fresh backlog items, often making this explicit during stand-ups by asking what can be completed today before asking what should be started next.

Interaction with Pull Policy

This principle reinforces pull-based flow: because new work is only pulled when capacity opens up, and capacity only opens up when existing items are completed, prioritizing completion is what actually creates the conditions under which new work is allowed to begin at all.

Situations That Create Tension With the Principle

Specialization and Skill Mismatch

When a team member lacks the specific skill needed to help finish an in-progress item, they may feel there is nothing productive to do except start something new, which creates pressure against the principle that must be resolved through cross-training, pairing, or accepting temporary idle capacity.

Blocked Items

An item that is blocked, waiting on an external dependency, cannot be advanced no matter how much attention is applied to it, and teams must distinguish between genuinely blocked work — where starting something new may be reasonable — and work that is merely unattended, where the principle still applies.

Perceived Urgency of New Requests

A newly arrived request, especially one framed as urgent, creates psychological pressure to start immediately, and applying Work Completion Before New Work requires a deliberate evaluation of whether the new request is truly more valuable than finishing what is already underway, rather than an automatic reaction to novelty.

Consequences of Neglecting the Principle

Growing WIP and Slower Delivery

If new work is routinely started before existing work is finished, WIP accumulates beyond sustainable levels, and paradoxically the overall rate of completed, delivered work tends to fall even as the appearance of activity increases.

Aging, Stale Items

Items that are repeatedly deprioritized in favor of new starts risk becoming stale, losing relevant context, or requiring rework by the time attention finally returns to them, adding hidden cost that would not exist had the principle been followed.

Reduced Predictability

When completion is inconsistently prioritized, the time any given item takes to finish becomes highly variable, weakening the reliability of forecasts and commitments made to stakeholders.

Visual Representation

The preferred path, shown by the solid arrow, favors completion. This preference can be expressed as a simple prioritization rule applied at each decision point:

Applied consistently, this rule is what allows Work in Progress limits and pull policies to function as intended, since it supplies the behavioral discipline that keeps the flow of work moving toward completion rather than toward ever-widening breadth.