Here's a question that separates teams who measure from teams who improve: How much of your process time is actual work, and how much is just waiting?
Most teams can't answer this. They track how long things take end-to-end and call it a day. But that single number hides the most important insight in process improvement — the difference between cycle time and lead time. Understanding that difference, and more importantly the gap between them, is where real improvement begins.
Two Clocks, Two Stories
Cycle time is the time spent actively working on something. Hands on the product, fingers on the keyboard, tool on the material. It's the stopwatch running only when value-adding work is happening.
Lead time is the total elapsed time from the moment a request enters the system until it's delivered. It includes every minute of cycle time — plus every minute of waiting, sitting in a queue, being transported, awaiting approval, or gathering dust in someone's inbox.
Think of it this way: if you order a coffee at a busy cafe, the cycle time is the 90 seconds the barista spends making your drink. The lead time is the 12 minutes from when you placed your order to when you picked it up. That other 10.5 minutes? You were waiting. The coffee was waiting. Nobody was adding value.
The coffee still gets made in 90 seconds regardless of how many people are in line. But your experience — your lead time — changes dramatically based on everything around the work.
Why the Gap Matters
In most processes, cycle time is a small fraction of lead time. Surprisingly small. Studies across industries consistently find the same pattern:
- Manufacturing: A product that takes 4 hours of actual machining, welding, and assembly sits in the factory for 6 weeks. Cycle time is less than 2% of lead time.
- Software development: A feature that takes 3 days to code and test takes 4 weeks from request to deployment. Active development is about 15% of the elapsed time.
- Healthcare: A patient who receives 45 minutes of actual medical care spends 4 hours in the ER. Treatment is less than 20% of the visit.
- Loan processing: An application that requires 2 hours of actual review and data entry takes 10 business days to process. Work content is under 3% of elapsed time.
These ratios aren't anomalies. They're normal. And they tell you something critical: most of the time in your process isn't work — it's waste.
This is why improving cycle time alone often fails to move the needle. If you make the barista 20% faster at making coffee, you save 18 seconds. If you eliminate 3 minutes of queue time, you save 3 minutes. The bigger improvement comes from attacking the gap, not the work.
The Five Types of Waiting
The gap between cycle time and lead time is filled with waiting. That waiting comes in predictable forms:
Queue time. Work sitting in a pile waiting for the next available resource. This is the most common source of delay. Every inbox, backlog, staging area, and "pending" folder is a queue. Queue time is governed by Little's Law (Tip 014): more work in progress means longer queues.
Batch time. Work waiting because the process requires a batch before it can proceed. "We run invoices every Friday." "Lab tests are processed in batches of 50." "We deploy every two weeks." The individual item is ready, but the batch isn't full yet.
Transport time. Work moving between locations — physically or digitally. The time a document spends being routed between departments. The time parts spend on a conveyor or in a truck between facilities. Movement that's necessary but adds no value.
Approval/handoff time. Work waiting for someone to review, approve, or take the next action. The report sitting in a manager's inbox for three days. The design waiting for sign-off. Every handoff is a potential delay.
Setup and changeover time. The time to prepare equipment, systems, or people for the next task. Machine changeovers, context switching between projects, logging into different systems. No product is being worked on, but the process can't move forward without it.
Each type of waiting has different root causes and different solutions. You can't fix them if you can't see them, and you can't see them if you only measure lead time.
How to Measure Each
Measuring Cycle Time
Cycle time measurement requires observing actual work. There are several approaches:
Direct observation. Watch the process and time the active work steps. This is the most accurate method but also the most labor-intensive. It works well for repetitive, physical processes.
Work logging. Have workers record when they start and stop active work on each item. This introduces some self-reporting bias but scales better than observation. Digital tools with start/stop timers make this easier.
System timestamps. If work happens in a digital system, use status change timestamps. When did the item move from "in progress" to "done"? But be careful — "in progress" often includes wait time if people don't update statuses in real time.
Value stream mapping. Walk the entire process and estimate cycle time at each step. This gives you a process-level view rather than individual item measurements (see Tip 018 on value-added analysis).
The key distinction: only count time when someone is actively working on the item. If they set it aside to work on something else, the clock stops.
Measuring Lead Time
Lead time is simpler to measure because it uses two timestamps:
Start: When did the request enter the system? The moment the order was placed, the ticket was created, the material arrived at the first step.
End: When was the deliverable completed? The moment the product shipped, the service was rendered, the ticket was closed.
Lead time = End timestamp − Start timestamp. That's it.
The challenge isn't the math — it's agreeing on where the clock starts and stops. An order's lead time looks very different depending on whether you start timing when the customer calls, when the order is entered in the system, or when production begins. Be explicit about your measurement points and keep them consistent.
Making the Gap Visible
Once you have both measurements, calculate the efficiency ratio:
Process Cycle Efficiency = Cycle Time ÷ Lead Time × 100%
This single number tells you what percentage of your lead time is actual work. The rest is waste.
World-class processes operate at 25-50% efficiency. Average processes run at 5-15%. Many processes — especially those involving knowledge work, approvals, and multiple handoffs — operate below 5%.
If your efficiency ratio is 3%, that means 97% of your lead time is waiting. You could triple your cycle time (make the work take three times longer) and your lead time would barely change. Conversely, cutting wait time by even 20% would deliver massive improvement that your customers actually feel.
This reframes the improvement conversation entirely. Instead of asking "How do we do the work faster?" you ask "How do we reduce the waiting?" The second question is almost always easier to answer and more impactful.
Closing the Gap
Once you can see the gap, here's how to close it:
Reduce batch sizes. If work waits for a batch, make the batch smaller. Instead of processing invoices weekly, process them daily. Instead of deploying biweekly, deploy daily. Smaller batches mean less waiting (see Tip 004).
Limit WIP. Queues grow when work in progress exceeds capacity. Use WIP limits (Tip 019 on Kanban) to prevent overloading and reduce queue time.
Eliminate handoffs. Every handoff is a queue. Cross-train team members so that one person can complete more steps without passing work to someone else. Fewer handoffs = fewer queues = shorter lead time.
Reduce approval layers. Every approval is a wait. Ask: what's the cost of a wrong decision versus the cost of the delay? Often, pushing authority to the front line and auditing after the fact is faster and cheaper than gate-keeping every decision.
Co-locate or synchronize. If transport time is significant, move resources closer together — physically or digitally. If work waits for people in different time zones, create overlap windows or shared queues.
Automate the non-value steps. Don't automate the work (automate that too if you can, but that's a different project). Automate the routing, the notifications, the status updates, the handoffs. Reduce the friction between work steps.
The Insight That Changes Everything
Here's what experienced process improvers know: cycle time improvements make your team faster, but lead time improvements make your customers happier. Both matter. But if you have to choose where to invest, the gap between them is where the biggest returns hide.
A hospital that reduces surgery time by 10 minutes helps one patient at a time. A hospital that reduces the time between "patient is ready for surgery" and "surgery begins" by 30 minutes helps every patient in the queue.
A factory that speeds up an assembly step by 5% improves one workstation. A factory that eliminates a day of queue time between departments improves the entire flow.
The gap between cycle time and lead time is where your process spends most of its life doing nothing. Measure both, compare them honestly, and you'll never run out of improvement opportunities.