Cycle Time vs Lead Time: What’s the Difference?

Lead time is the clock the customer experiences: the elapsed time from the moment a request enters the system to the moment it is fulfilled. Cycle time is the time spent actually working on one unit. The two are routinely confused, and the confusion matters, because the gap between them — often enormous — is where a process hides its waiting, its queues, and its waste. Improving one without watching the other is how teams get faster on paper while customers wait exactly as long as before.

How it’s used

A team that measures only cycle time tends to congratulate itself. The work, once started, goes quickly; everyone is busy; the metrics look strong. The customer, meanwhile, feels lead time — and lead time includes every hour the request sat in an inbox, a queue, or a handoff. Comparing the two numbers is one of the fastest diagnostics in process improvement: when hours of work stretch into weeks of elapsed time, the improvement target is the waiting, not the working. Practitioners formalize the comparison as process cycle efficiency — value-adding time divided by total lead time — and in unimproved processes the figure is usually startlingly small.

One honest caution: definitions vary between schools and teams. Some use cycle time to mean the working time per unit; others use it for the interval between successive completed units — a throughput rhythm closely tied to takt time. Neither is wrong, but a team that mixes them mid-project will produce numbers that cannot be compared. Agree definitions in writing before anyone starts a stopwatch.

A worked example

An illustrative lender approves small business loans in 14 days of lead time, and applicants complain constantly. The team traces a sample of applications and totals the time anyone actually touches one — reviewing documents, running checks, writing the decision. It comes to roughly two hours per application. The other thirteen-plus days are queues between departments and files waiting for sign-off. The lesson writes itself: halving the working time would save one hour and no one would notice; halving the queues would save days and every applicant would feel it. The team caps queue sizes and merges two approval steps, and lead time falls by days without anyone working faster.

• Measure lead time from the customer’s first signal, not from when your team got around to logging it
• Attack queues before speeding up work — the waiting usually dwarfs the doing
• Write down your definitions before collecting data; cycle time means different things to different teams
• Track both: cycle time sizes your capacity, lead time tells the customer’s truth

Customers never experience your effort — they experience your elapsed time.

Separating these two clocks is a Measure-phase skill, taught in our Yellow Belt program ($129, about 14 hours) and exercised fully in Green Belt DMAIC projects ($299, 35 hours, 100-question proctored exam). The free White Belt introduces both terms in about six hours — a sensible start if phrases like value stream and takt time are still new.