Cycle time

Cycle Time

Updated November 2026 · reviewed for today
In short

Cycle time is the elapsed time between when a work item starts and when it finishes. In lean manufacturing it is the time to produce a part or complete a process, timed by actual measurement; in software, the Kanban Guide defines it from start to finish of a work item. It is tied to work in progress and throughput by Little’s Law, proved by John Little in 1961.

Cycle Time: hand-drawn explainer by The Business Engineer
Drawing by The Business Engineer.

How it works

01
Pick start and finish points
Agree what counts as started and finished for each kind of work. Without fixed points, cycle time numbers cannot be compared.
02
Measure every item
Record the start and finish of each item and look at the spread, not only the average. A few slow items often reveal the real problem.
03
Use Little's Law
Average cycle time equals average work in progress divided by average throughput. Limiting work in progress is the most direct way to cut it.
04
Find the waiting
Most of the time in a slow process is usually queueing between steps, not the work itself. Lean calls this time that adds cost but no value.

Where you see it today

Software delivery metrics

DORA, the research programme behind the best-known software delivery metrics, tracks change lead time: the time from a change being committed to version control to it running in production. Teams use it with deployment frequency and recovery time to judge flow.

Kanban service level expectations

The Kanban Guide (May 2025 version) asks teams to set a service level expectation from historical cycle time, such as a forecast that a share of items will finish within a set number of days. Cycle time becomes a promise backed by data, not a guess.

AI coding tools and real speed

A randomised trial of experienced open-source developers using early-2025 AI tools (Becker et al., 2025) found that allowing AI increased task completion time by 19%, although the developers themselves believed it had made them faster. Measured cycle time beat perception.

AI as an amplifier

DORA’s 2025 State of AI-assisted Software Development report describes AI as an amplifier of an organisation’s existing strengths and weaknesses. Faster code writing helps cycle time only if review, testing and release can absorb the extra work.

Cycle time vs related time measures

Cycle time
What it timesFrom work started to work finished
Who cares mostThe team doing the work
Lead time
What it timesFrom request to delivery
Who cares mostThe customer
Takt time
What it timesAvailable production time divided by customer demand
Who cares mostPlanners pacing production
Throughput
What it timesItems finished per unit of time
Who cares mostManagers forecasting capacity
Work item age
What it timesTime since an unfinished item started
Who cares mostTeams spotting stuck work early

How to use it

  • Write down the start and finish points for each work type before you measure anything.
  • Plot cycle time for every finished item and review the slowest ones each week.
  • Cap work in progress; by Little's Law it is the quickest lever on cycle time.
  • Watch the age of open items so stuck work is found before it becomes a long cycle.
  • When you add AI tools, measure cycle time before and after instead of trusting how fast work feels.
The Business Engineer lens

AI makes some steps of a process much cheaper, which moves the bottleneck to the steps it does not touch, such as review and approval. The Business Engineer treats end-to-end cycle time, not the speed of one step, as the honest measure of whether AI has made a business faster.

Read: The State of Agentic Work →Explore everything we publish →

Related: Little's Law · Takt time · Kanban · Value stream mapping · Theory of constraints

Frequently asked questions

What is cycle time?

It is the elapsed time between when a work item starts and when it finishes, measured for each item.

What is the difference between cycle time and lead time?

Lead time runs from the customer's request to delivery; cycle time counts only from the moment work starts until it is finished.

How do you reduce cycle time?

Limit work in progress, remove waiting between steps and fix the slowest stage; Little's Law links lower work in progress to shorter cycle time.

Do AI coding tools shorten cycle time?

Not automatically. One randomised trial found experienced developers took longer with early-2025 AI tools, so measure before and after.

Sources

The full guide

The complete explainer, cleaned up and reformatted for mobile.

Cycle time is a critical metric used in various industries to measure the efficiency of processes, workflows, and operations. It represents the time it takes to complete a specific task or process from start to finish. Understanding and optimizing cycle time can significantly impact productivity, quality, and overall business performance.

Foundations of Cycle Time

To fully grasp the concept of cycle time, it’s essential to understand several foundational principles:

  1. Task or Process: Cycle time is applied to a specific task or process. It can refer to various activities, from manufacturing a product to processing customer service requests or software development tasks.
  2. Start and Finish: Cycle time measures the time elapsed between the initiation (start) and completion (finish) of a task. It includes both active work time and any waiting or idle time.
  3. Efficiency and Speed: Reducing cycle time often correlates with improved efficiency and speed in completing tasks. However, it should not compromise quality.
  4. Continuous Improvement: Cycle time analysis is a fundamental component of continuous improvement methodologies like Lean and Six Sigma. It helps identify bottlenecks, waste, and opportunities for optimization.

