Takt, cycle time and lead time are different

Takt, cycle time and lead time are different

Use three clocks to avoid three different questions becoming one number. Takt expresses the demand interval over a declared available period. Cycle observations describe how a process actually repeats, including its variation. Lead time follows one order through work and waiting from an agreed beginning to an agreed end. In this exercise, 400 available minutes for 300 units gives an 80-second takt. That is a planning reference, not proof that every task can safely be performed in 80 seconds. Investigate gaps in method or capacity and verify the effect on customer elapsed time.

Follow the method

1. Takt
2. Cycle time
3. Lead time

Keep the planning rhythm separate from two observed clocks

Fictional assembly planning case: a team has 400 net available minutes and demand for 300 units. Supervisor Bea is asked whether the line is fast enough and whether a customer order can be promised tomorrow. The supplied concept gives no measured cycle time or order lead time.

Follow the method

1. Available time
2. Demand
3. Takt
4. Cycle
5. Lead time

Three clocks, three decisions

Calculate takt from net time and demand, distinguish it from observed cycle and lead time, and label missing measurements instead of inventing performance.

Fictional assembly planning case: a team has 400 net available minutes and demand for 300 units. Supervisor Bea is asked whether the line is fast enough and whether a customer order can be promised tomorrow. The supplied concept gives no measured cycle time or order lead time.

Role: Assembly supervisor with the planner and an operator observer.

Normal condition

Time measures carry a defined start, finish, unit and operating condition before they are compared.

The gap

A planning sheet copies the demand-derived 80 seconds into the actual cycle and order lead-time boxes.

• 400 minutes is declared net production time; do not subtract planned breaks a second time.
• No observed cycle-time or order lead-time value is present in this worked case.

1. Align the planning quantities

   Bea checks that the 400 minutes and 300 required units refer to the same planning period and product mix. She converts minutes to seconds before dividing.

   Why: Mismatched periods or gross versus net time create a demand rhythm that looks precise but answers the wrong question.

   Evidence: 400 × 60 = 24,000 available seconds.

2. Calculate the required rhythm

   Divide 24,000 seconds by 300 units and label the result 80 seconds per required unit. Keep it in the planning reference column.

   Why: Takt comes from available time and demand. It is not a measurement of how long an operator or order actually took.

   Evidence: Takt = 80 sec/unit; demand basis and planning day recorded.

3. Define the cycle observation

   Agree a repeatable process event, such as successive completion of the same assembly operation, and plan repeated observations across relevant conditions. Record abnormal events and mix rather than silently discarding them.

   Why: A repeatable boundary makes observed cycle data interpretable. A single selected fast cycle cannot establish reliable capacity.

   Evidence: Cycle-time field remains “not measured”; observation boundary and conditions are named.

4. Define the customer clock

   Trace an identified order from accepted receipt to verified completion, stating whether the unit is working hours or elapsed calendar hours. Include waiting inside that chosen boundary.

   Why: Lead time spans the route and can be far longer than the time spent processing. An 80-second takt cannot support a next-day promise.

   Evidence: Order start/finish timestamps and boundary are still required.

5. Make only the supported decision

   Publish the 80-second demand reference and a measurement plan. Defer claims of achieved rate or delivery promise until cycle variation, route delays and capacity conditions are available.

   Why: Separating a known calculation from unknown observations prevents a target from being reported as a result.

   Evidence: Three named fields: calculated takt, measured cycle, measured order lead time.

A second plan uses gross time

Another planner supplies 450 minutes including 50 minutes of planned nonproduction time for the same 300 units.

Use 450 minus 50 = 400 net minutes; the takt stays 80 seconds per unit.

Dividing gross time would give 90 seconds and imply more productive time than the plan provides.

Both versions reconcile to 24,000 net seconds.

Run a practice session

Materials

• Calculator and timing-definition sheet
• Timestamp cards; no stopwatch needed for this desk exercise

1. Name the clocks · 4 minutes

   Which value can be calculated from the supplied original inputs?

2. Complete the original record · 7 minutes

   Why must two boxes remain unmeasured?

3. Work the changed case · 9 minutes

   Does 88 below 90 settle the capacity question?

4. Plan real observation · 5 minutes

   Which event boundaries and conditions will you record?

Debrief

• Ask learners to distinguish calendar and working time.
• Use the gross-time exception to expose double subtraction or missing deductions.

Calculate independently, then explain each result as one sentence containing its unit and boundary.

Transfer into the work

Owner: Process owner with planning and trained observers

Record: Demand/net-time basis, repeated cycle sheet and order timestamp trace

Review: When demand or time basis changes, and after the agreed observation period

Evidence: Traceable definitions, representative observations and a decision consistent with variation

Keep capacity and promise claims provisional; obtain missing timing and route evidence.