Lean teams use takt time to set the rhythm of a process. It drives line balancing, staffing and standard work. Comparing cycle times against takt shows quickly where a process is overloaded or underused.
Where it comes from
Takt is a German word for a beat or rhythm, as in music. Toyota adopted the concept and made it a basic element of standardized work in the Toyota Production System.
At a glance
Stations compared with takt
Swipe sideways to see the whole diagram.
How to apply Takt Time
- 1
Calculate available time
Take the shift length and subtract planned breaks, meetings and planned maintenance. Do not subtract unplanned downtime, since that is a loss to reduce, not a given.
- 2
Confirm customer demand
Use the demand for the same period, such as units per shift or per day. Base it on real orders or a stable forecast, not on what the line happens to produce.
- 3
Divide time by demand
Takt time equals available time divided by demand. Express it in seconds or minutes per unit so operators can relate it to their work.
- 4
Compare cycle times to takt
Time each step and plot the results against takt, often in a yamazumi chart. Steps above takt are bottlenecks, and steps well below may be combined.
- 5
Balance and staff to takt
Redistribute work elements so each station sits just under takt. Calculate the operators needed by dividing total work content by takt time.
- 6
Make takt visible and revisit it
Show planned versus actual output by hour on a board near the line. Recalculate takt whenever demand or available time changes significantly.
Worked example (illustrative)
An assembly cell runs one 8-hour shift with 30 minutes of breaks, leaving 450 minutes. Demand is 225 units per shift, so takt time is 2 minutes per unit. One station takes 2.5 minutes, so the team moves a sub-assembly task to the next station.
Common mistakes
- Confusing takt time with cycle time, which describes how long the work actually takes.
- Subtracting expected breakdowns from available time, which hides downtime instead of exposing it.
- Calculating takt once and never updating it when demand shifts.
When Takt Time is not the right tool
Takt time is less useful for one-off or very low-volume work, where there is no steady demand rate to match.
With several products on one line, calculate takt on total demand. Then level the mix with heijunka.
Takt time meaning
Takt time is the pace at which you must finish one unit to meet customer demand. Takt is a German word for a beat or a bar in music.
Takt time is set by demand, not by the process. Cycle time is how long the process actually takes. The two are compared to balance the work.
Takt time formula
Takt time equals available production time divided by customer demand in the same period. Available time excludes planned breaks, meetings and lunch.
Use the same units for both, for example seconds per shift and units per shift. The takt time calculator converts the units for you.
How to calculate takt time: an example
Say a shift lasts 480 minutes, with two 10-minute breaks and a 30-minute lunch. Available time is 430 minutes, or 25,800 seconds.
Customers need 430 units per shift. Takt time is 25,800 divided by 430, which is 60 seconds per unit.
Each station's cycle time should sit just under 60 seconds. A station at 75 seconds is a bottleneck, and the line will fall short of demand.
Planned cycle time and pitch
Some plants run slightly faster than takt to cover known losses. They call the target planned cycle time.
Pitch is takt time multiplied by the pack quantity. It sets how often work is released or moved.
How many operators? A worked count
In the illustrative assembly cell, takt is 2 minutes. Timing every work element gives a total work content of 9.4 minutes per unit.
Operators needed = total work content ÷ takt = 9.4 ÷ 2 = 4.7, so the cell needs 5 operators. If the team removes 0.4 minutes of walking and waiting, the work content becomes 9.0 minutes and 4.5 operators, still rounding to 5, but the fifth person now has slack for one more task.
Measuring cycle time: an observation sheet
Comparing cycle time with takt is only as good as the cycle time data behind it, and good data comes from watching the real work. A simple observation sheet keeps a time study consistent from one observer, and one shift, to the next.
Tell the team why you are timing the work, and time the process, not the person. Record a run of cycles rather than one, and note anything unusual instead of quietly leaving it out. These are the fields most studies need:
Cycle time observation sheet
Line ______ · Date ______ · Observer ______
- 1Operation
- The step being timed, with clear start and end points.
- 2Product or part
- The model, part number or order type, since cycle time often varies by product.
- 3Date, shift and time
- To spot differences between shifts and times of day.
- 4Role or team
- The role, not the person's name.
- 5Start and end of each cycle
- The raw times that give the cycle time.
- 6Value-added time
- Time spent changing the product.
- 7Non-value-added time
- Walking, searching, waiting and rework inside the cycle.
- 8Quantity and defects
- Good parts made, and any rework seen.
- 9Machine status
- Running, stopped, slow or in changeover.
- 10Material availability
- Whether parts were at hand or late.
- 11Abnormalities
- Anything unusual, such as a jam or a new operator.
- 12Operator ideas
- What the person doing the job would change.
Start with the fields that answer your question, and add more only when you need them. Time study software can capture the same fields on a tablet.
| Measure | What it is | Set by |
|---|---|---|
| Takt time | Available time divided by customer demand | The customer's demand rate |
| Cycle time | How often a step actually completes a unit | The process and its work content |
| Lead time | Time from order or start to delivery | Waiting, queues and batching |
Guides on this topic
- Lean construction: principles, techniques and how to startLean construction applies lean thinking to building projects. Learn the principles, the eight wastes on site, the Last Planner System and how to start.Read the guide
- Lean manufacturing examples from shop floor to officePractical examples of lean in action: what the problem looked like, which lean tool was used and what changed, in factories and beyond.Read the guide
- How to measure OEE: start tracking without a big IT projectHow to measure OEE with a free paper tracking sheet before buying software: what to record, how to calculate it and when to automate OEE tracking.Read the guide
Sources
Books and papers show their publication year. Web pages show the month we last checked them.
- 1.Mike Rother and John Shook, Learning to See: Value Stream Mapping to Add Value and Eliminate Muda (Lean Enterprise Institute, 1998)
- 2.Yasuhiro Monden, Toyota Production System: Practical Approach to Production Management (Industrial Engineering and Management Press, 1983)