Resources/Glossary/
Throughput Time
Pull and Flow

Throughput Time

How long a part takes to travel the whole stream, start to finish.

Updated
·
4
min read
Definition

What is Throughput Time?

Throughput time is the elapsed time for one unit to travel the entire value stream, from the moment work begins on the raw material to the moment the finished unit is ready to ship. It includes every cycle time, every queue, every handoff in between. Throughput time differs from lead time in where the clock starts: throughput starts at work, lead time starts at order.

Throughput time and lead time get used interchangeably in most shop conversations, and that is fine for casual use. When something is broken in the value stream, though, the distinction matters. Lead time is the customer's clock. Throughput time is the floor's clock. Improving one without the other leaves either the floor sluggish or the customer waiting longer than the floor is.

"The clock starts when work starts. Everything that happens before that is procurement. Everything after is the stream."

How throughput time works

Throughput time is measured by following one unit from work-start to work-done. The unit is a part, a sub-assembly, or a finished product, depending on which slice of the value stream you are studying. The clock starts at the first value-adding operation. It runs continuously, regardless of whether the unit is being worked on, sitting in a cart, waiting for inspection, or staged for ship. It stops the moment the unit is ready for the next customer in the chain.

The math underneath is Little's Law applied to a value stream: throughput time equals work-in-process divided by throughput rate. If a shop has 500 parts of work in process and ships 100 parts per day, the average throughput time is five days. That formula is the most useful diagnostic in any shop that wants to understand why things take as long as they take. WIP and throughput time move together. Cutting WIP cuts throughput time. Adding WIP, without adding throughput, lengthens it.

The thing that surprises shops new to lean is the breakdown. Most throughput time is queue or wait time, not value-added work. A part that has eight hours of actual machining might have a throughput time of forty hours, because thirty-two of those hours are queue time between operations. The ratio of value-added time to total throughput time is called process cycle efficiency, and in most non-lean shops it runs between two and ten percent. The leverage is not in cutting the eight hours of work. It is in cutting the thirty-two hours of waiting.

The trick to seeing throughput time clearly is measuring it physically, not through software. Chalking a date on a WIP cart the moment material enters the floor turns throughput time into a number anyone can read by glancing at the cart. ERP reports tend to back out throughput time from system events, which often miss the actual physical wait. The chalk method is more reliable and faster to install.

Where throughput time fits on the shop floor

Picture a small contract machine shop running precision brackets for industrial OEMs that make ground-support equipment. Total ordered work-in-process across the shop is about 800 brackets. The shop ships about 200 brackets a week, or 40 a day. By Little's Law, average throughput time is 20 days.

The owner walks the floor on a Friday with a stopwatch and a date marker. The first cut happens. The bracket goes into a cart. Three days later, the cart is finally pulled for the second operation. Three days for one transition. The shop has six operations. If the pattern is similar at each handoff, eighteen days of throughput time is spent in carts, and only two days is in actual work. That single observation drives the entire improvement plan: do not buy a faster machine, do not add a shift. Cut the cart time. A WIP limit between each operation, sized to one day, brings throughput time from 20 days down to about 8 within a quarter, without touching the machining itself.

Common mistakes with throughput time

  • Averaging without looking at variation. An average hides spikes. The spikes are the flow problem.
  • Confusing it with cycle time. Cycle time is one operation. Throughput time is the whole stream including all the queues.
  • Measuring only through ERP events. Software events miss physical wait time. Chalk on a cart is more reliable.
  • Trying to fix it with faster machines. Most throughput time is queue, not cycle. Faster machines do not move the needle if the carts still sit.
  • Treating it as the customer-facing metric. Customers feel lead time, which includes order entry and material procurement. Throughput time is the floor's metric.

Throughput time and related Lean tools

Throughput time is closely tied to lead time, with the difference being where the clock starts. It is built from many cycle times chained together, with queue time between them. The dock-to-dock measurement is a close relative, scoped to the time between receiving and shipping. And process cycle efficiency, the ratio of value-added time to throughput time, is the metric that exposes how little of the stream is actual work and how much is waiting.

Common questions

The questions we hear most about this term.

How does throughput time work?
You pick one unit and follow it. The clock starts when the first operation begins on it, usually at the first cut or first stamping. The clock runs while the unit is being worked on, while it sits in carts between operations, while it waits for inspection, while it sits in the ship-ready rack. The clock stops when the unit is packaged and ready to leave. The total is throughput time. In most shops, more than 90 percent of that time is queue or wait, and only a small slice is actual value-added work.
How is throughput time different from lead time?
The difference is where the clock starts. Lead time starts when the customer places the order. Throughput time starts when the shop begins work on raw material. The gap between them is usually order-entry time and material procurement: the days between the order landing and the first cut happening. In a shop with weekly material deliveries, that gap can be five to ten days. Throughput time is what the floor controls. Lead time includes things the floor does not control, like supplier delivery and order paperwork.
Is throughput time the same as lead time?
In casual conversation, they often get used interchangeably, but they measure different things. Lead time is the customer's view: order to delivery. Throughput time is the shop floor's view: work begins to work finishes. A shop that improves throughput time without changing material procurement or order entry will improve lead time only partly. The two metrics are both useful, but they answer different questions. Lead time tells you what the customer feels. Throughput time tells you what the floor produced.
What are common mistakes with throughput time?
Measuring it by averaging is the first mistake. A throughput time average hides huge variation, and the variation itself is the flow problem. Tracking max and min alongside average tells more. Second mistake: confusing throughput time with cycle time at the bottleneck. They overlap but they are not the same. Throughput time includes the queue waits between operations, which often dwarf the bottleneck cycle. Third: trying to improve throughput time by speeding up cycle times instead of cutting queue time.
What does throughput time look like on the shop floor?
It looks like a date on a tag. A small fab shop wanting to see throughput time chalks a date on every WIP cart the first time material enters the floor. When the part ships, the difference between today and the chalked date is throughput time. The exercise is more reliable than any ERP report because the date is physical and cannot be backed out. Walking the floor at the end of a week and reading the dates tells you exactly where time is being spent in the stream. Old carts are the bottleneck.

Ditch the whiteboards and spreadsheets.

Same-day setup. No distributor lock-in. Zero stockouts. Top teams double revenue in 9 months.