Friction is diffuse drag spread across a whole process; a bottleneck is one specific, identifiable stage whose limited capacity caps how much can get through, no matter how much demand shows up. The test is whether the evidence points at the whole process or at one stage.
The test in practice
"Onboarding feels harder than it should" across several steps is friction. "Nothing can move past legal review because one person can only clear five contracts a week" is a bottleneck -- a hard, identifiable ceiling set by one stage's capacity.
Friction: "Our signup flow has friction throughout -- extra fields, unclear error messages, a slow confirmation email."
Bottleneck: "Contract review is the bottleneck -- one lawyer can only clear five contracts a week, no matter how many come in."
Staying consistent with the app's own bottleneck content
This boundary is deliberately kept consistent with the app's own published bottleneck content: as "What Does a Bottleneck in a Sales Funnel Look Like?" puts it, "'Friction' describes a feeling across the whole funnel. 'Bottleneck' names the one stage actually capping how many people get through it." That framing carries over directly: friction is the general texture of a process, a bottleneck is the one gate deciding total throughput.
From vague to specific
"Vague: 'there's friction in our funnel.' Specific: 'lead qualification capacity is capping how many leads convert' -- that specificity is what turns a friction complaint into a bottleneck diagnosis."
Want to learn "Friction" 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 →Moving from a friction complaint to a bottleneck diagnosis isn't just a vocabulary swap -- it requires actual evidence that one stage, specifically, is what's capping the numbers. Without that evidence, the more honest word is still friction.
Why the mix-up matters
The common mistake is describing general process friction as if it were a bottleneck. Unless one identifiable stage is capping how much advances, the accurate word is friction, not bottleneck -- and the fix is different: broad experience improvements for friction, added capacity at one stage for a real bottleneck. Calling ordinary friction a "bottleneck" points a team at the wrong lever -- staffing up one stage that was never actually capping anything, while the real drag stays spread across the whole process untouched.
The reverse mistake is just as costly
The reverse mistake happens too: describing a real bottleneck as if it were just "general friction" can undersell how fixable the problem actually is. A vague friction complaint about a whole process can feel overwhelming, like it needs a broad, expensive redesign -- when the truth is that one specific stage, once given more capacity, would unblock the entire flow. Correctly identifying a bottleneck as a bottleneck, rather than diffuse friction, can turn a project that looks like it needs months of rework into one fix at one stage.
Practice scenarios
Practice using friction in situations like:
- deciding whether a scenario describes diffuse friction or one specific bottleneck
- turning a vague friction complaint into a specific, evidence-backed bottleneck diagnosis
- choosing the right fix -- broad improvement for friction, added capacity for a bottleneck
Useful practice phrases:
- "This is friction throughout the process, not one bottleneck."
- "Contract review is the bottleneck -- nothing else is capping volume."
- "Lead qualification capacity is what's actually capping conversion."
Friction is the texture of a process; a bottleneck is the one gate that decides how much gets through it. Confuse the two, and you fix the wrong thing.
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.