Pull Based Work Selection

Pull Based Work Selection is the foundational mechanism of flow-based systems in which new work is drawn into active status by the team only when genuine capacity becomes available, rather than being assigned or pushed onto the team according to a predetermined schedule or external directive. It inverts the traditional relationship between work and worker: instead of work being handed out, the system's own capacity signals when it is appropriate for the next item to begin.

The Core Principle

Capacity Signals Readiness, Not the Calendar

In a pull-based system, the trigger for starting new work is the completion of existing work and the resulting availability of capacity, rather than the arrival of a fixed planning interval or a manager's directive to begin something new.

Work Is Drawn, Not Assigned

Team members actively select the next item to work on from the organized queue, in accordance with agreed selection policies, rather than having work pushed onto them regardless of their current load.

The System Self-Regulates

Because new work only enters when capacity opens, a pull-based system naturally resists the accumulation of excessive work in progress, in contrast to push-based approaches where work can be added regardless of whether the system can actually absorb it.

Why Pull Improves Flow

Preventing Work-in-Progress Overload

Pull-based selection directly enforces work-in-progress limits, since no new item can be started until an existing item is completed and its slot becomes genuinely free, preventing the silent accumulation that push-based systems are prone to.

Reducing Multitasking and Context Switching

Because team members are not handed new work regardless of their current commitments, pull-based selection discourages the kind of forced multitasking that occurs when work is pushed onto already-occupied capacity.

Surfacing Bottlenecks Naturally

When a particular stage in the workflow cannot pull new work because it remains occupied, this visibly signals a bottleneck, drawing attention to exactly where the system needs improvement rather than hiding the problem behind externally imposed deadlines.

Aligning Work Start With Actual Availability

Pulling ensures that work begins only when someone with the necessary capacity and attention is genuinely ready to engage with it, improving the likelihood of sustained, uninterrupted progress once work does start.

How Pull Operates in Practice

Completing Work Triggers the Next Pull

As soon as an item is finished and moved out of active status, the resulting open capacity prompts the team member, or the next appropriate stage, to pull the next ready item from the queue.

Selection Governed by Agreed Policy

The specific item pulled follows the team's established work selection policies, ensuring pull decisions remain consistent and are not left to arbitrary preference.

Stage-to-Stage Pull in Multi-Step Workflows

In workflows with multiple sequential stages, each downstream stage pulls work from the stage before it only when it has capacity, rather than upstream stages pushing completed work forward regardless of downstream readiness.

Contrasting Pull With Push

Push-Based Assignment

Work is scheduled or assigned in advance based on planning-time estimates of who should be doing what, regardless of whether actual real-time capacity aligns with that plan when the moment arrives.

The Risk Push Systems Carry

Push-based approaches can result in work being started before genuine capacity exists to handle it properly, since the decision to begin was made in advance rather than in response to real-time system state.

Why Pull Suits Continuous Flow

Because flow-based systems operate continuously rather than in discrete planning cycles, pull provides a natural, ongoing mechanism for controlling work entry that does not depend on periodic replanning to stay accurate.

Measuring Pull System Health

Idle Capacity Rate

A high idle rate may indicate the ready queue is insufficiently stocked, undermining the responsiveness pull-based selection is meant to provide.

Common Failure Modes

Reintroducing Push Behavior Informally

Allowing managers or stakeholders to directly assign specific work to specific individuals, bypassing the pull mechanism, quietly undermines the self-regulating benefit the system depends on.

Pulling Without Sufficient Ready Work Available

If the queue frequently lacks genuinely ready items when capacity opens, team members may be forced to pull unready work or sit idle, both of which erode the effectiveness of pull-based selection.

Ignoring Selection Policy During Pull

Allowing pull decisions to default to convenience or individual preference, rather than following agreed selection policy, reintroduces the inconsistency that structured selection is designed to prevent.

Treating Pull as Purely Individual Rather Than Systemic

Focusing only on individual team members pulling their own next task, without attention to how work moves across the entire multi-stage system, can allow bottlenecks between stages to persist unnoticed.