Pull means work is triggered by real demand — not forecasts, not internal schedules, not optimism.
You don’t produce because you can.
You produce because something downstream needs it.
Pull systems aim to:
• Reduce overproduction
• Stabilize flow
• Shorten lead time
• Expose bottlenecks
If work only starts when it’s needed, inventory stays low and problems surface faster.
Most organizations claim they run on demand.
They don’t.
They run on:
• Forecasts
• Capacity utilization
• “Since we’re already set up…”
• “Let’s just run a few extra.”
That’s push.
Push fills the system.
Pull empties it.
Pull feels uncomfortable because it limits activity.
Push feels productive because everything looks busy.
Pull is about system stability.
Push is about local efficiency.
🔗 Cycle Time
🔗 Bottleneck
A downstream process consumes 50 units per hour.
Upstream can produce 80.
In a push system:
Upstream runs at 80.
Inventory grows.
In a pull system:
Upstream produces 50.
Flow stabilizes.
Pull aligns production with demand.
Push aligns production with capacity.
Lean workshops, Kanban discussions, supply chain planning — and anytime someone says:
“We should produce ahead to be safe.”
✅Yes.
Pull:
• Reduces inventory
• Shortens lead time
• Makes bottlenecks visible
• Improves predictability
Push:
• Hides instability
• Increases WIP
• Inflates lead time
• Creates artificial urgency
Pull doesn’t eliminate problems.
It removes the cushion hiding them.
🔗 Little’s Law
🔗 Priority
Pull means producing less.
No. It means producing what is needed.
Pull eliminates planning.
No. It changes what planning focuses on.
Pull works only in manufacturing.
Pull applies to approvals, software work, hiring, and projects.
Pull means zero inventory.
No. It means intentional inventory.
🚩 Production continues even when downstream is full.
🚩 Work-in-progress keeps growing.
🚩 Forecasts override real consumption signals.
🚩 “We’re ahead of schedule” — but customers still wait.
🚩 Managers reward utilization over system stability.
🔗 Manager
5/5
If you understand pull, you understand why most organizations create their own congestion.
Push vs Pull
Push systems:
• Produce based on schedule
• Optimize utilization
• Fill buffers
• Hide variability
Pull systems:
• Trigger production based on consumption
• Limit WIP
• Expose constraints
• Stabilize flow
Push maximizes activity.
Pull maximizes stability.
Pull and Flow
Pull enables flow by:
• Preventing overproduction
• Controlling WIP
• Aligning production with demand
Without pull, flow breaks under pressure.
Without flow, pull collapses into chaos.
Kanban as a pull mechanism
Kanban is one implementation of pull.
It limits how much work can be in the system at once.
Less WIP → shorter lead time.
More WIP → longer lead time.
Not motivational.
Mathematical.
🔗 Kanban
🔗 Little’s Law
Found something wrong or misleading? Let us know — we want this site to stay fact-based (even when we joke).