Controlling Work‑in‑Progress: Delay Start and Focus on Completion

In lean product development, the principle "Delay Start, Focus on Completion" (Stop Starting, Start Finishing) is advocated to avoid the side‑effects of work‑in‑progress (WIP) that arise when tasks are started but not finished promptly.

The core idea is that only when user value is delivered can a task be considered complete; therefore, WIP should be measured in units of user value rather than merely counting parallel tasks.

Controlling WIP by user value makes the flow of value visible, helps teams and managers quickly identify problems, and gains better support from business stakeholders because the focus shifts from abstract task limits to concrete value delivery.

Rather than speaking of "limiting" WIP, the article prefers the term "controlling" WIP, which implies a proactive approach with a broader set of possible actions aligned with the goal of early value delivery.

Common control techniques include:

Organizing development work around user‑value items so that task completion directly translates into delivered value.

Rapidly identifying and resolving impediments to finish started work.

Quickly moving completed work to testing and subsequent stages.

Prioritising bug fixes discovered in testing over starting new tasks.

Limiting the number of concurrent demand items to focus on finishing those already started.

When formal limits are not yet feasible, visualising the queue and actively reducing waiting and parallelism.

These practices, when applied in daily stand‑ups and planning activities, create a virtuous cycle where controlling WIP enables fast value delivery, and fast value delivery further reinforces effective WIP control.

In summary, "Delay Start, Focus on Completion" means that only delivered user value counts as finished work; controlling WIP by user value is the prerequisite for smooth, rapid delivery, making WIP control a natural outcome of a well‑designed Kanban system.