Cycle Time vs. Lead Time: Team Speed vs. Customer Wait
Lead Time is the total time a customer waits for a feature, from request to delivery. Cycle Time is the portion of that time your team is actively working. The footgun is optimizing only for Cycle Time, which can hide major customer-facing delays in the.
The mental model
Lead Time measures the entire customer journey, from the moment they ask for something to the moment they get it. Cycle Time measures just one part of that journey: the time your team is actively building the feature. If your process were a road trip, Lead Time is the total travel time, including traffic jams and rest stops, while Cycle Time is just the time the wheels are actually turning.
How it works
Lead Time starts the clock when a request is made or an idea is logged. It stops when the finished work is delivered to the customer. This metric encompasses every single delay, including time spent in the backlog, waiting for prioritization, or sitting in approval queues.
Cycle Time starts the clock only when a team member begins active work on an item, such as moving a ticket to an 'In Progress' column. It stops when the work is considered 'Done' and ready for delivery. It measures the efficiency of the development process itself.
When to use it
Track both metrics to get a complete diagnosis of your workflow. Lead Time is a proxy for customer satisfaction and predictability. Cycle Time helps you understand and improve your team's internal efficiency. The most valuable insight comes from the gap between them. A large difference between Lead Time and Cycle Time signals that the biggest delays are happening outside of active development, in your queues and handoffs.
When not to use it
Never use these metrics interchangeably, as they tell you different things. Focusing only on reducing Cycle Time (making the team faster) is a common mistake. This can lead to local optimization while ignoring a massive backlog where features sit for months, which is what the customer actually experiences. These are process improvement tools, not metrics for individual performance reviews.
One canonical example
A customer requests a new report on January 1st. It sits in the backlog until a developer starts work on March 15th. The feature is built, tested, and deployed on March 30th. The Lead Time is three months (Jan 1 to Mar 30), reflecting the customer's total wait. The Cycle Time is only 15 days (Mar 15 to Mar 30). This data clearly shows the biggest opportunity for improvement is not in making development faster, but in reducing the 2.5-month wait time in the backlog.
Interview question
A software development team consistently observes that their Lead Time is significantly longer than their Cycle Time. What does this disparity most likely suggest?
- a.The team should focus on optimizing their active development tasks to reduce the time spent coding.
- b.Significant bottlenecks exist in the workflow before or after the team's active development phase.Correct
- c.The overall project scope is too ambitious, causing the entire development lifecycle to be prolonged.
- d.The metrics are being miscalculated, as Lead Time and Cycle Time should ideally be very similar.
Why? this is the answer
The card explicitly states that "A large difference between Lead Time and Cycle Time signals that the biggest delays are happening outside of active development, in your queues and handoffs." Option A represents a common mistake, as focusing only on Cycle Time optimization ignores these larger, customer-impacting delays.
Just read this? Test yourself on what you have been reading.
Read the original → agile-academy.com
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on agile — each one lists the topics its interview covers.
See open roles