Core Principles of Cycle Time

Several core principles underpin the concept of cycle time

  1. Measurement: Accurate measurement of cycle time is crucial. It requires defining clear start and end points for the task or process.
  2. Standardization: To compare cycle times across similar tasks or processes, standardization is essential. This ensures consistency in measurement.
  3. Reduction: The goal of cycle time analysis is often to reduce the time required to complete a task while maintaining or improving quality.
  4. Efficiency: Shorter cycle times generally signify improved efficiency, but it’s important to strike a balance between speed and quality.

Methods for Measuring Cycle Time

Cycle time can be measured using various methods, depending on the nature of the task or process:

  1. Stopwatch or Timer: For manual tasks or processes, a stopwatch or timer can be used to record the time taken from start to finish.
  2. Software Tools: Many digital tools and software applications are available to track cycle time for specific processes, such as project management software for software development tasks.
  3. Workflow Analysis: In complex workflows, cycle time can be analyzed by breaking down the process into its constituent steps and measuring the time taken at each stage.

Benefits of Measuring and Optimizing Cycle Time

The measurement and optimization of cycle time offer numerous benefits across various industries and sectors:

  1. Increased Productivity: Shorter cycle times mean tasks and processes are completed faster, leading to increased productivity.
  2. Improved Quality: Optimizing cycle time should not compromise quality. In fact, it often leads to improved quality as bottlenecks and inefficiencies are addressed.
  3. Faster Response Times: Shorter cycle times enable organizations to respond more quickly to customer demands and changing market conditions.
  4. Cost Savings: Efficiency gains resulting from cycle time optimization can lead to cost savings, as resources are used more effectively.
  5. Competitive Advantage: Organizations that can deliver products or services faster often gain a competitive advantage in the market.
  6. Enhanced Customer Satisfaction: Faster response times and improved quality can lead to higher customer satisfaction.

Practical Applications of Cycle Time

Cycle time has practical applications in a wide range of industries and processes:

  1. Manufacturing: In manufacturing, cycle time measures the time it takes to produce a unit of a product. Reducing cycle time can lead to higher production rates and lower costs.
  2. Software Development: In agile software development, cycle time tracks how long it takes to complete a user story or feature. Shorter cycle times lead to faster product releases.
  3. Customer Service: In customer service operations, cycle time measures how quickly customer inquiries or requests are resolved. Faster response times lead to improved customer satisfaction.
  4. Healthcare: In healthcare, cycle time measures the time patients spend in various stages of care, from admission to discharge. Reducing cycle time can lead to improved patient outcomes and reduced costs.
  5. Supply Chain: In supply chain management, cycle time measures the time it takes for products or materials to move from suppliers to customers. Shorter cycle times can reduce inventory holding costs and improve order fulfillment.
  6. Project Management: In project management, cycle time measures how long it takes to complete specific project tasks or deliverables. It helps project managers track progress and make adjustments as needed.

The Role of Cycle Time in Workflow Optimization

Cycle time plays a crucial role in optimizing workflows

  1. Identification of Bottlenecks: Analyzing cycle times can help identify bottlenecks or areas where tasks or processes are slowing down. This information allows organizations to focus their improvement efforts where they are needed most.
  2. Process Streamlining: By reducing cycle times, organizations can streamline their processes, making them more efficient and cost-effective.
  3. Resource Allocation: Understanding cycle times enables organizations to allocate resources more effectively and prioritize tasks or processes that have longer cycle times.
  4. Performance Monitoring: Cycle time serves as a key performance indicator (KPI) for monitoring the efficiency of workflows and measuring the impact of process improvements.

Challenges and Considerations

While measuring and optimizing cycle time offer substantial benefits, there are challenges and considerations to

keep in mind

  1. Quality vs. Speed: Striking the right balance between speed (shorter cycle times) and quality is crucial. Optimizing for speed alone can lead to quality issues.
  2. Data Accuracy: Accurate measurement of cycle time relies on precise data collection and standardization. Inaccurate data can lead to misleading conclusions.
  3. Process Complexity: Complex processes may have multiple cycle times within them, making analysis and optimization more challenging.
  4. Human Factors: Human factors, such as skill levels and motivation, can impact cycle times. Addressing these factors may require additional interventions.
  5. Continuous Improvement: Optimizing cycle time is an ongoing process. Organizations should commit to continuous improvement and regularly revisit their workflows.

