You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
When discussing the importance of workflow in Kanban, two primary notions come into play lead time and cycle time. What is the difference between them, and how can we measure them?
Lead time is mainly a period. It starts when a request enters the work cycle and is in the "ready to start" phase and ends when the request is "completed."
The following example better illustrates the concept behind lead time:
Let's say you placed a dinner order at 8:00 p.m. and your order gets delivered at 8:30 p.m. your lead time, in this case, is 30 minutes.
It's the period from the moment you placed a request until you got your request delivered.
Cycle time is how much time a resource spends on a task. For example, cycle time starts when a team member processes a request from the "in-progress" status until the "completion" status.
Back to the dinner example, cycle time is when the chef starts preparing your order. Let's say the kitchen received it at 8:10 p.m. You get your food delivered at 8:30 p.m; in this case, your cycle time is 20 minutes. It is the actual time needed to process your order.
How are both times measured?
The main difference between lead time and cycle time is their unit of measurement. Lead time is measured by seconds, hours, and weeks, whereas cycle time is measured by the time spent per task, unit, or process.
What is their relationship, and how can we calculate it?
Lead time = Cycle time x Work in Progress (WIP)
The purpose of this formula is to render the entire process predictable, allowing you to reliably forecast project completion with minimal loss and enabling you to outpace your competitors with faster, more efficient output.
Calculating lead-time vs. cycle time to ensure a better flow
The truth behind the flow of work is not how fast an item moves through the cycle but how smoothly it flows from start to end. And that's what matters. Limiting work in progress is of utmost importance as to why the Kanban method works well. It may sound unrealistic, but limiting work in progress refers to how many tasks can be started at once.
The cumulative flow diagram is one of the most effective ways to calculate lead time vs. cycle time. This diagram helps you:
Track the total number of tasks entering the workflow and gather completed tasks over time.
Shorten gap time between lead time and cycle time
Adjust workflow and improve team efficiency
Managing lead time versus cycle time effectively leads to smoother, more efficient workflows. In the process, limiting the time gaps between the start and ongoing phases ensures more predictable and achievable team goals. In addition, defining the work in progress and balancing the initial tasks results in significant added value for the customer.
Andreas Springer _Actonic_