Blocked Work Control

Blocked Work Control is the discipline of identifying, marking, tracking, and actively resolving work items that cannot progress due to an external dependency, obstacle, or unmet condition, so that blocked items do not silently consume Work in Progress capacity while producing no forward movement. It exists because a blocked item behaves differently from a normally progressing item even though both may occupy the same column or status on a board, and flow control requires distinguishing between the two.

Recognizing Blocked Work

Definition of a Blocked State

An item is considered blocked when further progress cannot occur until some condition outside the current owner's control is satisfied — for instance, awaiting a decision from another team, a missing piece of information, an external vendor delivery, or a failed dependency that must first be fixed elsewhere.

Distinguishing Blocked from Simply Slow

Blocked Work Control depends on separating items that are blocked from items that are merely progressing slowly due to complexity or effort required. A slow item still benefits from continued attention; a blocked item does not, no matter how much attention is applied, until the blocking condition is removed.

Why Blocked Work Requires Explicit Control

It Occupies WIP Without Producing Flow

A blocked item still counts against Work in Progress limits and still represents unfinished inventory, yet it contributes nothing to throughput while blocked. Left unmanaged, blocked items quietly consume capacity that could otherwise be allocated to progressing work.

It Can Mask the True State of the Workflow

If blocked items remain visually indistinguishable from active items on a board, the team's perception of how much work is genuinely moving becomes inaccurate, which undermines the reliability of stand-ups, flow metrics, and forecasts.

It Tends to Accumulate Silently

Because a blocked item requires no immediate action from its owner, it is easy for it to be forgotten or deprioritized in daily attention, allowing blockages to persist far longer than necessary if no explicit control mechanism forces regular reconsideration.

Mechanisms of Blocked Work Control

Explicit Blocked Markers

Boards commonly use a visible marker — a colored tag, a flag icon, or a dedicated "Blocked" swimlane — attached to an item the moment it becomes blocked, ensuring the blockage is visible to anyone glancing at the board rather than buried in a comment or conversation.

Recording the Blocking Reason

Effective control requires capturing why an item is blocked at the moment it is marked, since a generic "blocked" label without context makes it difficult for anyone other than the original owner to help resolve it or judge its urgency.

Tracking Blocked Duration

Measuring how long an item has remained blocked, separately from its overall cycle time, allows a team to identify chronic sources of blockage and to prioritize resolving the oldest or most impactful blockages first.

Escalation Paths

A defined escalation path — specifying who is contacted and when, if a blockage exceeds an expected duration — prevents blocked items from lingering indefinitely simply because no one owns the responsibility of pushing for resolution.

Removing Blocked Items From Active WIP Counts

Some flow control schemes explicitly exclude confirmed-blocked items from active WIP counts once they exceed a threshold duration, or place them in a distinct blocked buffer, so that the count of "active, progressing" work remains meaningful and does not overstate real throughput capacity.

Consequences of Poor Blocked Work Control

Distorted Flow Metrics

If blocked time is not tracked separately, cycle time calculations blend genuine processing time with unproductive waiting time, weakening the accuracy of forecasts derived from those metrics.

Chronic Bottlenecks Going Unaddressed

Without visibility into which dependencies cause blockages most often, teams cannot identify and address the systemic sources of blockage, and the same type of blocking issue may recur indefinitely.

False Sense of Progress

A board full of items that appear active but are in fact silently blocked can create a misleading impression of healthy flow, delaying recognition that meaningful progress has actually stalled.

Visual Representation

The red flag marks Item B as blocked, distinguishing it from Item A even though both occupy the same column. The proportion of active WIP that is genuinely progressing can be expressed as:

Blocked Work Control is the practice of keeping the second term of this equation visible, current, and actively driven toward zero, rather than allowing it to remain an unacknowledged part of the total.