Conclusion

Cycle time is a fundamental metric for measuring and optimizing workflow efficiency across various industries. Whether in manufacturing, software development, customer service, or healthcare, understanding and improving cycle time can lead to increased productivity, improved quality, and better resource allocation. By identifying bottlenecks and inefficiencies, organizations can streamline their processes and gain a competitive edge in today’s fast-paced business environment.

Key Highlights

  • Foundations of Cycle Time:
    • Refers to the time between initiating and completing a specific task or process.
    • Emphasizes efficiency and speed without compromising quality.
    • Integral to continuous improvement methodologies like Lean and Six Sigma.
  • Core Principles:
    • Measurement: Accurate measurement with clear start and end points is crucial.
    • Standardization: Standardize measurement methods for consistency.
    • Reduction: Aim to reduce cycle time while maintaining or improving quality.
    • Efficiency: Shorter cycle times signify improved efficiency.
  • Methods for Measuring Cycle Time:
    • Stopwatch or Timer: Manual tasks can be timed using stopwatch or timer.
    • Software Tools: Digital tools track cycle time for specific processes.
    • Workflow Analysis: Complex workflows are broken down for analysis.
  • Benefits:
    • Increased Productivity: Faster completion leads to enhanced productivity.
    • Improved Quality: Optimization improves quality by addressing inefficiencies.
    • Faster Response Times: Quick response to demands and market changes.
    • Cost Savings: Efficient resource utilization reduces costs.
    • Competitive Advantage: Faster delivery provides a competitive edge.
    • Enhanced Customer Satisfaction: Faster response and improved quality lead to higher satisfaction.
  • Practical Applications:
    • Manufacturing: Higher production rates and lower costs.
    • Software Development: Faster product releases in agile development.
    • Customer Service: Quick resolution enhances satisfaction.
    • Healthcare: Improved patient outcomes and reduced costs.
    • Supply Chain: Reduced inventory costs and improved fulfillment.
    • Project Management: Efficient task completion and progress tracking.
  • Role in Workflow Optimization:
    • Bottleneck Identification: Pinpoints areas needing improvement.
    • Process Streamlining: Enhances efficiency and cost-effectiveness.
    • Resource Allocation: Enables effective resource distribution.
    • Performance Monitoring: Serves as a key performance indicator.
  • Challenges and Considerations:
    • Quality vs. Speed: Balancing speed with quality is crucial.
    • Data Accuracy: Precise data collection ensures accurate analysis.
    • Process Complexity: Multiple cycle times in complex processes pose challenges.
    • Human Factors: Skills and motivation impact cycle times.
    • Continuous Improvement: Optimization is an ongoing process.
