Lead time — Lead time is the total time from when a request is made until it is delivered.
In plain English
Lead time is the total time it takes from when work is requested until it is completed.
Not when someone starts working on it.
Not how long the machine runs.
Not how long it “should” take.
From request → to finished result.
If a customer places an order on Monday and receives it three weeks later, the lead time is three weeks.
Simple.
Brutal.
🔗 Flow
🔗 Cycle Time
🔗 Takt Time
What they actually mean
Most organizations don’t optimize lead time.
They optimize activity.
They measure:
• Machine utilization
• Labor efficiency
• Output per shift
And then wonder why customers still wait.
Lead time exposes the truth:
How long does the system actually take to deliver?
You can have:
• 95% machine utilization
• Fully booked teams
• Zero idle time
And still terrible lead time.
Because waiting dominates.
Lead time doesn’t care how busy you were.
It cares how long it took.
🔗 KPI
🔗 Bottleneck
Example
An order requires:
• 2 hours of processing
• 3 departments
• 4 approvals
Total processing time: 6 hours.
Actual delivery time: 12 days.
Lead time is not 6 hours.
It’s 12 days.
Where did the rest go?
Waiting.
Queues.
Priority changes.
Batching.
“Just finishing something else first.”
The system wasn’t slow.
It was congested.
Where you’ll hear it
Lean initiatives, operations reviews, customer complaints — and anytime someone says:
“Why does this take so long?”
Does it actually matter?
✅ Yes —
Lead time affects:
• Customer satisfaction
• Cash flow
• Stress levels
• Predictability
• Competitiveness
Shorter lead time means:
• Faster feedback
• Lower inventory
• Less firefighting
• Less chaos
Lead time is not just a metric.
It’s a symptom of system health.
Common misconceptions
Lead time equals processing time.
No. Processing time is usually a small fraction.
Reducing setup time automatically reduces lead time.
Not if batch sizes stay large.
If everyone works harder, lead time drops.
Usually the opposite.
Lead time only matters in manufacturing.
Lead time exists in projects, approvals, hiring, software, decisions.
Red flags
🚩 Processing time is measured — but total lead time isn’t.
🚩 Work-in-progress keeps increasing.
🚩 Urgent jobs constantly jump the queue.
🚩 Delivery promises are always “next week”.
🚩 The system looks efficient — but customers wait.
Worth learning?
5/5
If you understand lead time, you understand why most organizations feel productive but deliver slowly.
Deep dive
Lead Time vs Cycle Time
Cycle time = how long one unit takes once work starts.
Lead time = how long the unit waits + gets processed.
Cycle time is local.
Lead time is systemic.
Most improvements target cycle time.
Customers experience lead time.
🔗 Cycle Time
Why lead time explodes
Lead time increases when:
• Batch sizes increase
• Utilization approaches 100%
• Variability increases
• Bottlenecks shift
• Priorities constantly change
Small inefficiencies multiply across the chain.
Waiting compounds.
🔗 Flow
🔗 Bottleneck
The uncomfortable truth
Reducing lead time often requires:
• Smaller batches
• Lower utilization
• More visible problems
• Exposed instability
Which looks inefficient.
Until you measure system performance.
This is why Lean focuses on flow first.
Lead time follows.
🔗 Lean
Little’s Law (without the math lecture)
There’s a simple relationship:
More work-in-progress → longer lead time.
It’s not motivational.
It’s mathematical.
If your system is full of half-done work, lead time will increase.
No matter how hard people work.
This is why reducing WIP often reduces lead time faster than increasing output.
🔗 Little’s Law
🔗 Kanban
Report an error
Found something wrong or misleading? Let us know — we want this site to stay fact-based (even when we joke).