Takt time, cycle time, and lead time get used almost interchangeably in casual floor conversation, and it causes real confusion, because the three numbers can point in completely different directions at the same time. A line can have plenty of cycle time to spare and still miss every due date, or run a cycle time nobody thinks is a problem while steadily falling behind demand every single day. Knowing which one is actually broken is the difference between fixing the right thing and speeding up a machine that was never the bottleneck.
The one line version of each
Takt time is how often a unit needs to come off the line to keep up with customer demand. It’s not measured, it’s calculated from a target: available production time divided by demand.
Cycle time is how long a process actually takes to produce one unit, measured at the machine or the station. It’s a fact about your equipment and your process, not a target.
Lead time is how long a unit spends in the system from the moment work starts on it to the moment it’s done and ready to ship. It includes cycle time plus every minute spent waiting: queued behind another job, sitting in front of a machine, waiting on an inspection.
Takt time, the pace demand sets
Takt is the German word for the beat a conductor sets for an orchestra, and that’s exactly the right mental image: it’s not a measurement of how fast anything currently runs, it’s the pace the customer needs, whether or not the line is hitting it yet.
Takt time = Available production time / Customer demand
Say a line has 420 minutes of available production time in a shift after breaks, and demand is 280 units a day. Takt time is 420 divided by 280, or 1.5 minutes. To meet demand exactly, a finished unit needs to leave the line every 1.5 minutes, no faster and no slower needed, just that pace, sustained.
Cycle time, what the process actually does
Cycle time is a measurement, not a target. Time the actual process, part start to part start, on the slowest station in the line, since that station is the line’s constraint and sets the pace for everything downstream of it.
If the slowest station in that same line has a measured cycle time of 1.8 minutes per unit, the line cannot hit its 1.5 minute takt time no matter how well everything else runs, because the bottleneck station is slower than the beat demand is setting. That’s a real, specific gap: 0.3 minutes per unit. Over a 420 minute shift, running at 1.8 minutes a unit produces about 233 units against a target of 280, a shortfall of roughly 47 units every single day.
A line running under takt, cycle time faster than takt time, isn’t automatically a good thing either. It usually means the line is overbuilt for current demand, spending labor and machine time producing capacity nobody’s asking for, which is its own kind of waste, just a quieter one than falling behind.
Takt time also isn’t fixed. It moves whenever demand or available time changes, and a schedule that doesn’t get revisited when demand shifts is comparing the line against a stale target. A plant that lands a big new order and doubles daily demand to 560 units, with the same 420 minutes available, has just cut its takt time in half, to 45 seconds. That line hasn’t gotten slower overnight, its target has gotten tighter, and the gap between takt and the measured cycle time needs to be recalculated against the new number, not the one from last quarter’s demand plan.
Lead time, everything the customer’s unit actually experiences
Lead time is the number a customer feels. It’s the full span from when a job starts to when it’s done, and it’s almost always dramatically longer than the sum of every process’s cycle time, because most of a job’s life in a shop is spent waiting, not being worked on.
Take a part that moves through four operations, each with a cycle time of 3 minutes. Add those up and you’d expect the part to move through the shop in 12 minutes. In practice, that part might sit in queue in front of each operation for hours, waiting for a machine to free up, waiting for a batch to accumulate, waiting for the previous job to finish. A lead time of two or three days on a part whose total processing time is 12 minutes isn’t unusual in a job shop, and the gap between those two numbers is entirely queue time, not process time.
Why chasing the wrong one wastes real effort
A shop that’s missing due dates often reaches for the same fix: speed up cycle time, push harder, tune the program, add a second shift on the bottleneck. If the actual problem is lead time driven by queue and scheduling, that effort barely moves the number, because the 12 minutes of process time was never where the two days went. The fix for a queue problem is dispatching and prioritization, not a faster machine.
The reverse mistake happens too. A line missing takt time gets treated as a scheduling problem, more expediting, more chasing, when the real issue is that the slowest station’s cycle time is actually too slow to hit the beat demand is setting, no amount of expediting fixes a station that’s mechanically slower than what’s needed.
Telling the three apart before choosing a fix is the entire point of naming them separately. A takt time gap points at the process and the equipment. A lead time gap points at scheduling, batching, and queue discipline. Confusing the two means solving the wrong problem convincingly.
Putting all three on the same line
The most useful diagnostic isn’t picking one of these numbers, it’s comparing all three at once. Takt time tells you the pace demand requires. Cycle time at the bottleneck tells you whether the process can physically hit that pace. Lead time tells you how much of a customer’s actual wait has nothing to do with the process at all and everything to do with how work gets sequenced and prioritized on the floor. A line can look completely healthy on cycle time and still be losing customers on lead time, and that gap is where a scheduling and dispatch view, not a stopwatch on the machine, earns its keep.
Quick recap
- Takt time is a target: available time divided by demand, how often a unit needs to finish to keep up
- Cycle time is a measurement: how long the slowest station actually takes per unit
- Lead time is everything a unit experiences: cycle time plus every minute spent waiting in queue
- Cycle time slower than takt time means the line cannot meet demand, no matter how the rest of it runs
- Lead time is almost always dominated by queue time, not process time, especially in high-mix shops
- Diagnose before fixing: a takt gap points at the process, a lead time gap points at scheduling and dispatch