Key takeaways
Short answer: Cycle time and lead time measure two different clocks. Cycle time is internal: how long it takes to actually produce one unit at a step or across the line. Lead time is external: how long the customer waits from placing a request to receiving the finished product. The crucial point is that lead time includes cycle time but is usually dominated by everything around it — queuing, batching, transport, and waiting. A short cycle time hidden inside a long lead time is one of the most common signals of process waste. For the wider system, see OEE for manufacturing.
Cycle time is the time it takes to complete one unit at a given process, from starting one piece to starting the next — or across a whole line, the rate at which finished units emerge. It is an internal, production-centric measure: it tells you how fast the work itself happens when it is happening. Cycle time is what you tune when you balance a line, debottleneck a station, or compare a machine against its rated speed. It says nothing, though, about how long a unit waited in a queue before its turn came, which is why cycle time alone can look excellent while customers still wait far too long.
Lead time is the total elapsed time from a customer's request to delivery of the finished product. It is the clock the customer actually experiences, and it spans everything: order processing, material availability, queuing before each step, the production itself, movement between steps, batching delays, inspection, and shipping. Because it includes all the waiting, lead time is usually far longer than the sum of the cycle times — often by an order of magnitude. Lead time is the honest measure of responsiveness; it is what determines whether you can quote a customer two days or two weeks, regardless of how fast any single machine runs.
The space between a short cycle time and a long lead time is where waste hides. If a unit takes minutes of actual processing but days to reach the customer, the difference is almost entirely non-value-added waiting: sitting in queues, waiting for a batch to fill, waiting for the next step to free up. This is why focusing only on cycle time can mislead — speeding up a machine that is already fast does nothing if the unit then waits two days in a queue. The biggest lead-time gains usually come not from faster processing but from removing the waiting between steps, which is exactly what pull systems and flow improvements target.
A part needs four operations with cycle times of 2, 3, 2, and 3 minutes — ten minutes of actual processing. Yet the measured lead time from order to delivery is three days. Where did the time go? The part waited in a queue before each station, sat in a batch until twenty units accumulated, and waited overnight for the next shift. Total processing: ten minutes. Total waiting: nearly three days. Chasing the cycle times — shaving a minute off operation two — barely moves the lead time. Cutting the batch size and the inter-step queues, on the other hand, could collapse the lead time from days to hours. The math points straight at the waiting, not the working.
Focus on cycle time when the constraint is genuinely the processing speed of a step — a true bottleneck running flat out, or a machine well below its rated rate. That is where faster processing directly lifts output. Focus on lead time when customers are waiting longer than the actual work justifies, which is most of the time. Reducing lead time means attacking the waiting: smaller batches, less queuing, better flow, pull replenishment. The two are related — cycle time is one component of lead time — but they call for different interventions, and confusing them sends improvement effort to the wrong place.
Cycle time is woven directly into OEE: the performance factor compares your actual cycle time against the ideal, so slow cycles and micro-stops show up as performance loss. Lead time sits outside OEE — it captures the waiting between steps that OEE does not see — which is exactly why the two metrics are complementary. A line can post strong OEE while lead time remains poor because work queues between otherwise-efficient stations. Reading OEE for the processing efficiency and lead time for the flow gives a fuller picture than either alone, and connects to the waste view in six big losses vs seven wastes.
Fabrico measures cycle time and the performance losses around it directly — actual versus ideal rate, micro-stops, speed loss — so you can see where processing is slower than it should be. By exposing where time is genuinely lost at the machine versus where units are simply waiting, it helps teams tell a cycle-time problem from a flow problem and aim improvement at the right one. Book a demo to see your real cycle times and performance losses on live equipment.
Cycle time is how long it takes to produce one unit at a process or line — an internal measure. Lead time is the total time from a customer request to delivery — an external measure that includes cycle time plus all the waiting, queuing, and movement around it.
Almost always, and usually by a wide margin. Lead time includes the actual processing (cycle time) plus all the non-value-added waiting between and around steps, which typically dominates the total.
Because most of the elapsed time is waiting, not working — units sitting in queues, waiting for a batch to fill, or waiting for the next step or shift. Reducing batch sizes and inter-step queues usually cuts lead time far more than speeding up processing.
Focus on cycle time when a processing step is the genuine constraint. Focus on lead time when customers wait longer than the actual work justifies — which is common, and is fixed by attacking the waiting rather than the processing.
Cycle time drives the performance factor of OEE, which compares actual cycle time to the ideal. Lead time sits outside OEE because it captures waiting between steps, making the two metrics complementary.
Login
Blog
