If you've ever been confused about cycle time versus lead time, you're not alone. These terms get misused constantly — even by consultants who should know better.
Getting them wrong doesn't just make you sound uninformed. It leads to measuring the wrong things and optimizing the wrong parts of your process.
Let's fix that today.
The Simple Definitions
Cycle Time: How long it takes to complete one unit of work, from start to finish of the active process.
Lead Time: How long it takes from when work is requested until it's delivered — including all waiting.
Here's the key insight: Lead time includes cycle time, but also includes queue time, wait time, and delays.
A Concrete Example
Imagine ordering a custom sandwich:
- You place your order (clock starts for lead time)
- You wait in line: 5 minutes (queue time)
- Sandwich maker starts building: 0 (cycle time starts)
- Assembly and toasting: 3 minutes (cycle time)
- Sandwich handed to you (both clocks stop)
Cycle time: 3 minutes (actual work) Lead time: 8 minutes (your total wait)
If you only optimize cycle time, you might get a 2-minute sandwich. But with a 10-minute queue, customers still wait 12 minutes.
Why This Distinction Matters
Most improvement efforts target cycle time. It's visible, measurable, and feels productive.
But here's the uncomfortable truth: in most processes, queue time dwarfs cycle time.
Studies across industries consistently show:
- Manufacturing: 5-10% of lead time is actual processing
- Software development: 10-20% of lead time is hands-on coding
- Healthcare: 15-25% of patient time involves actual treatment
The rest? Waiting. Sitting in queues. Stuck in handoffs.
When you only measure cycle time, you're optimizing the minority of time while ignoring where most time actually goes.
The Manufacturing View
In manufacturing, these terms have specific meanings:
Cycle Time = Machine or process time to produce one unit Takt Time = Available production time / customer demand Lead Time = Total time from order to delivery
The goal: Cycle time ≤ Takt time (so you can meet demand) The reality: Lead time is often 10-50x cycle time
The Software Development View
Agile teams often track:
Cycle Time = Time from "work started" to "work done" Lead Time = Time from "request created" to "deployed to production"
A task might have:
- Lead time: 14 days (from ticket creation to production)
- Cycle time: 2 days (actual development and testing)
Those 12 missing days? Sitting in backlogs, waiting for review, stuck in deployment queues.
Which One Should You Track?
Track both. They tell different stories:
Cycle time reveals process efficiency:
- How good are we at executing work?
- Where are the slow steps?
- Is individual performance improving?
Lead time reveals system efficiency:
- How fast can we deliver value?
- What does the customer actually experience?
- Is our overall flow improving?
If you can only track one, track lead time. It's what customers care about, and it exposes systemic issues that cycle time hides.
The Dangerous Trap
Here's what happens when you only measure cycle time:
- Team celebrates reducing processing time by 20%
- Customer experience doesn't change
- Leadership wonders why metrics improved but satisfaction didn't
- Turns out: 80% of delay was in queues between processes
- The "improvement" affected 4% of total lead time
I've seen teams spend months optimizing a 10-minute process while ignoring the 3-day queue feeding it.
Finding Your Hidden Queue Time
Calculate the ratio:
Flow Efficiency = Cycle Time / Lead Time × 100%
- Below 10%: Major queue problems (common)
- 10-25%: Typical for complex processes
- Above 25%: You're doing well
- Above 50%: World-class flow
Most organizations are shocked to discover they're below 10%.
Practical Measurement
To measure both:
- Mark timestamp when work enters the system (lead time start)
- Mark timestamp when active work begins (cycle time start)
- Mark timestamp when active work ends (cycle time end)
- Mark timestamp when delivered to customer (lead time end)
The gap between lead time start and cycle time start? That's your queue time — and usually your biggest opportunity.
Today's Action: Pick one process. Track a single item through from request to delivery. Note when it's actively being worked versus when it's just sitting. Calculate your flow efficiency. The number might surprise you.
Need visibility into where time actually goes? ProcessModel tracks cycle time and lead time automatically, showing you exactly where items wait — and how to eliminate those delays.