Throughput and capacity describe different features of the same system, and mixing them up can lead to poor choices.
Capacity is the amount a system can handle under stated conditions. Throughput is its actual completion rate over a stated period. A bottleneck can keep throughput below capacity.
Possible maximum or actual rate?
Capacity can sit unused behind a bottleneck.
Ready to go beyond the quiz on "Throughput"?
Take the full learning path: hear it in real workplace contexts, watch short explanations, learn its nuances and when to use it, then practice using it yourself.
Start learning for free →Now see if you can use it naturally yourself.
Try it yourself
You know how to use "Throughput," too.
Keep going with the full learning path — more workplace contexts, related expressions, and continued practice.
Continue with "Throughput" →There's more to "Throughput" than it seems.
You've got part of it, but the full learning path goes deeper into its nuances, workplace contexts, and when it sounds natural — then gives you practice using it yourself.
Learn "Throughput" in depth →Why the two numbers can differ
These numbers can differ sharply. More capacity may not improve throughput when another step limits flow. Reporting capacity as throughput overstates current delivery. The opposite error may hide room for growth. Always state the unit, period, and working conditions.
"The line has capacity for 300 units an hour, but throughput has been stuck closer to 200 because of a bottleneck at final inspection."
"We have the server capacity to handle far more traffic; the throughput ceiling right now is a single slow database query."
Leadership asked why throughput hadn't grown even though the team had added capacity -- the answer was that the new capacity sat unused behind the same unaddressed bottleneck.
Want to actually use "Throughput" naturally at work?
Understanding it is one thing. Practice its nuances, see how it works in real workplace situations, and use it yourself with feedback.
Start the "Throughput" learning path →Adding capacity doesn't automatically move throughput
The third example shows an important pattern. More servers, people, or machines may seem helpful. Yet added capacity can sit idle behind a narrow later step. Throughput may rise only after the team fixes the true limit. Demand, staffing, downtime, and process changes can also affect it.
The mistake
The mistake is presenting rated capacity as observed throughput. Capacity describes an ability under stated conditions, not current performance. Suppose a line is rated for 300 units per hour. If it completes 200, its observed throughput is 200 units per hour. Calling 300 the current throughput overstates completed work.
Why the gap between the two numbers is itself useful information
The gap between capacity and throughput can guide a review. A lasting gap may point to low demand, downtime, or a bottleneck. A small gap may mean the system is near its stated capacity. Still, bad data or different assumptions can create a gap. Report both numbers with their units, periods, and conditions.
Practice scenarios
Practice using throughput in situations like:
- explaining why added capacity hasn't moved a system's actual throughput
- distinguishing a rated maximum from a currently achieved completion rate
- diagnosing which specific step is the real bottleneck limiting throughput
Useful practice phrases:
- "We have the capacity for..., but throughput has been stuck closer to..."
- "Adding capacity here won't help if the real bottleneck is..."
- "That's our rated capacity; actual throughput has been..."
Explain unused capacity
Capacity is what a system can handle under stated conditions. Throughput is its observed completion rate.
Find the real bottleneck before you add more capacity that was never the constraint.
Lyra Practice helps advanced non-native English professionals learn the nuance of high-value workplace expressions and practice using them in realistic scenarios, so their English sounds natural, precise, and senior at work. Try Lyra Practice.