Cycle time — Cycle time is the time it takes to complete one unit of work from start to finish.

In plain English

Cycle time is the time it takes to complete one unit of work — once work has started.

It measures active processing time.

Not waiting.
Not queue time.
Not approvals sitting in inboxes.

Just the time spent actually doing the work.

If it takes 10 minutes to assemble one unit, the cycle time is 10 minutes.

Simple.

🔗 Lead Time
🔗 Flow

What they actually mean

Most teams obsess over cycle time.

Because it’s visible.
Measurable.
Controllable.

“We reduced cycle time by 15%.”

Sounds impressive.

But if lead time didn’t change, customers won’t notice.

Improving cycle time without improving flow often just creates bigger queues downstream.

Cycle time optimization feels productive.

System improvement feels uncomfortable.

🔗 Lead Time
🔗 Bottleneck

Example

Where you’ll hear it

Operations dashboards, productivity reviews, Six Sigma projects — and anytime someone says:

“We just need to work faster.”

Does it actually matter?

✅Yes — but only in context.

Cycle time matters when:

• It’s a true bottleneck.
• It directly limits throughput.
• It affects capacity planning.

It doesn’t matter when:

• Waiting dominates the system.
• Batch sizes are large.
• Work-in-progress is excessive.

Reducing cycle time by 10% won’t fix a system drowning in queues.

Common misconceptions

“Cycle time is the same as lead time.”
No. Lead time includes waiting. Cycle time does not.

“Cycle time only matters on production lines.”
Any repeatable work has a cycle time — including office tasks.

“Shorter cycle time means higher quality.”
Not automatically. Poor flow can shorten cycle time and still create defects.

“People control cycle time.”
Systems influence it far more than individuals do.

Red flags

🚩 Cycle time is measured obsessively — lead time is ignored.

🚩 Teams celebrate local efficiency improvements while customers still wait.

🚩 Every department optimizes itself independently.

🚩 “We’re more productive than ever” — but delivery dates slip.

Worth learning?

3/5

You should understand it.
But never confuse it with system performance.