Lead time is the one flow metric your customers actually feel. It measures the total elapsed time from the moment a request enters your system to the moment it is delivered — every hour of active work and every hour the item spends waiting in a queue. When a stakeholder asks “how long will this take?”, lead time is the honest answer. This guide explains what lead time is, how Flow Metrics Charts for Jira Cloud measures it from your real Jira history, how to read the chart, and how to bring lead time down.
What is lead time?
Lead time is the elapsed time from when a work item is created — the moment a request enters your system — until it is resolved and delivered. The defining feature of lead time is that it counts all of that elapsed time: the periods when someone is actively working the item, and the usually far longer periods when it sits in a backlog, waits for review, or is blocked on a dependency. That is exactly why lead time is the truest measure of how your delivery feels from the outside.
Lead time is one half of the app’s Flow Time chart. The other half is cycle time, which counts only the active working period once a team has started an item. Read together they answer two different questions: lead time asks “how long does the whole thing take?” while cycle time asks “how long does the work itself take once we begin?”
Lead time vs cycle time: where the waiting hides
The gap between lead time and cycle time is pure waiting — time an item spends in a queue before anyone touches it. If lead time is 20 days but cycle time is only 4, then 16 of those days were spent waiting, and coding faster will not fix that. Shrinking the gap usually means starting work sooner and reducing queues, not working harder. We cover the distinction in depth in Cycle Time vs. Lead Time.
How lead time is measured in Jira
In Flow Metrics Charts for Jira, lead time is the difference between an issue’s created date and its resolution date, reported in days. Two design choices make the number trustworthy:
- Aging work is included. Issues still in progress are measured from their creation date to today, so a request open for 40 days appears as a 40-day-and-counting item instead of hiding until it closes. That turns the chart into an early-warning system rather than a post-mortem.
- You see the range, not just an average. Each period shows the minimum, average and maximum lead time, so a single outlier cannot quietly distort your view of typical performance.
You can point the chart at any data source — a project, board, saved filter, user or custom JQL query — and view the trend by day, week or month.
How to read the lead time chart
Read the trend and the spread, not individual issues:
- A rising trend signals growing queues, an overloaded backlog, or too much work in progress — often long before a deadline is actually missed.
- High variability (a wide gap between minimum and maximum) means some items take far longer than others. Break the chart down by issue type, epic, label or fix version to find the cause.
- Forecast with percentiles. Instead of quoting a fragile average, use the distribution: “85% of items finish within 12 days” is a probabilistic promise you can actually keep.
- Watch aging in-progress items. An item whose lead time is climbing while it is still open is a live risk you can act on now, not after the fact.
Why lead time matters for your business
Lead time is the closest proxy you have for time to market, and time to market drives revenue, customer satisfaction and competitive advantage. Shorter, more consistent lead times mean faster feedback, quicker fixes, and delivery dates you can commit to without crossing your fingers. For service teams, lead time is the backbone of a credible SLA; for product teams, it is the difference between a roadmap that lands and one that quietly slips.
How to reduce lead time
The most reliable lever is counter-intuitive: reduce work in progress. Lead time, work in progress (WIP) and throughput are linked by Little’s Law — average lead time is approximately average WIP divided by average throughput. A team with 24 items in progress that finishes 8 per week has an average lead time of about three weeks; cut WIP to 16 without adding people and lead time falls to about two weeks. Practical moves:
- Set WIP limits so the team finishes work before starting more — see Work in Progress (WIP) in Jira.
- Attack queue time by finding the statuses where items wait longest and removing the handoff or approval that stalls them.
- Make work items smaller and more uniform so they flow through review and testing quickly.
- Protect focus — context switching across many open items is one of the biggest hidden costs in lead time.
How lead time connects to the other flow metrics
Lead time never moves alone. Because of Little’s Law, lowering flow load (WIP) shortens lead time at the same throughput; and as lead time stabilizes, your system stability and forecasts improve. Reading the flow metrics together — rather than as isolated dashboards — is what lets a team diagnose why delivery is slow and pull the right lever.
Track lead time in Jira
Flow Metrics Charts for Jira Cloud calculates lead time — and every other flow metric — directly from your Jira status history, with no manual tagging, spreadsheets or exports. It runs on Atlassian Forge, so your issue data never leaves Atlassian’s cloud, and its built-in Rovo AI reads the chart and explains anomalies in plain language. Start with the flow metrics for Jira overview, or read the canonical explainer, Flow Metrics Explained.
Frequently asked questions
What is a good lead time?
There is no universal target — a good lead time is one short enough to meet customer expectations and, above all, stable and trending down. Track your own 85th-percentile lead time over time rather than comparing against another team’s raw number.
What is the difference between lead time and cycle time?
Lead time measures the full customer wait, from request created to delivered, including all queues. Cycle time measures only the active working period, from when the team starts an item to when it is done. Lead time is always equal to or longer than cycle time; the gap is waiting time.
How is lead time calculated in Jira?
Flow Metrics Charts for Jira calculates lead time as the number of days between an issue’s created date and its resolution date. Work still in progress is measured from creation to today so you can see aging items, and each period reports minimum, average and maximum.
2 Comments
Leave your reply.