Cycle Time Analysis studies how long a process step or complete work cycle takes, including average time, variation, delay, constraint behavior, and the gap to takt or customer demand.
Definition
Cycle Time Analysis is the study of the time required to complete one process cycle, work element, transaction, part, service request, or repeated activity. It looks beyond a single average by examining time variation, waiting, interruptions, batching, changeover effects, rework, operator sequence, equipment behavior, and constraints.
In Lean and Six Sigma, cycle time is often compared with takt time, lead time, process time, queue time, and throughput. The purpose is to understand whether the process can reliably meet demand, where time is being consumed, and what improvement actions will reduce delay or instability.
History
Cycle time has been central to industrial engineering, time study, work measurement, and production management for more than a century. Lean production later emphasized cycle time as part of flow, takt, standardized work, line balancing, and waste reduction.
Six Sigma teams use cycle time analysis in service and manufacturing processes because time is often a measurable customer requirement. Reducing variation and delay can improve delivery, capacity, cost, and customer experience without sacrificing quality.
When to Use
Use cycle time analysis when a process misses delivery commitments, has long queues, struggles to meet takt, shows inconsistent output, creates overtime, hides bottlenecks, or produces customer complaints about speed. It is useful before line balancing, staffing decisions, automation proposals, Kaizen events, and DMAIC projects focused on flow or responsiveness.
It is also useful after improvements to verify that changes reduced the right time elements and did not simply shift work, increase defects, or overload another step.
Step-by-Step
- Define the cycle. State the start and stop points, work unit, process boundary, and whether the measure is per part, per batch, per transaction, or per customer.
- Separate time types. Distinguish manual time, machine time, walk time, wait time, queue time, changeover time, inspection time, rework time, and information delay.
- Collect time-ordered observations. Use time study, system timestamps, video review, production logs, or direct observation while preserving context.
- Stratify the data. Compare product family, shift, operator, machine, order type, defect status, customer segment, and workload level.
- Analyze center and variation. Review median, average, range, standard deviation, percentiles, and unusual outliers.
- Compare to takt and demand. Determine whether the process can consistently meet required pace with current resources and variation.
- Find constraints and waste. Identify waiting, motion, handoffs, batch queues, approvals, setup losses, rework loops, and bottlenecks.
- Improve and verify. Pilot countermeasures, measure before and after, and confirm quality, safety, and downstream performance are protected.
- Standardize and monitor. Update standard work, staffing logic, visual boards, dashboards, or control charts as needed.
Examples
- Assembly line: A team measures each station against takt time and finds one station with high variation caused by part fit issues and tool retrieval.
- Service intake: A claims team separates touch time from queue time and discovers most delay occurs while waiting for missing customer information.
- Changeover: A packaging line studies cycle time before and after SMED changes to confirm shorter setup time and faster first-good-piece approval.
- Healthcare flow: A clinic measures rooming, provider wait, documentation, and discharge cycle times to reduce patient visit duration.
- Engineering review: A drawing-change process reveals that approval batching, not technical review time, drives lead time.
Common Pitfalls
- Confusing cycle time with lead time. Cycle time usually measures work-cycle duration; lead time includes the broader elapsed time from request to completion.
- Using averages only. Variation and percentiles often explain customer misses better than the mean.
- Ignoring rework. Repeated cycles and defect correction must be included if they consume capacity.
- Timing an artificial condition. Observations should represent normal work, not a staged best-case demonstration.
- Improving speed at the expense of quality. Faster work that creates defects, ergonomic strain, or unsafe behavior is not real improvement.
- Missing demand context. A cycle time is only meaningful when compared with customer demand, staffing, uptime, and process mix.