Pull system
Also known as Pull-based workflow, Pull scheduling
Definition
A pull system starts or advances work when the receiving stage has capacity and the item meets its policy. Pulling controls WIP and makes the decision to begin work visible.
Capacity decides what starts
In a pull system, upstream completion does not automatically force the next item into a full stage. A downstream participant pulls eligible work when capacity exists. This limits unfinished work and encourages finishing, unblocking, or improving the current queue before starting more.
A concrete example
An illustrative review stage has room for three changes. When the third change enters, the team does not pull a fourth just because implementation finished another item. The next choice is to review, unblock, or change the policy, making the constraint visible.
Make pull safe
Define eligibility, WIP limits, service classes, and what happens when no item meets the criteria. Pulling oldest eligible work can reduce arbitrary selection, but urgency or risk may justify another policy. Record exceptions rather than hiding them.
Limitations
Pull does not eliminate dependencies or guarantee balanced capacity. A team can pull poorly prepared work and create a new queue. The system works only when states and policies reflect reality.
How this relates to Weave
Weave can help teams investigate what happens after work is pulled into implementation, review, and delivery. It does not control the pull decision or replace workflow policies, which should remain visible to the people operating the system.
Explore Engineering intelligence