Three different clocks are running on your production line at once — and mixing them up is one of the most common scheduling mistakes in operations.
People use "takt time," "cycle time," and "lead time" almost interchangeably in casual conversation, and it causes real damage on the shop floor: a team celebrates a fast cycle-time number while customers are still waiting weeks for delivery, or a line gets "balanced" to a number that has nothing to do with what customers are actually buying. Each term answers a genuinely different question, and a healthy production system needs all three to line up correctly — not just one of them to look good.
Takt time — "how often does a unit need to come off the line?" Takt time is a target, not a measurement. It's calculated purely from customer demand: available production time divided by demand over that period. A shift with 480 minutes available and a daily demand of 240 units needs a finished unit every 480 / 240 = 2 minutes. Nothing about the process itself enters that calculation — takt time would change if demand changed, even if the process never did.
Cycle time — "how long does this station actually take?"Cycle time is a measured, observed property of a process step, as it's actually performed today. It has nothing to do with demand — a station's cycle time is whatever a stopwatch says it is, whether customers want one unit a year or one a minute.
Lead time — "how long from order to delivery?"Lead time is the total elapsed time from when a unit of work is started (an order placed, a job released to the floor) until it's finished and delivered. It includes every station's cycle time, but it also includes everything else that happens to that unit along the way — queueing behind other work, waiting for a batch to accumulate, sitting in a buffer between stations. In almost every real system, that "everything else" dwarfs the actual processing time.
That relationship is straightforward: keep every station's cycle time at or below takt time and the line keeps up with demand. But now suppose Welding gets fixed — every single station comfortably beats takt time. Does that mean an order now moves through the plant quickly? Not necessarily. That question is answered by lead time, and lead time runs on a completely different clock.
Little's Law makes the relationship explicit: Lead Time = Work-in-Process ÷ Throughput. Throughput is capped by the bottleneck station's cycle time relative to takt — that's the first diagram. But lead time also scales directly with however much work-in-process (WIP) is sitting in queues between stations — and that number has nothing to do with any individual station's cycle time. A line can hit every cycle-time target and still drown an order in queue time simply because too much WIP is piling up between steps, whether from batch-and-queue scheduling, unbalanced station speeds feeding a slower one downstream, or excess buffer stock carried "just in case." This is exactly why lean manufacturing spends so much energy on flow — one-piece flow, kanban limits, pull systems — targeting queue time and WIP directly, rather than only chasing faster individual process steps.
False, and the timeline above is exactly why. In most real production and service systems, the majority of total lead time is consumed by queueing and waiting between process steps — not by actual processing. A line with excellent individual cycle times at every station can still have a very long overall lead time if work-in-process piles up in the queues between them, whether from batch-and-queue scheduling, unbalanced line speeds, or excessive buffer stock carried between stations. Fast cycle times are necessary to keep pace with takt; they are not sufficient to guarantee a fast lead time.That's precisely why lean and flow-focused improvement efforts target reducing WIP and queue time specifically — not just speeding up individual operations that were never the real constraint on lead time to begin with.
Takt time, cycle time, and lead time answer three different questions about a production line, and confusing them is a common source of bad scheduling decisions. Takt time is a target pace derived purely from customer demand (available time ÷ demand) — it says nothing about the process itself. Cycle time is the actual, measured time a process step takes as it's currently performed, independent of demand. Lead time is the total elapsed time from when a work item starts until it's delivered, and it includes not just processing time but all the queueing and waiting in between — which, in most real systems, is where nearly all of the lead time actually lives.
For a line to keep up with customer demand, the cycle time at every station must be at or below takt time. If any single station's cycle time exceeds takt time, that station becomes the bottleneck — the entire line can only produce as fast as its slowest step, regardless of how quickly every other station runs. Line balancing, in the lean-manufacturing sense, means redistributing work (or adding capacity) so that every station's cycle time sits comfortably at or under takt, with the bottleneck station typically closest to the takt line since it sets the pace.
Lead time is not the sum of cycle times — it's the sum of cycle times plus every queue, wait, and buffer delay a unit passes through on its way from order to delivery. Little's Law formalizes this: Lead Time = Work-in-Process ÷ Throughput. Throughput is capped by the bottleneck's cycle time relative to takt, but lead time also scales directly with how much WIP is sitting in queues — a variable that has nothing to do with any individual station's cycle time. A line can have excellent cycle times everywhere and still deliver painfully slowly if batch-and-queue scheduling, unbalanced station speeds, or excess buffer stock let WIP pile up between steps.
This is why lean improvement efforts (single-piece flow, kanban pull systems, WIP caps, SMED-driven smaller batch sizes) target queue time and work-in-process directly, rather than only chasing faster individual operations. A value stream map makes the split visible by charting each station's cycle time against the queue/wait time that follows it, then computing process cycle efficiency — value-added (processing) time divided by total lead time — which in most unoptimized systems comes out in the low single digits.
No. Takt time is a target pace derived from customer demand (available production time ÷ demand) — it exists even if no process has been designed yet. Cycle time is a measured property of an actual process step. The goal of line design is to bring cycle time at or under takt time, not to treat them as the same number.
Not by itself — a station well under takt time simply has slack capacity relative to demand. Problems appear when a station exceeds takt time (it becomes the bottleneck) or when uneven cycle times across stations cause WIP to pile up in the queue in front of the slower one, which increases lead time even without a takt violation.
Because in real production and service systems, work spends most of its time waiting, not being processed — queued behind other jobs, waiting for a batch to accumulate, sitting in a buffer between stations. Process cycle efficiency (value-added time ÷ total lead time) is frequently under 10% in unoptimized systems, meaning over 90% of lead time is non-processing wait time.
Little's Law states Lead Time = WIP ÷ Throughput. If throughput (set by the bottleneck relative to takt) stays fixed, the only way to reduce lead time is to reduce WIP — meaning less work sitting and waiting in queues at any given moment. That is exactly what kanban limits, smaller batch sizes, and pull-system scheduling are designed to do.
Yes. Meeting takt time at every station only guarantees the line's throughput matches demand on average. It says nothing about how long any individual order sits in queue between stations. A line can be perfectly takt-balanced and still have a long, unpredictable lead time if WIP levels and queueing are not separately managed.
Try our Industrial & Systems Engineering Studio
More calculators, simulators, and guides for this discipline.