Takt Time: What It Means, How to Calculate It, and What to Do When CT Exceeds It

Takt time is the heartbeat of a lean process. If you do not know yours, you cannot know whether your process is capable of meeting demand.

What takt time is

Takt is German for pulse or beat. Takt time is the rate at which you need to complete one unit of work to satisfy customer demand within your available time. It is not the rate you want to work. It is the rate the customer is pulling from you.

The formula: Takt Time = Available Production Time / Customer Demand

If you have 480 minutes of available time per shift and customers demand 60 units per shift, your takt time is 8 minutes. One unit every 8 minutes. Every step in the process must be capable of completing its work in 8 minutes or less.

What available time actually means

Available time is not the length of the shift. It is the shift length minus scheduled breaks, planned maintenance, and changeover time. If your shift is 480 minutes but you have two 10-minute breaks and a 20-minute changeover, your available time is 440 minutes. Use the real number. Takt calculated on inflated available time is fiction.

Reading a takt comparison on your VSM

Draw a horizontal line across your VSM at takt time. Every step whose cycle time bar rises above the takt line is a problem. That step cannot keep up with demand. Every step well below the takt line has excess capacity. The question is whether that excess capacity matters or whether it is just buffering for the constrained step.

When cycle time exceeds takt

Option 1 — Reduce CT at the constrained step. Eliminate NVA activities, improve setup, reduce wait within the step.

Option 2 — Add parallel capacity. Split the work across two operators or two machines. This doubles throughput at that step without reducing CT.

Option 3 — Accept demand you cannot meet and communicate it. Sometimes the honest answer is that takt time reveals a capacity gap that cannot be closed with current resources. That is important information. Better to know now than to promise delivery lead times the process cannot support.

When cycle time is significantly below takt

A step that runs at 30 percent of takt time is not a win. It is either overbuilt, a symptom of earlier problems, or covering for a bottleneck elsewhere. Look at the steps around it. The excess capacity is almost always there because the team knew something upstream or downstream was unreliable.