Cycle Time, Takt Time, and Lead Time are related but they answer different questions.
The simplest distinction is:
- Cycle Time = how fast the process actually completes a cycle.
- Takt Time = how fast the customer requires output.
- Lead Time = how long the job spends in the total system.
Cycle Time
Cycle Time measures the actual time required for a process or operation to complete one cycle.
For example, a workstation completes one unit every 55 seconds.
Cycle time describes process performance. It may vary by product, operator, machine condition, and method.
Takt Time
Takt Time is calculated from available production time divided by customer demand.
For example:
420 available minutes ÷ 420 units = 1 minute per unit
Takt is a demand rhythm. It does not automatically describe how fast the process currently operates.
Lead Time
Lead Time measures total elapsed time from a defined start to a defined finish.
It includes processing, waiting, transport, queues, and approvals.
A product may have a 55-second cycle time at one operation but still have a three-day production lead time.
Compare cycle time with takt
If cycle time is greater than takt, the process may not keep up with required demand.
For example:
- takt = 60 seconds;
- cycle time = 72 seconds.
The process is slower than the required rhythm.
Line Balancing can help distribute work content across stations so the line can operate closer to takt.
Understand why low cycle time does not guarantee low lead time
A fast operation can still feed a large queue.
If every station produces whenever it can, the system may accumulate WIP, waiting, and long lead time.
Work in Process should therefore be considered together with local cycle time.
Use the three measures together
A useful management view might ask:
- Can the operation meet takt?
- Where is cycle time unstable?
- How much WIP is waiting?
- What is the end-to-end lead time?
Little’s Law connects WIP, throughput, and lead time at the system level.
This helps explain why excess WIP can create long customer waiting even when individual operations are fast.
Example
Suppose customer demand requires one unit every 60 seconds, workstation cycle time is 50 seconds, and product spends eight hours in the value stream.
The workstation can theoretically keep pace with demand, but the total process still contains substantial waiting. The improvement focus should not be limited to making the 50-second operation faster.
Common mistakes
Calling takt time a target cycle time without understanding demand, measuring one machine cycle and calling it total lead time, reducing cycle time while WIP grows, ignoring available production time in takt calculation, and using all three terms interchangeably are common mistakes.
Practical sequence
- calculate takt from demand.
- measure actual cycle time.
- compare cycle with takt.
- define total lead-time boundaries.
- measure WIP and waiting.
- identify the system constraint.
- improve unstable or overloaded operations.
- reduce queues.
- recheck lead time.
- manage the three measures as a connected system.
The practical lesson
Cycle Time tells you how fast the process works. Takt Time tells you how fast demand requires it to work. Lead Time tells you how long the customer or job waits for the whole system.