Takt Time, Cycle Time and Lead Time, Untangled

Three clocks govern every process, and they measure different things. Lead time is the customer’s clock: how long from request to delivery. Cycle time is the process’s clock: how often a finished unit actually emerges. Takt time is the demand clock: how often a unit must emerge to keep pace with customers. Confuse them and you will chase the wrong problem with real money. Untangle them and a process’s true condition reads like an instrument panel.

The confusion is understandable. All three are expressed in time per unit, all three shrink when things improve, and casual usage mixes them freely — “cycle time” alone is used at least three different ways across industries. This guide pins each term down, shows how the three relate, and follows one running example so the definitions have something to hold on to.

The example: a small firm processes insurance claims. Claims arrive from customers, pass through intake, assessment, and approval, and a decision goes back out the door. Every number in what follows is illustrative — the point is the relationships, which hold at any scale.

Lead time: the customer’s clock

Lead time is the elapsed time from the moment a request enters the process to the moment the result is delivered. It is measured in calendar time — including nights, weekends, and every minute the work spends waiting — because that is how the customer experiences it. A claim filed on the first of the month and decided on the fifteenth has a lead time of fourteen days, and the customer does not care that only ninety minutes of that involved anyone touching the file.

That gap — fourteen days elapsed, ninety minutes worked — is the single most common discovery in process improvement, and lead time is the metric that exposes it. In most office processes, the overwhelming share of lead time is waiting: work sitting in queues between steps. Which is why attacking lead time almost never means working faster. It means waiting less.

Cycle time: the process’s clock

Cycle time is the rhythm of output: on average, how much time passes between one finished unit and the next. If the claims team completes forty claims in a forty-hour week, a decision emerges on average once per hour — the process’s cycle time is one hour per claim. Note what this does not say: it does not say any individual claim took an hour. Cycle time describes the drumbeat of the process, not the journey of one item through it.

Be warned that usage varies. Some practitioners use cycle time for the hands-on processing time at a single step; others — especially in kanban circles — use it for the start-to-finish age of one item, which overlaps with lead time. The label matters less than the discipline: whenever someone quotes a cycle time, ask what event started the clock and what event stopped it. Half of all metric arguments dissolve at that question.

Takt time: the demand clock

Takt time is different in kind from the other two: it is not a measurement of the process at all, but a target derived from demand. Take the time available for work in a period, divide by the units the customer requires in that period, and the result is the pace the process must hold. The word comes from the German Takt — the beat a conductor sets for an orchestra.

Suppose the claims team receives two hundred claims per week and works a forty-hour week. Forty hours divided by two hundred claims is one claim every twelve minutes. That is the takt: to keep pace with demand, a finished decision must leave the process, on average, every twelve minutes. Notice that nothing about the team’s current speed appears anywhere in the calculation. Takt is what demand requires, whether or not the process can deliver it.

Reading the three clocks together

The comparisons are where the diagnosis lives. Cycle time against takt time tells you whether capacity matches demand. Our claims team finishes one claim per hour against a takt of one every twelve minutes — the process runs five times slower than demand, and the backlog grows by the day no matter how hard anyone works. That is not a motivation problem; it is arithmetic, and it points at capacity, staffing, or the design of the process itself.

Cycle time against lead time tells you where the time goes. One hour of rhythm producing fourteen days of elapsed time means claims spend nearly all their lives waiting — so the improvement lever is queues, batches, and handoffs, not faster assessors. And lead time against the customer’s expectation tells you whether any of this is urgent. Three numbers, three comparisons, and a process that explains itself.

Quick reference

• Lead time — request to delivery, in calendar time; the customer’s experience of the process
• Cycle time — average time between finished units; the observed drumbeat of output
• Takt time — available time divided by demanded units; the pace demand requires
• Cycle slower than takt — demand outruns capacity, and the backlog grows
• Cycle faster than takt — capacity exceeds demand; expect idle time or overproduction
• Lead time far above touch time — the process is mostly queues, and the queues are the project

The mistakes to avoid

Three errors recur. First, benchmarking your lead time against someone else’s cycle time — a fourteen-day lead is not refuted by a rival’s claim of one-hour handling; the terms describe different things. Second, setting takt as a stretch goal: takt is derived from demand, not chosen from ambition, and inflating it simply schedules overproduction. Third, celebrating a cycle-time improvement while lead time stands still — the customer feels queues, and a faster drumbeat feeding the same queues changes nothing they can see.

A process keeps three clocks; managing by only one of them is how the other two get worse.

Putting the clocks to work

These three definitions are the entry point to flow measurement, and flow measurement is where Lean stops being philosophy and starts being engineering. Our free White Belt program sets the foundations in about six hours, ending with a 30-question exam and a verifiable credential. Green Belt — 35 hours for $299, with a proctored 100-question exam, one free retake, and lifetime access — puts these metrics to work inside a full simulated improvement project, from baseline to control plan. Every process you touch is already keeping all three clocks. Certification teaches you to read them.