Lead Time vs Cycle Time

Lead time and cycle time are two of the most common delivery measures, and two of the most often confused. Both measure elapsed time, and both are used to understand how quickly work gets done. The difference is where the clock starts. Lead time starts when someone asks for something. Cycle time starts when the team actually begins working on it. The gap between the two is the time the request spends waiting in a backlog or queue, and in many organizations that gap is the largest part of the total. Knowing which measure is in use, and which one a stakeholder cares about, avoids many disagreements about whether a team is fast or slow.

The terms come from lean manufacturing, where lead time measured how long a customer waited for an order and cycle time measured how long production took. In software delivery, Kanban teams use both, and DORA research defines its own version, lead time for changes, as the time from code commit to production. For delivery leaders, product managers and engineering teams, understanding the difference prevents misleading comparisons and points to the right improvements.

Definition of Lead Time vs Cycle Time

Lead time is the elapsed time from the creation or acceptance of a request until it is delivered to the customer. Cycle time is the elapsed time from the start of active work on that request until it is completed. Lead time therefore equals waiting time before work starts plus cycle time.

Both are flow metrics; cycle time is the more common team-level measure, while lead time for changes is one of the DORA metrics.

Lead Time

Lead time is the customer's view. It answers the question of how long someone waits from asking for something to receiving it.

It includes time in the backlog, prioritization, any waiting before work begins and all the work itself.

Long lead times are often caused by large backlogs and slow prioritization rather than slow engineering. Requests that sit unprioritized for months inflate lead time even though no one has started working on them.

Cycle Time

Cycle time is the team's view. It answers the question of how long work takes once the team commits to it.

It includes active work and any waiting after work starts, such as for reviews, testing or deployment.

Long cycle times usually point to too much work in progress, large items or bottlenecks inside the delivery process. Because the team controls most of what happens after work starts, cycle time is often the first measure teams improve.

Importance of the Distinction in Delivery Management

Using the right measure points to the right fix. If lead time is long but cycle time is short, the problem is the backlog and prioritization, not the team's delivery process.

It keeps comparisons fair. Comparing one team's lead time with another team's cycle time produces misleading conclusions, so definitions need to be agreed and stated.

It also helps set expectations. Customers and stakeholders care about lead time, so promises based only on cycle time will feel late to them. Sharing both measures with stakeholders explains why a team can be fast at delivery while customers still wait a long time.

Lead Time, Cycle Time and Financial Management

Lead time is the clearer measure of cost of delay, since value is not realized until the customer receives the work.

Large backlogs inflate lead time while representing ideas the organization has not yet decided to fund.

Reducing cycle time improves engineering efficiency, while reducing lead time often requires better portfolio and backlog decisions.

Tracking both shows whether spending on delivery capacity or on better prioritization would do more to speed up value.

Common Challenges

Organizations use the terms inconsistently, and some tools label one as the other. Writing down definitions avoids confusion.

Lead time depends on when requests are recorded. If ideas are logged long before anyone intends to act on them, lead time can look much worse than customers experience.

DORA's lead time for changes starts at commit, which is closer to a slice of cycle time than to customer lead time. Reports that quote lead time without stating the start point should be read with care, since the same term can describe very different spans of time.