Throughput and bandwidth get used almost interchangeably in casual workplace speech, and the app already teaches bandwidth on its own -- which makes this the single highest-value pair to get straight.
"Throughput" describes work actually completed and moving through a system or team; "bandwidth" describes available capacity or willingness to take on new work. "I don't have bandwidth" is about starting something new; "our throughput is low" is about how much is actually finishing.
Starting versus finishing
This is the single highest-value near-synonym boundary in this entire batch, named explicitly because bandwidth is already a taught word in this app -- an objective product fact about what learners here already know, not a stylistic preference on our part. The same actual-vs-potential logic reappears in networking, where technical bandwidth (a channel's capacity) and throughput (what's actually transferred) form a classic confusable pair -- see Bandwidth vs Throughput in Technical Contexts for the same distinction framed from bandwidth's side, and What Does Bandwidth Mean at Work? for the general human-capacity sense this article contrasts against.
"I don't have bandwidth to take on the new project this week." -- availability to start, not a completion claim.
"Our support throughput is still low, even though we now have more bandwidth on the team." -- both words correctly distinguished in one sentence: more room to start hasn't yet translated into more finished.
"The link has plenty of bandwidth, but throughput stays low because of retries eating into what's actually transferred." -- the same actual-vs-potential logic in a technical context.
Why the two numbers can move independently
The second example is the one worth sitting with: bandwidth going up doesn't automatically move throughput. A team can free up room to start new work -- clearing a backlog of blockers, adding headcount, reprioritizing -- and still see the same completion rate for weeks, because the constraint holding throughput flat was never a shortage of starting room in the first place. The reverse is also possible: throughput can look healthy while bandwidth is genuinely tight, if the team is finishing what it has without any room to absorb something new.
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 using "bandwidth" to describe how much work is actually getting finished, as in a status update that reports a completion rate under the heading "our bandwidth this quarter." Bandwidth measures room to start; throughput measures what's actually completed. Swapping the two in either direction misreports which problem a team actually has.
Why picking the wrong one leads to the wrong fix
Getting this pair right matters beyond precision for its own sake, because the two words point toward genuinely different fixes. A low-bandwidth problem gets solved by freeing up room -- reprioritizing, clearing blockers, adding people. A low-throughput problem, especially one where bandwidth already looks fine, gets solved by finding the actual bottleneck in the completion process itself. Reaching for the wrong word can send a team chasing the wrong fix entirely: adding headcount to solve a bottleneck problem, or reshuffling priorities to solve a problem that was never about available room in the first place.
Practice scenarios
Practice using throughput in situations like:
- distinguishing an availability claim from a completion claim in a status update
- explaining why more bandwidth on a team hasn't yet moved throughput
- correcting a report that labels a completion rate as "bandwidth"
Useful practice phrases:
- "I don't have bandwidth to take on..."
- "Our throughput is still low, even though we now have more bandwidth on..."
- "Bandwidth measures room to start; throughput measures what's actually finished."
Bandwidth is room to start. Throughput is what's actually finishing.
Keep the two separate, and a status update tells the reader which problem you actually have.
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.