Definition
Lead Time
Lead time is the total elapsed time from when an issue is first created or requested to when it is delivered. Unlike cycle time, it includes the waiting period in the backlog before work begins. Lead time reflects the customer's experience of how long a request actually takes end to end.
Key takeaways
- Lead time is the total elapsed time from when an issue is first created or requested to when it is delivered. Unlike cycle time, it includes the waiting period in the backlog before work begins. Lead time reflects the customer's experience of how long a request actually takes end to end.
- Lead time answers the question a requester actually asks: 'I reported this — when will it be done?' It measures the full journey from creation to completion, including all the time an issue sat in the backlog waiting to be picked up.
- Planoda timestamps issue creation and completion, so lead time and cycle time are both derived from the same audit trail and can be compared side by side.
Lead time answers the question a requester actually asks: 'I reported this — when will it be done?' It measures the full journey from creation to completion, including all the time an issue sat in the backlog waiting to be picked up. That waiting is invisible to the team's working metrics but very visible to whoever is waiting on the result.
The gap between lead time and cycle time is itself diagnostic. If issues take five days of active work but three weeks of lead time, the bottleneck is not execution — it is prioritization and queue length. The fix lives in triage and backlog discipline, not in working harder. Shrinking the backlog and pulling work in sooner moves lead time even when cycle time is already tight.
Lead time is the headline metric for support and request-driven work, where the clock the customer feels is the only one that matters. Tracking its trend over time shows whether the team is keeping up with inbound demand or quietly falling behind.
Planoda timestamps issue creation and completion, so lead time and cycle time are both derived from the same audit trail and can be compared side by side.
Related terms
- Cycle TimeCycle time is how long an issue takes from the moment work actively starts on it to the moment it is done. Measured in hours or days, it captures the team's hands-on flow efficiency. Shorter, more consistent cycle times mean a more predictable system — the core flow metric Kanban teams optimize.
- ThroughputThroughput is the number of work items a team completes in a given period — issues finished per week, for example. It is the simplest flow metric: a direct count of output over time. Tracked across periods, throughput reveals a team's real delivery capacity and is the basis for probabilistic, estimate-free forecasting.
- BacklogA backlog is the ordered list of all work a team has identified but not yet started — features, bugs, improvements, and ideas. It is the team's single source of pending work, prioritized so the most valuable or urgent items sit at the top, ready to be pulled into a cycle or onto a board.
- TriageTriage is the process of reviewing newly reported issues and deciding what happens to each — accept and prioritize, request more detail, route to a team, or close. Borrowed from emergency medicine, it keeps the incoming flow of bugs and requests from overwhelming a team by quickly sorting signal from noise at the front door.