Throughput and capacity describe two different numbers about the same system, and confusing them is one of the most consequential mistakes you can make in an operations conversation.
"Capacity" is the maximum a system could handle; "throughput" is what it's actually completing. A system can have unused capacity while throughput stays flat, because a bottleneck elsewhere is holding it back.
The profile's second-highest-priority boundary
This is the second-highest-priority near-synonym boundary in this batch, right behind bandwidth. The two numbers can diverge sharply: adding capacity does nothing for throughput if the constraint limiting flow sits somewhere else in the system. Reporting capacity as if it were throughput overstates what's actually being delivered; reporting throughput as if it were capacity understates how much room the system might still have once the real bottleneck is fixed.
"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.
Adding capacity doesn't automatically move throughput
The third example is the pattern worth remembering, because it's the one that surprises people who haven't seen it before. Adding capacity feels like it should help -- more servers, more headcount, more machines -- but if the actual constraint is one narrow step downstream, all that new capacity just sits idle behind it. Throughput only moves once the real bottleneck gets fixed, not when capacity somewhere else in the system goes up.
Want to learn "Throughput" in depth?
Lyra Practice teaches advanced non-native professionals the nuance of high-value expressions like this one, then has you practice using them in realistic work scenarios.
Start learning for free →The mistake
The mistake is reporting a system's rated or theoretical maximum as if it were the actual throughput being achieved -- capacity describes potential, not performance. A system rated for 300 that's actually delivering 200 has a capacity of 300 and a throughput of 200; presenting the 300 figure as the current throughput overstates what's genuinely getting done.
Why the gap between the two numbers is itself useful information
The gap between capacity and throughput isn't just a number to correct -- it's diagnostic information in its own right. A large, persistent gap tells you there's a real bottleneck somewhere worth finding and fixing. A small or shrinking gap tells you the system is running close to its actual limits, and further throughput gains will likely require raising capacity itself, not just clearing a blockage. Reporting both numbers together, rather than picking whichever one sounds better, gives a reader that diagnostic picture instead of a single, less useful figure.
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..."
Capacity is what a system could do. Throughput is what it's actually doing.
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.