Resources/Glossary/
Throughput
Lean Metrics and Measurement

Throughput

How fast good parts actually leave your shop. Not how busy you look.

Updated
·
4
min read
Definition

What is Throughput?

Throughput is the rate at which a process produces good output over a period of time, usually measured in units per hour, shift, day, or week. It counts only parts that pass quality at the end of the line, which is why scrap and rework drag throughput down even when the machines never stop. It is the single most honest signal of how a shop is actually performing.

Throughput is the rate at which good parts leave the process, and it is the metric most small shops misread the worst. The temptation is to count everything the machines made and call it a productive day. The honest count is the one that subtracts rework, scrap, and parts still sitting in the rework cage. A shop with high machine utilization and low throughput is a shop in trouble, but the dashboards will not tell you that until the customer does.

"Busy is not the same as productive. Throughput is the only number that knows the difference."

How throughput works

Throughput is calculated by dividing good output by elapsed time. The two parts of that calculation are where the disagreements live. Good output means units that passed final quality, not units the machines produced. Elapsed time means the wall-clock window you are measuring, not the time the machines were running. The first distinction strips out the hidden factory of rework. The second strips out the trick of timing only the productive hours and ignoring the changeovers, breakdowns, and waiting.

Anatomy of a throughput number

A real throughput number has three components worth pulling apart:

  • The count. Good units, full stop. Anything that needed rework before passing final does not count until it passes.
  • The window. A consistent interval. An hour, a shift, a day, a week. Mixing windows produces nonsense.
  • The mix. Throughput on easy parts is different from throughput on hard parts. Note the mix or the average lies to you.

Throughput is also the output of the slowest step in the chain, not the average of every step. If a shop has five operations and the fourth runs at 60 units an hour while every other operation runs at 100, the shop's throughput is 60. The four faster operations are producing inventory that will sit. This is why lean shops fix the constraint first and ignore the rest.

Where throughput fits on the shop floor

Imagine a 25-person CNC job shop running parts for two HVAC contract customers. The owner has been tracking machine hours and reporting 85 percent utilization to the customers, who are happy. Then a shipment misses its date by ten days and the relationship cools. The owner walks the floor and finds the answer: 85 percent utilization, yes, but throughput on the shipping dock has been declining for six weeks. The rework cage has grown. A worn fixture on the second op produces parts that pass at the machine and fail at final inspection. The machines are busy. The good output is shrinking.

The fix is not better utilization tracking. The fix is putting a throughput board at the shipping dock with a daily target and a daily actual, updated by hand. The fixture gets noticed within two days because every operator can see the gap on the board, and the conversation moves from "we ran hard today" to "we shipped what we promised." Throughput is the metric that surfaces problems machine-hours-tracked will hide.

Common mistakes with throughput

  • Counting gross output instead of good output. Parts the customer rejects do not count. Parts the customer accepts after the third reorder do not count three times.
  • Picking the wrong measurement point. Throughput measured at the first operation tells you what the first operation made, not what the shop shipped. Always measure at the last step that actually matters to the customer.
  • Treating throughput as a target. Pay-per-unit schemes inflate the count and ruin quality. Throughput is a result of good flow, not a goal you push toward.
  • Mixing windows or mixes without noting it. A weekly throughput number that averages across different product mixes is a number that lies. Either pin the mix or report by mix.
  • Reporting throughput from a dashboard nobody on the floor sees. Throughput lives on the shop floor. If only the office sees it, it is a vanity metric.

Throughput and related Lean tools

Throughput is one of the canonical lean KPIs and the rate-counterpart to throughput time, the duration a single unit takes to travel the value stream. It is closely tied to overall yield and first-pass yield, since only good output counts. And it is the result side of capacity utilization: chasing utilization usually drops throughput, while improving flow lifts both at once.

Common questions

The questions we hear most about this term.

How does throughput work as a daily metric?
You pick a measurement point, usually the last operation or the shipping dock, and you count good units leaving it over a fixed window. A shift, a day, a week. Anything caught and reworked or scrapped before that point does not count. The window matters: shorter windows surface problems sooner but bounce around with normal variation. Most small shops settle on a daily good-output number tracked against a target, with a weekly rolling average to smooth out the noise. The number lives on a board the floor can see, not in a report nobody reads.
How is throughput different from throughput time?
Throughput is a rate. Throughput time is a duration. Throughput tells you how many good units leave the shop per hour or per day. Throughput time tells you how long a single unit takes to travel from start to finish. They move in opposite directions when flow improves: throughput goes up, throughput time goes down. People mix them up constantly because they share a word. If someone asks for "throughput" and means the elapsed time per unit, they are asking about throughput time.
What are common mistakes with throughput?
The biggest one is measuring gross output instead of good output. Counting parts at the press and ignoring rejects at final inspection produces a flattering number that does not match what shipped. The second is treating throughput as a target rather than a result. When operators are paid per unit produced, they will produce units. Quality drops, machines get pushed past their service window, and the throughput number eventually crashes anyway. The third is averaging across mix without noting which products ran. A high-throughput day on easy parts is not the same as a high-throughput day on hard parts.
When should I focus on throughput versus capacity utilization?
Focus on throughput when the customer is waiting. Focus on capacity utilization only when throughput is already where you need it and you are trying to understand whether you have room to grow. Most small shops have the priority backward. They chase utilization, pushing every machine toward 100 percent, and end up with high WIP and lower throughput because the loaded machines block flow. The right sequence is to set a throughput target, hit it reliably, then check utilization as a diagnostic.
What does good throughput tracking look like on the shop floor?
A whiteboard near the shipping area with two columns: target and actual. Updated by hand every hour or every shift by the person responsible for that interval. A short note next to any shortfall explaining what got in the way. No software dashboard, no after-the-fact report. The floor sees the gap in real time and reacts. At the end of the week, the pattern of shortfalls tells you where the biggest constraints are. That is the data lean improvement work is built on.

Ditch the whiteboards and spreadsheets.

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