Lead Time: What It Measures, Why It Matters, and Where It Hides
Lead time is the time a customer waits. In most organizations, very little of it is spent working on the customer's request; most of it is spent waiting between the people who do.
By Capstera Business Architecture Staff · Updated
12 min read
Lead time is the total elapsed time from when a request is made to when it is fulfilled: from a customer placing an order to receiving it, from a purchase requisition to delivery, or from an idea being approved to a product reaching the market. It measures what the customer experiences, including all the waiting, not just the time someone spends working.
A customer orders a replacement part. Picking it takes four minutes, packing six, and the truck journey a few hours. The customer receives it nine days later. Nobody in the chain thinks they were slow, and each of them is right about their own step. The missing days were spent in queues: an order waiting for a credit check, a pick list waiting for the next wave, a parcel waiting for a carrier that only collects twice a week. Lead time is the measure that makes those days visible, and value stream mapping is the method that shows where they went.
Key Takeaways
- Lead time runs from request to fulfillment, as the customer experiences it. Cycle time measures how long the work itself takes.
- In most processes, most of the lead time is waiting, not working. Reducing waiting usually beats speeding up the work.
- Little's Law links lead time to work in progress and throughput: more work in progress, at the same throughput, means longer lead times.
- Time to market is lead time for a new product: from concept approval to launch.
- Measure lead time across a whole value stream, stage by stage, to find where the delay actually is.
- Report the spread, not just the average. Customers remember the slow ones.
What Is Lead Time?
The term is used across manufacturing, supply chain, software and services. The meaning is the same: how long from asking to receiving.
In supply chain and manufacturing, the most common forms are customer lead time, from order to delivery; supplier lead time, from purchase order to receipt; and production lead time, from release to finished goods. In software delivery, lead time for changes, from code committed to code running in production, is one of the four measures popularized by the DevOps Research and Assessment program and the 2018 book Accelerate. In services, it may be the time from a claim being submitted to a decision, or from an application to an approved account.
What these share is the boundary: lead time starts when the requester asks and stops when they have what they asked for. It includes every queue, handoff, approval and rework loop in between. That is why it is the measure that matters to customers, and why internal measures that look only at working time can look healthy while customers wait.
Lead Time vs. Cycle Time vs. Takt Time
Three time measures are often confused. Each answers a different question.
Lead time is what the customer waits. Cycle time, in its most common usage, is the time from when work actually starts on an item to when it is finished, excluding the wait before it starts. Process time or touch time is narrower still: the time someone is actively working on the item. Takt time is not a measure of performance at all; it is the pace demand requires, calculated as available working time divided by customer demand.
Usage varies by industry and author, especially for cycle time, so define each measure explicitly before comparing numbers across teams.
| Measure | Starts | Ends | The question it answers |
|---|---|---|---|
| Lead time | When the request is made | When it is fulfilled | How long does the customer wait? |
| Cycle time | When work starts on the item | When the work is finished | How long does the work take once started? |
| Process (touch) time | When someone works on it | When they stop | How much effort does the item actually need? |
| Takt time | (A rate, not a duration) | How fast must we finish items to keep up with demand? |
How to Calculate Lead Time
For a single item, lead time is simple subtraction. For a process, two further calculations are worth knowing.
For one order, lead time is the fulfillment date minus the request date. For a process, report the distribution: the median and a high percentile, such as the 85th or 95th, tell you more than the average, because a few very slow items can hide behind a reasonable mean and customers remember those.
Little's Law, proven by John Little in 1961, relates three quantities in any stable system: average work in progress equals average throughput multiplied by average lead time. Rearranged, average lead time equals work in progress divided by throughput. Its practical lesson is uncomfortable for busy organizations: if a team finishes ten items a week and has fifty in progress, the average item takes five weeks, however hard everyone works. Starting fewer things is often the fastest way to finish each one sooner.
Process cycle efficiency compares working time with lead time: total process time divided by total lead time. In processes nobody has examined, it is usually low, because most of the lead time is waiting. That number is the case for looking at queues before looking at people.
Time to Market: Lead Time for New Products
Time to market is the lead time of an organization's product development value stream.
It usually runs from a concept being approved to the product being available to customers. Like any lead time, it is mostly made of waiting: for funding decisions, for scarce specialists, for test environments, for regulatory or quality sign-off, for a supplier's tooling. And like any lead time, it is shortened less by working harder than by removing queues, reducing the amount of work in progress, and releasing value in smaller increments where the product allows it.
Time to market matters because it compounds. A shorter cycle lets an organization learn from customers sooner, correct course sooner, and capture a window before competitors close it. It is also one of the clearest outcome measures for capabilities such as Product Development, Portfolio Management and Go-to-Market Planning, and a natural KPI for transformation programs that claim to make the organization more responsive.
Reducing Lead Time with Value Stream Mapping
You cannot reduce lead time by looking at one team. You have to look at the whole stream and see where items wait.
Value stream mapping, a technique from lean practice, draws every stage an item passes through from request to fulfillment, and records for each stage the process time and the wait before it. Adding them up separates working time from waiting time, and usually shows that a small number of queues account for most of the delay. Those queues tend to sit at handoffs between teams, at approvals, and wherever work is batched.
The illustrative example below shows the pattern. The figures are invented to make the mechanics visible.
| Stage | Process time | Wait before the next stage | What causes the wait |
|---|---|---|---|
| Order received and entered | 10 minutes | 1 day | Orders keyed in once daily in a batch |
| Credit check | 5 minutes | 2 days | Manual review queue for any order above a set amount |
| Stock allocation | 2 minutes | 1 day | Allocation run overnight |
| Pick and pack | 10 minutes | 3 days | Carrier collects twice a week |
| Transport | 1 day | None | |
| Total | About 1 day of work | 7 days of waiting | Lead time of about 8 days |
Lead Time and Business Architecture
Lead time belongs to value streams, and the causes of long lead times belong to capabilities. Business architecture connects the two.
A value stream in business architecture is defined from the customer's trigger to the customer's outcome, so its natural headline measure is lead time. Each stage of the stream draws on business capabilities, and when a stage is slow, the cause usually traces to one of them: a credit decision that waits because Credit Risk Management has no automated limits; an allocation that waits because Inventory Management runs in overnight batches; a delivery that waits because Transportation Management has no flexible carrier capacity.
That mapping turns a lead time problem into an investment decision. The capability heat map shows which capabilities limit the value streams customers care about most; the business case for improving them can promise a lead time reduction for a named stream, and be measured against it. It also prevents a common waste: improving a capability that is not on the critical path of any slow value stream.
Go further
- Value stream KPIs — What to measure along a value stream, and why stage measures predict outcomes.
- KPI meaning — How to define lead time precisely so teams calculate it the same way.
- Procurement — Supplier lead time and the procure-to-pay value stream.
- What is a value stream? — The business architecture definition, from trigger to outcome.
Common Lead Time Mistakes
Lead time is easy to measure badly.
- Starting the clock late. Measuring from when work begins rather than when the customer asked hides the first queue, often the longest.
- Reporting only the average. A few very long items can hide behind a reasonable mean; report a high percentile too.
- Optimizing one stage. Making one team faster while the queue in front of the next team grows leaves lead time unchanged.
- Too much work in progress. Starting more items does not finish them sooner; by Little's Law it makes each one slower.
- Inconsistent definitions. If one team measures to dispatch and another to delivery, their numbers cannot be compared.
- Ignoring rework. Items that loop back to an earlier stage add lead time that stage-by-stage averages often miss.
Frequently Asked Questions
What is lead time?
Lead time is the total elapsed time from when a request is made to when it is fulfilled, such as from a customer placing an order to receiving it. It includes all waiting, handoffs and rework, not just the time someone spends working.
What is the difference between lead time and cycle time?
Lead time runs from the customer's request to fulfillment. Cycle time, in its most common usage, runs from when work actually starts on an item to when it is finished, so it excludes the wait before work begins. Definitions vary, so state yours explicitly.
How do you calculate lead time?
For one item, subtract the request date from the fulfillment date. For a process, report the median and a high percentile of those durations. Across a stable system, Little's Law gives average lead time as average work in progress divided by average throughput.
What is Little's Law?
A relationship proven by John Little in 1961: in a stable system, average work in progress equals average throughput multiplied by average lead time. It implies that, at constant throughput, reducing work in progress reduces lead time.
What is time to market?
The lead time of product development: the elapsed time from a product concept being approved to the product being available to customers.
How do you reduce lead time?
Map the value stream from request to fulfillment, separate working time from waiting time, and remove the largest queues first, usually at handoffs, approvals and batched steps. Limit work in progress, and avoid optimizing one stage while the queue moves elsewhere.
What is supplier lead time?
The time from placing a purchase order with a supplier to receiving the goods or service. It is a key input to inventory planning and procurement.
How does business architecture help reduce lead time?
Lead time is the headline measure of a value stream, and each slow stage traces to the business capabilities it depends on. Mapping stages to capabilities shows which capability improvements will shorten the streams customers care about, and lets the business case promise and measure a lead time reduction.
Pro Tips
- Start the clock when the customer asks, not when your team starts work.
- Report median and 85th or 95th percentile lead time side by side.
- Before adding people, count the work in progress. Finishing before starting usually shortens lead time faster.
- Map one value stream end to end, with process time and wait time per stage, before choosing any improvement.
- Tie each slow stage to the capability that causes the wait; that is where the investment belongs.