Executive summary: Takt time is the rhythm of customer demand: available production time divided by customer demand for that period. It is not how fast your machines run and not how long an order takes to reach the customer. Those are cycle time and lead time, and confusing the three is one of the most common errors in manufacturing analysis. This guide gives the formula, the two inputs people get wrong, a worked example, and what to do when a station’s cycle time exceeds takt.
- What is takt time?
- How do you calculate takt time?
- What does the calculation look like worked through?
- What is the difference between takt, cycle, and lead time?
- What do you do when cycle time exceeds takt time?
- Should you run at takt or slightly under it?
- What are the most common takt time mistakes?
- Takt time: operator FAQ
- About the Stagnation Assassin
What is takt time?
Takt time is the rate at which you must complete one unit to exactly meet customer demand. It equals available production time divided by customer demand for that same period. It is a demand rhythm, not a machine speed, which is why it is set entirely by the customer and not by anything happening inside your plant.
The word comes from the German Takt, meaning beat or pulse, and it entered manufacturing through the Toyota Production System. The metaphor is musical. Takt is the metronome the whole operation plays to. Run faster than the beat and you produce inventory nobody ordered. Run slower and you miss deliveries. Neither is a small problem, and most plants do one of them constantly without ever naming it.
Here is the part that trips people up, and it is worth being blunt about it. Takt time has nothing to do with your capability. You do not calculate it from your equipment, your headcount, or your historical output. You calculate it from what customers want and how much time you have to make it. It is an external target handed to you by the market. What you control is whether your processes can meet it.
That distinction matters because of what it enables. Once you have a takt time, every process in the plant can be measured against a single objective standard. A station that runs faster than takt has spare capacity. A station that runs slower than takt is limiting your ability to serve demand, which makes it a candidate for your constraint. Without takt, you are comparing stations to each other and to their own history, which tells you who is fastest but never tells you who is fast enough.
How do you calculate takt time?
Divide net available production time by customer demand for the same period. Net available time excludes breaks, planned meetings, and scheduled maintenance, but not unplanned downtime. Customer demand means actual orders, not forecast or capacity. Both inputs are routinely calculated wrong, and either error alone invalidates the result.
The formula itself is trivial. Getting the two inputs honest is where the work is.
Input 1: net available production time
Start with scheduled shift time, then subtract time the line is legitimately not available to produce: scheduled breaks, shift-start meetings, planned changeovers if they are scheduled, and planned maintenance windows. What you do not subtract is unplanned downtime, breakdowns, or micro stoppages. Those are performance losses you are trying to eliminate, and burying them in the takt calculation hides them.
This is the single most common place people get it wrong, and the error always runs the same direction. Teams subtract their actual downtime, which inflates takt time, which makes their processes look adequate when they are not. If you subtract breakdowns from available time, you have quietly redefined your problem as a constant.
Input 2: customer demand
Use real customer demand for the period, not the sales forecast and not what your plant is capable of producing. If customers order 430 units a day, demand is 430. Not the 500 the forecast promised, and not the 600 the line could run. Takt exists to synchronize you to the market, so feeding it internal numbers defeats the entire point.
Where demand genuinely varies, calculate takt over a stable window, typically weekly or monthly, and recalculate when demand shifts materially. Recalculating daily against a volatile order book produces a target that changes faster than the plant can respond to it, which is worse than useless.
What does the calculation look like worked through?
With two shifts of 480 minutes each, less 50 minutes per shift of breaks and meetings, net available time is 51,600 seconds. Against daily customer demand of 430 units, takt time is 120 seconds. That means the plant must complete one finished unit every two minutes to meet demand exactly, no faster and no slower.
Walk the arithmetic all the way through, because the unit conversions are where errors creep in.
Step one, gross shift time. Two shifts at 8 hours each is 960 minutes of scheduled time.
Step two, subtract non-available time. Each shift loses two 15-minute breaks and a 20-minute startup meeting, so 50 minutes per shift, 100 minutes across both shifts. Net available time is 860 minutes.
Step three, convert to seconds. 860 minutes times 60 gives 51,600 seconds of net available production time per day.
Step four, divide by demand. 51,600 seconds divided by 430 units of daily customer demand gives a takt time of 120 seconds per unit.
Now the number does real work. Every station in the line gets measured against 120 seconds. A station cycling at 95 seconds has headroom. A station cycling at 118 seconds is uncomfortably close with no margin for variation. A station cycling at 140 seconds cannot meet demand, full stop, and no amount of effort elsewhere in the plant will fix that. It is limiting the system, and it is where your attention belongs.
What is the difference between takt, cycle, and lead time?
Takt time is the demand rhythm set by customers. Cycle time is how long a process actually takes to complete one unit. Lead time is total elapsed time from order or material entry to delivery, including all waiting. Takt is a target, cycle is a capability, and lead time is the customer’s experience of both.
These three get used interchangeably in conversation and they mean completely different things. Getting them straight changes what you measure and what you fix.
Takt time: what the customer requires
Externally set, calculated from demand and available time. It never depends on how your plant performs. If demand rises, takt shortens and the beat gets faster. If you add a shift, available time rises and takt lengthens. It answers: how often must a unit come off the line?
Cycle time: what a process delivers
Internally set, measured with a stopwatch at each station. Every process has its own cycle time. The longest cycle time in the flow determines how fast the line can actually run, which is why the slowest station and the constraint are usually the same thing. It answers: how long does this step actually take?
Lead time: what the customer experiences
Total elapsed time from order placement or material release through to delivery, including every queue, inspection, transport, and rework loop. This is almost always vastly longer than the sum of cycle times, because most of a unit’s life is spent waiting rather than being worked on. It answers: how long does the customer wait?
The gap between the sum of cycle times and total lead time is the number that shocks executives, and it should. A unit that takes four hours of actual processing routinely spends eighteen days in the plant. That is not a processing problem. That is a queuing problem, and queues form in front of constraints.
Little’s Law makes the relationship precise: lead time equals work in process divided by throughput rate. Which means you have exactly two ways to shorten lead time. Raise throughput, which means fixing the constraint, or cut work in process, which means stopping the plant from releasing material faster than the constraint can consume it. Every genuine lead time reduction is one of those two things. Everything else is rearranging queues.
Little’s Law gives you only two levers on lead time: raise throughput or cut work in process. A plant with 18 day lead times against 4 hours of actual processing does not have a slow process. It has a queue, and the queue exists because material enters faster than the constraint can consume it.
What do you do when cycle time exceeds takt time?
A station cycling slower than takt cannot meet demand and is limiting the system. Fix it in this order: eliminate waste inside that station’s cycle, rebalance work to adjacent stations with headroom, reduce its changeover and downtime losses, and only then add capacity. The order matters, because the first three cost almost nothing.
In the worked example, welding cycles at 140 seconds against a 120 second takt. That gap is not a rounding error. Twenty extra seconds across 430 units is nearly two and a half hours of production time the plant does not have, which is demand it structurally cannot serve. Here is the sequence I use.
First, strip waste out of the cycle itself. Watch the station honestly for an hour. Operators walking to fetch tools, waiting for material, searching for fixtures, doing paperwork mid-cycle. In most stations that have never been studied, a meaningful share of the cycle is not value-adding work at all. This is free capacity and it is usually the largest single chunk available.
Second, rebalance the line. You have stations at 95 and 102 seconds with real headroom against takt. Move discrete elements of welding work to those stations. This is the classic line balancing move, and it converts idle time at fast stations into relief at the slow one without spending anything.
Third, attack losses at that station specifically. Changeover time, unplanned downtime, and micro stoppages all consume capacity at the one place you cannot afford to lose it. Cutting a changeover at a station running below takt is nearly free capacity. The same cut anywhere else is motion. Track the specific losses at that station rather than plant-wide averages, which hide exactly the detail you need.
Only then consider adding capacity. A second welding station, an additional operator, an equipment upgrade. I have watched companies skip straight to this step and commit seven figures to a problem that a week of waste elimination and rebalancing would have solved. Exhaust the free options first, every time.
Should you run at takt or slightly under it?
Run at planned cycle time, which is takt minus a deliberate margin, typically 5 to 15 percent. Designing a line to exactly match takt leaves no room for normal variation, so any hiccup immediately becomes a missed delivery. The margin absorbs ordinary variability without carrying the cost of real excess capacity.
This is a detail most introductions skip, and it causes real damage when missed. If takt is 120 seconds and you design every station to hit exactly 120 seconds, you have built a line with zero tolerance. One quality stop, one material delay, one slightly slow operator, and you are behind, with no mechanism to catch up.
Set planned cycle time at roughly 85 to 90 percent of takt instead. With a 120 second takt, design to 102 to 108 seconds. The margin gets consumed by the variation that will absolutely occur, and on a good day you finish early, which is a far better problem than the alternative.
How much margin depends on your actual stability. A mature line with high availability and low variation can run at 90 to 95 percent of takt. A line with frequent breakdowns, unstable material supply, or heavy product mix needs more, sometimes 80 percent. Set it from measured variability, not from optimism. And if the required margin is embarrassingly large, that is the real finding: your problem is not takt, it is reliability, and that is where the work belongs.
A line designed to hit takt exactly has no tolerance for the variation that will certainly occur. Design instead to 85 to 90 percent of takt. If the margin your line actually needs is 20 percent or more, the finding is not a scheduling problem, it is a reliability problem, and the fix belongs in downtime and quality, not in the takt calculation.
What are the most common takt time mistakes?
Four errors account for most bad takt calculations: subtracting unplanned downtime from available time, using forecast instead of actual demand, applying a single takt to a high-mix line with wildly different work content, and calculating takt once and never revisiting it as demand moves.
Mistake 1: subtracting breakdowns from available time
Teams remove actual downtime from available time because it feels realistic. It inflates takt time and makes inadequate processes look adequate. Subtract only planned unavailability: breaks, meetings, scheduled maintenance. Unplanned downtime is a loss you are trying to eliminate, and hiding it inside takt guarantees you never will.
Mistake 2: using forecast or capacity as demand
Using the sales forecast gives you a takt synchronized to a spreadsheet rather than to customers. Using plant capacity is worse, because it makes takt a function of your own equipment, which defeats the purpose entirely. Use actual customer demand over a stable window.
Mistake 3: one takt for a high-mix line
A single takt time assumes reasonably consistent work content per unit. On a line running products with dramatically different work content, one takt is meaningless. Either calculate takt by product family, or convert to a work-content-weighted equivalent unit. Applying one number across genuinely different products produces confident nonsense.
Mistake 4: calculating it once
Takt is a function of demand, and demand moves. A takt time calculated in January against a January order book is wrong by March if volume shifted materially. Recalculate on a defined cadence and whenever demand changes meaningfully. A stale takt quietly misdirects every balancing and staffing decision made against it.
The mistake I made personally, early on, was treating takt as a scheduling exercise rather than a communication tool. I calculated it correctly, published it, and assumed the floor would organize around it. Nothing happened, because nobody on the floor could see whether they were ahead or behind at any given moment. The fix was visual: a simple display at each station showing target versus actual against the beat. The calculation was never the hard part. Making the beat visible in real time was what changed behavior.
Takt time: operator FAQ
What is the takt time formula?
Net available production time divided by customer demand for the same period. Net available time excludes planned breaks, meetings, and scheduled maintenance, but never unplanned downtime. For example, 51,600 seconds of net available time against 430 units of daily demand gives a takt time of 120 seconds per unit.
What is the difference between takt time and cycle time?
Takt time is set by customer demand and tells you how often a unit must be completed. Cycle time is set by your process and tells you how long a station actually takes. Takt is the target, cycle is the capability. A station whose cycle time exceeds takt cannot meet demand and is limiting the system.
Should cycle time be equal to takt time?
No, it should be slightly below. Design to roughly 85 to 90 percent of takt so normal variation does not immediately turn into missed deliveries. A line built to match takt exactly has zero tolerance, so one quality stop or material delay puts it behind with no way to recover.
Does takt time apply to high-mix low-volume production?
Only with adjustment. A single takt time assumes reasonably consistent work content per unit. On high-mix lines, calculate takt by product family or convert to a work-content-weighted equivalent unit. Applying one takt across products with dramatically different work content produces a number that looks precise and means nothing.
About the Stagnation Assassin
Todd Hagopian is a Fortune 500 transformation executive who has generated $3B+ in shareholder value across Berkshire Hathaway, Illinois Tool Works, Whirlpool, and JBT Marel, where he serves as VP of Global Product Strategy. Known as The Stagnation Assassin, he is the author of two published books: The Unfair Advantage: Weaponizing the Hypomanic Toolbox and Stagnation Assassin: The Anti-Consultant Manifesto. His blog is published in 15+ languages and read by operators worldwide. Bring him to your stage via the speaking page or connect with him on LinkedIn.
Next step: a takt and constraint check
If you cannot name your takt time in one sentence, your plant is running to a beat nobody set. Book a 20 minute check and I will help you calculate takt honestly, measure your stations against it, and find the one that is quietly capping what you can deliver. Start the check here.