Takt time is the pace at which you must produce to meet customer demand — total available time ÷ customer demand. Cycle time is the actual time it takes to produce one unit. If cycle time exceeds takt time, you can’t keep up with demand. If cycle time is much shorter, you’re building excess inventory.
Cycle time measures the total time to complete one production cycle, while takt time dictates the pace needed to meet customer demand. Aligning cycle time with takt time is essential for optimizing efficiency, reducing waste, and ensuring timely delivery.
Takt Time vs. Cycle Time: The One-Line Difference
The one-line difference is simple: takt time is demand-driven, while cycle time is process-driven. Takt time is calculated from available production time and customer demand. Cycle time is measured from the actual process and represents how long it takes to produce a unit or complete a repeating work cycle.
That distinction matters because the two metrics answer different questions. Takt time asks, “How often must we complete a unit to satisfy customer demand?” Cycle time asks, “How often are we actually completing a unit?”
Lean Enterprise Institute defines takt time as available production time divided by customer demand, and describes it as the heartbeat used to match production with demand. It defines cycle time as the time required to produce a part or complete a process, based on actual measurement.
A process may therefore have a takt time of two minutes per unit but a cycle time of 2.4 minutes per unit. The customer requires one unit every two minutes, but the process can only deliver one every 2.4 minutes. Unless something changes, demand will eventually exceed the process’s output capability.
The reverse can also occur. If cycle time is 1.5 minutes while takt is two minutes, the process is capable of producing faster than current demand. That extra capability may provide useful capacity, but continuously running faster than takt without a downstream need can create overproduction, excess inventory, and additional handling.
The goal is not necessarily to make cycle time numerically identical to takt time every second of the day. The practical goal is to design a stable process with enough capability to meet takt reliably while avoiding unnecessary overproduction.
Takt Time Explained (With Formula)
Takt time is the rate at which finished units need to be produced to match customer demand. The word “takt” comes from German and refers to a beat or rhythm. In Lean manufacturing, takt time provides a demand-based production rhythm that helps teams align people, equipment, and standardized work.
The basic formula is:
Takt Time = Available Production Time ÷ Customer Demand
The time units must be consistent. If available time is measured in minutes per shift, takt will be expressed in minutes per unit. If time is measured in seconds, takt will be expressed in seconds per unit.
What counts as available production time?
Available production time is the time actually available for production during the period being analyzed. Planned breaks, lunches, meetings, planned maintenance, or other known non-production periods are normally removed if operators cannot produce during those periods.
For example, an eight-hour shift contains 480 clock minutes. If the workforce has two 10-minute breaks and a 30-minute lunch, the available production time would be 430 minutes if those periods are fully unavailable for production.
This distinction is important. Using scheduled clock time instead of genuinely available production time can make takt appear more generous than it really is.
What demand should be used?
The denominator should represent customer demand for the same period as the available time. If the calculation uses one shift of available time, the demand should also be expressed per shift. If demand is 240 units per day and there is one production shift per day, daily demand can be used directly.
Demand should be based on the rate the process is expected to support, not simply on the maximum quantity the machine could make. Takt is therefore a customer-demand metric rather than an equipment-speed metric.
Takt time example
Suppose a production line has 450 minutes of available production time and customer demand is 225 units per shift.
Takt Time = 450 minutes ÷ 225 units = 2 minutes per unit
The process must therefore complete approximately one good unit every two minutes to match demand. If actual cycle time is consistently longer than two minutes, the line will struggle to keep pace.
Cycle Time Explained (With Formula)
Cycle time measures the actual pace of a process. Lean Enterprise Institute defines it as the time required to produce a part or complete a process, as timed by actual measurement. Depending on the context, cycle time can refer to the repeating work cycle of an operator, a machine’s operating cycle, or an end-to-end process segment.
For an output-based calculation over a period, a common formula is:
Cycle Time = Total Production Time ÷ Units Produced
For example, if a process produces 180 units during 360 minutes of operating time:
Cycle Time = 360 minutes ÷ 180 units = 2 minutes per unit
Cycle time can also be measured directly with a stopwatch or digital system. If an operator repeats the same work sequence, the time from the beginning of one cycle to the beginning of the next can be observed across multiple cycles and averaged or analyzed for variation.
Cycle time can mean different things
Cycle time is sometimes used loosely, so the measurement boundary should be explicit. A machine cycle time may exclude operator loading and unloading. Operator cycle time may capture the manual work sequence at a workstation. An effective machine cycle time may include loading, unloading, and a share of changeover time.
This is one reason cycle-time comparisons can become misleading when teams use different definitions. Always document where the timing starts, where it ends, whether waiting is included, and whether the result represents one operator, one machine, one workstation, or a broader process.
Cycle time is not lead time
Cycle time should also not be confused with lead time. Cycle time typically focuses on the time required to perform or repeat a production step. Lead time measures the broader elapsed time from a request or order until completion or delivery and can include waiting, queues, transportation, approvals, and inventory time.
A factory may therefore have a two-minute production cycle time but a customer lead time of several days if orders spend most of their time waiting between processes.
Also Called: Cycle Time vs. Takt Time (Same Concepts, Reversed Order)
“Cycle time vs. takt time” and “takt time vs. cycle time” describe the same comparison. Reversing the order of the terms does not change their meaning, formulas, or relationship.
People often search the concepts in both directions because the terms are easy to confuse. The simplest way to remember them is:
- Takt time = the pace demand requires.
- Cycle time = the pace the process actually achieves.
If a process has takt time of 60 seconds and cycle time of 50 seconds, the process is capable of completing work faster than the demand rate. If cycle time is 70 seconds, the process is slower than the required pace.
The comparison becomes especially useful when displayed by workstation. A Lean team can place each station’s cycle time beside a horizontal takt-time reference line. Stations above the takt line require more time than demand allows and may become bottlenecks. Stations well below the line may have excess capacity or an imbalanced work assignment.
Comparing the Two: What the Gap Tells You
The gap between takt time and cycle time is a quick diagnostic of whether current process capability aligns with demand. It does not explain every operational problem, but it shows where further investigation is needed.
| Condition | What it means | Likely implication |
| Cycle time < Takt time | Process is faster than the required demand pace | Potential capacity cushion; avoid producing ahead unnecessarily |
| Cycle time ≈ Takt time | Process pace is close to demand pace | Good balance if the process is stable and variation is controlled |
| Cycle time > Takt time | Process is slower than required | Backlog, missed output, overtime, or bottleneck risk |
When cycle time is longer than takt time
If cycle time exceeds takt, the process cannot consistently meet the required demand rate under the current conditions. Typical responses include removing non-value-added work, rebalancing tasks, improving standardized work, reducing downtime, simplifying motion, adding appropriate resources, improving equipment reliability, or redesigning the process.
Simply asking operators to work faster is not a Lean solution. The objective is to improve the system so the work can be completed safely, repeatedly, and with the required quality within takt.
When cycle time is much shorter than takt time
A cycle time well below takt can indicate useful spare capacity, but it can also expose overproduction if the process continues running at maximum speed regardless of downstream demand. Overproduction is especially problematic because it creates inventory that can hide defects, consume floor space, increase handling, and disconnect upstream work from customer need.
Lean systems often use pull mechanisms, standard work, and production leveling so processes operate in response to demand instead of simply maximizing local machine utilization.
Variation matters too
An average cycle time below takt does not guarantee success. Suppose takt is 60 seconds and average cycle time is 55 seconds, but actual cycles frequently range from 40 to 75 seconds. The average looks acceptable, yet the frequent long cycles can disrupt flow and create downstream shortages.
For this reason, teams should evaluate both the average cycle time and its stability. Standardized work, visual management, quality at the source, and problem-solving help reduce variation so meeting takt becomes repeatable rather than occasional.
Worked Example: 8-Hour Shift, 240 Units Demand
Consider a production line operating one eight-hour shift with customer demand of 240 units. For the simplest illustration, assume all 480 minutes are available for production.
Available production time = 8 hours × 60 minutes = 480 minutes
Customer demand = 240 units
Takt Time = 480 minutes ÷ 240 units = 2 minutes per unit
The customer-demand rhythm is therefore one completed unit every two minutes. This is the same basic example used by Lean Enterprise Institute to illustrate takt time.
Scenario 1: cycle time is 1.8 minutes
If the line’s actual cycle time is 1.8 minutes per unit, the process is faster than takt by 0.2 minute, or 12 seconds, per unit.
At that speed, theoretical output across 480 production minutes would be:
480 ÷ 1.8 = approximately 267 units
The process has enough theoretical capacity to meet 240-unit demand. In a pull-based Lean environment, however, that does not mean the line should automatically produce all 267 units. Producing beyond demand would create unnecessary inventory unless there is a justified replenishment requirement.
Scenario 2: cycle time is 2.2 minutes
If actual cycle time is 2.2 minutes per unit, the process is slower than takt by 0.2 minute, or 12 seconds, per unit.
Theoretical output would be:
480 ÷ 2.2 = approximately 218 units
That leaves an output gap of approximately 22 units compared with 240-unit demand. The team must either improve the process, add appropriate capacity, change the work balance, extend available production time, or otherwise address the mismatch.
| Metric / scenario | Calculation | Result | Interpretation |
| Takt time | 480 min ÷ 240 units | 2.00 min/unit | Required demand pace |
| Cycle time – faster case | 1.80 min/unit | ≈267-unit theoretical capacity | Enough capacity; avoid unnecessary overproduction |
| Cycle time – matched case | 2.00 min/unit | 240-unit theoretical capacity | Matches demand exactly in the simplified case |
| Cycle time – slower case | 2.20 min/unit | ≈218-unit theoretical capacity | About 22 units short of demand |
More realistic version with breaks
Now assume the eight-hour shift includes 50 minutes of planned non-production time. Available production time becomes 430 minutes rather than 480.
Takt Time = 430 minutes ÷ 240 units = 1.79 minutes per unit, or approximately 107.5 seconds
The process now needs to complete units more frequently because the same customer demand must be met in less available production time. This illustrates why takt calculations should use true available production time rather than nominal shift length whenever planned breaks or other non-production periods apply.
How to Use Both Metrics in Lean
Takt time and cycle time are most useful when they are used together. Takt provides the customer-demand reference. Cycle time reveals actual process performance. Lean teams compare them to design work, balance production, expose bottlenecks, and guide continuous improvement.
1. Establish takt from current demand
Start with a clearly defined demand period and the genuinely available production time for that period. Recalculate takt when meaningful changes in demand, working time, or production structure occur. Lean Enterprise Institute notes that takt is used to match production precisely with demand rather than to maximize output independently of demand.
2. Measure cycle time at each key process
Observe the actual repeating cycle rather than relying only on engineered standards or historical assumptions. Capture several cycles when possible so the team can see both average performance and variation.
3. Compare each cycle with takt
Processes above takt are immediate candidates for analysis because they may prevent the value stream from meeting demand. Processes well below takt should also be examined for workload balance and overproduction risk.
4. Balance standardized work
Lean standardized work is built around takt time, work sequence, and standard inventory. By comparing work content with takt, teams can redistribute tasks among operators, remove wasted motion, simplify handoffs, and design a repeatable sequence that supports the required pace.
5. Use the gap to prioritize kaizen
If cycle time is above takt, do not treat the difference as merely a worker-speed problem. Observe the process and look for waiting, walking, searching, defects, rework, awkward motion, setup losses, machine downtime, material shortages, or unbalanced task content. These causes create concrete targets for kaizen.
6. Connect takt with flow and pull
Takt provides the rhythm, but Lean performance also depends on flow and pull. When a process can meet takt, one-piece flow or small-lot flow can reduce waiting and inventory. Kanban can regulate replenishment so upstream processes make what has actually been consumed rather than producing ahead simply because capacity is available.
7. Monitor changes instead of treating the numbers as fixed
Customer demand changes, product mix changes, staffing changes, and equipment conditions change. Takt and cycle time should therefore be treated as operating metrics rather than one-time calculations. When the takt requirement tightens, the team may need new balancing or improvement. When demand falls, maintaining the old output rate can create overproduction.
Used together, takt time and cycle time give Lean teams a simple but powerful operating question: Is the process actually capable of working at the pace the customer requires, with stable quality and without creating waste?
Conclusion
Takt time and cycle time are closely related, but they measure different sides of production performance. Takt time translates customer demand into the pace the process must support, while cycle time measures the pace the process actually achieves. Comparing the two immediately shows whether capacity is aligned with demand and helps Lean teams identify bottlenecks, rebalance work, prevent overproduction, and focus kaizen where it matters most. The comparison becomes even more valuable when cycle-time variation, standardized work, flow, and pull are considered alongside the averages. In practical terms, takt tells the operation where the finish line is; cycle time tells the team whether the current process can reach it consistently.
Frequently Asked Questions
What is a Kanban inventory system?
A Kanban inventory system uses visual signals — cards, bins, or digital triggers — to pull stock only when demand consumes it. When inventory falls to a preset trigger point, a Kanban card requests replenishment. This prevents overstocking and stockouts.
How do you calculate the number of Kanban cards?
“Number of Kanban cards = (Average daily demand × Lead time × Safety factor) ÷ Container quantity. Safety factor typically ranges 1.1 to 1.5 depending on demand variability.
What is the difference between two-bin and three-bin Kanban?
Two-bin Kanban uses one active bin and one reserve bin — when the active bin empties, replenishment is triggered and the reserve bin becomes active. Three-bin Kanban adds a third bin as extra safety stock, useful when suppliers have variable lead times.
Can Kanban be digital instead of physical cards?
Yes. Digital Kanban systems use software to trigger replenishment based on real-time inventory data — often integrated with ERP or WMS. Digital Kanban scales better for large SKU counts and remote suppliers but loses the visual, gemba-friendly signal of physical cards.
