Project management · Practical guide
Cycle Time vs. Lead Time: Boundaries and Worked Examples
By My First Task editorial team
Updated
The short answer
How to approach the work
Define the event that starts each clock before collecting data. A request-created date, a ready-for-work date and a committed-to-delivery date are not interchangeable. Calendar days include nights and weekends; working-day measures use a stated calendar. Compare completed items with similar boundaries and work types. A mean describes an average, while percentiles can help show how much longer the slower items take.
A practical sequence
- Choose the request or commitment event for lead time.
- Choose the active-start event for cycle time.
- Record the same completion event for both measures.
- Use calendar days or a defined business calendar consistently.
- Review the spread of completed items, not just the mean.
- Investigate queues and blocked time when elapsed durations rise.
Illustrative scenario · not customer research
Worked example
A request arrives on Monday, work starts on Thursday and finishes on Saturday. Using elapsed calendar-day differences, lead time is five days and cycle time is two days. Three days were spent waiting before work started. If fifteen completed items have sixty combined cycle-days, mean cycle time is four days. The sixty is the sum of individual item durations, not the length of the reporting window.
Common mistakes to avoid
- Mixing request-to-finish and start-to-finish durations.
- Treating working days as calendar days.
- Using the mean as a guaranteed deadline for every item.
Try the method with your own inputs
Questions answered
Is cycle time the same as time spent working?
Can lead time be shorter than cycle time?
Which metric should I show a customer?
Apply it in a shared workspace
Keep the agreed owner, completion criteria and important decisions with the work. Explore the relevant My First Task feature.
Research context is available in our source library. The worked example above is an editorial illustration.
Continue learning
Kanban Metrics: WIP, Throughput, Cycle Time and Work Item Age
Four useful Kanban flow measures are work in progress, throughput, cycle time and work item age. Together they show how much work is active, how much finishes, how long finished work took and how long unfinished work has been active.
ExploreWIP Limits: Finish Work Before Starting More
A work-in-progress limit caps the number of items allowed inside a defined workflow stage or system. It exposes bottlenecks and encourages finishing or unblocking work before pulling another item into progress.
ExploreProject Status Report Template: Progress, Risks and Decisions
A project status report summarizes progress toward an outcome for a stated reporting period. Include completed deliverables, upcoming commitments, risks, changed dates and decisions needed, with an owner for each follow-up.
ExploreMethod references
Turn the plan into shared work
Give each next action an owner, a completion condition and a realistic date. My First Task brings tasks, boards, project workflows and issue tracking into one workspace.