Kanban Lead Time Average Days

Average Lead Time in Kanban

Lead time measures the whole stretch from the moment a ticket is created (when it lands on the board) to the moment it reaches “Done”. That stretch includes whatever time the card sat in the backlog and in any queues along the way. The formula behind it stays simple: lead time = queue time + cycle time. This is also the number the customer actually feels, because it captures the wait between asking for something and getting it.

Cycle time sits inside lead time, covering only the part where work is actually happening. Cut your lead time and you move time-to-market, NPS, and how quickly the team can react to change. Frameworks like Kanban Lite and books such as “Rethinking Agile” by Klaus Leopold keep coming back to the same point: measure lead time end to end, not just the active stage.

Applications

You will see it in service contracts, agility OKRs, customer relationship work, and decisions about clearing out bloated backlogs. Help desks track ticket lead time, product teams lean on it to forecast feature delivery, and operations watch the lead time of internal demands. Because the number is so visible, it tends to push teams toward shrinking queues, whether by capping the backlog itself or running periodic triage.

FAQ

What is the difference between lead time and cycle time? Lead time starts counting at creation, backlog included. Cycle time only starts once active work begins. So lead time ≥ cycle time, always.

Should I show lead time or cycle time to the customer? Show lead time. It mirrors the total wait they experience. Keep cycle time for internal use, where it helps you tune the production process.

How do I shrink lead time? Trim the backlog by putting a WIP cap on it. Prioritize hard using cost of delay, slice work into smaller items, and stop accepting new requests in bulk when there is no capacity to handle them.