The Metric That Predicts Delivery
Velocity tells you how much work a team completes per sprint. Lead time tells you how long any given piece of work takes from start to finish. These sound similar but measure different things — and for teams trying to make reliable delivery commitments, lead time is the more useful number.
A team with high velocity but high lead time is completing a lot of work, but each individual item takes a long time. A team with low velocity but low lead time is completing less work but delivering it predictably. For a stakeholder who needs to know when a specific feature will ship, lead time is what answers the question.
How FlowEra Measures Lead Time
FlowEra calculates lead time per task as the time between the task entering the first “in progress” category status and entering the first “done” category status. Because FlowEra’s status model maps every status to a category (not started / in progress / done / cancelled), this calculation works regardless of what your statuses are named.
Lead time is then visualized as a distribution across all tasks in a flow or sprint. You can see the median (P50), the typical range (P75), and the outliers (P95). Percentile distributions are more useful than averages because a small number of unusually large tasks don’t distort the central tendency.
Reading the Distribution
A tight distribution around a low median is the target. It means your team’s work is consistently sized and consistently executed.
A wide distribution with a high median means your tasks vary significantly in size and/or frequently get blocked. This is worth investigating: are your tasks poorly estimated? Are there common blockers that you haven’t addressed systematically?
A bimodal distribution — two clusters at very different lead times — often indicates two distinct types of work mixed in the same flow. Bugs and features in the same backlog often produce this pattern. Splitting them into separate flows with appropriate status models often clarifies both curves.
Cycle Time vs. Lead Time
These terms are often confused, including in our own conversations. The distinction matters:
Lead time — from the moment a task was created (or entered the backlog) to when it was done. Includes waiting time.
Cycle time — from the moment active work started to when it was done. Excludes waiting in the backlog.
For teams that want to understand their process efficiency, cycle time is the cleaner metric. For teams that need to set customer expectations about delivery, lead time is more honest because it includes the queue.
FlowEra calculates cycle time from the first “in progress” transition — the moment someone picked the task up — rather than from creation. This makes cycle time a measure of process efficiency rather than backlog management.
Using Lead Time to Set Commitments
Once you have a few months of lead time data, you can make probabilistic delivery commitments. “Based on our last 3 months of data, 85% of tasks in this flow complete within 5 days. This feature is 3 tasks, so there’s an 85% chance it ships within 15 business days.”
This is more honest and more useful than sprint-based estimates, which require breaking down work into story points and rely on velocity consistency that many teams don’t actually have.
Reducing Lead Time
Lead time reduces when:
- Task scope is smaller and more consistent
- Handoffs between states are faster (less waiting for reviews, sign-offs, or dependencies)
- Blocking issues are addressed at the system level, not one at a time
- Work in progress is limited so tasks don’t sit in “in progress” statuses while actual work happens elsewhere
The analytics tell you what’s happening. The team decides what to change.