Lead Time
DescriptionLead Time measures the total duration from the moment a customer or stakeholder submits a request until it is delivered or fulfilled. It includes all stages of the development process, such as backlog grooming, planning, implementation, testing, and deployment. Lead Time provides insights into the overall responsiveness and efficiency of the development team in delivering value to customers.
When to ApplyWhen analyzing the end-to-end process of delivering value to customers in Agile development. Lead Time is used by Agile teams, product owners, and stakeholders to understand the time it takes to deliver requested features or changes, identify areas for improvement, and optimize the development process for faster delivery and enhanced customer satisfaction.
Cycle Time Efficiency
DescriptionCycle Time Efficiency measures the ratio of value-added time to total cycle time in a process. It provides insights into process efficiency and waste reduction opportunities. By improving Cycle Time Efficiency, organizations can streamline processes, reduce lead times, and deliver products or services more quickly and efficiently.
When to ApplyWhen evaluating process efficiency and identifying opportunities for waste reduction. Cycle Time Efficiency is used in Lean manufacturing, Agile development, and process improvement initiatives to assess the effectiveness of processes, identify non-value-added activities, and implement strategies to streamline workflows and improve productivity.
Throughput
DescriptionThroughput measures the rate at which a system, process, or team delivers output or completes tasks within a specific time period. It provides insights into system capacity, productivity, and performance. By optimizing throughput, organizations can increase efficiency, meet demand, and deliver value to customers more effectively.
When to ApplyWhen assessing system or team productivity and capacity. Throughput metrics are used in Agile development, manufacturing, and operations management to monitor output rates, identify bottlenecks, and improve overall productivity. They help organizations set realistic performance goals, allocate resources effectively, and optimize workflows to meet customer demand and deliver products or services in a timely manner.
Value Stream Mapping
DescriptionValue Stream Mapping is a visual tool used to analyze, design, and improve the flow of materials, information, and activities required to deliver a product or service to customers. It helps organizations visualize end-to-end process flows, identify opportunities for improvement, and optimize workflows to enhance efficiency and customer value.
When to ApplyWhen analyzing and improving end-to-end process flows and cycle times. Value Stream Mapping is used in Lean manufacturing, Agile development, and service industries to identify waste, streamline processes, and improve overall efficiency and performance. It helps organizations visualize process flows, identify bottlenecks, and implement changes to deliver products or services more quickly and effectively to customers.
Process Cycle Efficiency
DescriptionProcess Cycle Efficiency measures the ratio of value-added time to total cycle time in a specific process. It provides insights into process effectiveness and waste reduction opportunities. By improving Process Cycle Efficiency, organizations can streamline processes, reduce lead times, and deliver products or services more quickly and efficiently.
When to ApplyWhen evaluating process effectiveness and identifying opportunities for waste reduction. Process Cycle Efficiency metrics are used in Lean manufacturing, Agile development, and process improvement initiatives to assess the effectiveness of processes, identify non-value-added activities, and implement strategies to streamline workflows and improve productivity.
Process Lead Time
DescriptionProcess Lead Time measures the total duration from the initiation of a process until its completion or delivery. It provides insights into the overall efficiency and responsiveness of a process in delivering value to customers. By reducing Process Lead Time, organizations can improve customer satisfaction, increase agility, and deliver products or services more quickly to the market.
When to ApplyWhen analyzing the duration of specific processes and activities. Process Lead Time is used by organizations to assess process efficiency, identify bottlenecks, and optimize workflows to improve overall performance and responsiveness. It helps organizations measure and monitor the time it takes to complete tasks or deliverables, identify areas for improvement, and implement changes to enhance productivity and customer satisfaction.
Flow Efficiency
DescriptionFlow Efficiency measures the ratio of value-added time to total cycle time in a specific process. It provides insights into process efficiency and waste reduction opportunities. By improving Flow Efficiency, organizations can streamline processes, reduce lead times, and deliver products or services more quickly and efficiently.
When to ApplyWhen evaluating process efficiency and identifying opportunities for waste reduction. Flow Efficiency metrics are used in Lean manufacturing, Agile development, and process improvement initiatives to assess the effectiveness of processes, identify non-value-added activities, and implement strategies to streamline workflows and improve productivity.
Process Bottleneck Analysis
DescriptionProcess Bottleneck Analysis is a method used to identify constraints or bottlenecks in a process that limit its capacity or throughput. It helps organizations identify opportunities to increase efficiency, reduce lead times, and optimize resource allocation to improve overall process performance.
When to ApplyWhen analyzing process flow and identifying constraints that limit capacity or throughput. Process Bottleneck Analysis is used in Lean manufacturing, Agile development, and operations management to identify and address bottlenecks that hinder process efficiency and productivity. It helps organizations optimize resource allocation, streamline workflows, and improve overall process performance to meet customer demand and deliver value more effectively.
Work in Progress (WIP) Limits
DescriptionWork in Progress (WIP) Limits are constraints placed on the number of tasks or items that can be actively worked on simultaneously in a process or workflow. They help prevent overloading and congestion, reduce multitasking, and improve flow efficiency.
When to ApplyWhen managing workloads and optimizing flow in Agile development or Kanban workflows. WIP Limits are used in Agile development, Kanban, and Lean manufacturing to manage work in progress, balance workloads, and optimize flow efficiency. They help organizations prioritize tasks, limit multitasking, and maintain a steady flow of work to deliver value more effectively and efficiently to customers.
Value-added Time Analysis
DescriptionValue-added Time Analysis is a method used to identify and quantify the time spent on activities that directly contribute to creating value for the customer in a process. It helps organizations identify opportunities to reduce waste, streamline processes, and optimize resource utilization to improve overall process efficiency and effectiveness.
When to ApplyWhen analyzing process flow and identifying opportunities for waste reduction. Value-added Time Analysis is used in Lean manufacturing, Agile development, and process improvement initiatives to assess process efficiency, identify non-value-added activities, and implement strategies to streamline workflows and improve productivity. It helps organizations focus on activities that create value for customers and eliminate or minimize activities that do not contribute to customer value or satisfaction.

Main Case Studies

Scroll to Top
FourWeekMBA