Delay means elapsed time itself is the entire issue, with no meaningful added effort. Friction means a troublesome step or interaction is causing real difficulty -- delay may be one effect of that friction, but it isn't the whole claim.
The test: is waiting the only complaint?
The test is whether waiting is the only complaint. "The approval takes three days" with nothing else wrong is a delay -- pure elapsed time. "The approval takes three days because the form has to be manually re-entered into two separate systems" is friction -- a troublesome step that happens to produce a delay as one of its effects, but the actual problem is the step itself, not just the clock.
Delay: "The only issue is that legal review takes three business days -- nothing else about the process is hard, it just takes time."
Friction: "The approval isn't just slow -- the requester has to manually re-enter the same information into two different systems before it can even start."
When a delay turns out to be friction
"What looked like a simple delay turned out to be friction: the wait wasn't from a queue, it was from a broken handoff that required rework each time."
A queue is a delay a system will clear on its own given time. A broken handoff that requires manual rework every single time is friction, even though it also produces a wait -- because the wait isn't the fixable part, the handoff is.
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 →Why picking the wrong word misdirects the fix
Naming pure waiting time as "friction" overstates the problem; naming a genuinely difficult, effort-adding step as mere "delay" understates it and points the fix at the wrong lever -- speeding up a queue instead of redesigning a step. A delay is fixed by adding capacity or shortening a queue. Friction is fixed by removing or simplifying a step. Applying the delay fix (more capacity) to a friction problem (a broken handoff) doesn't help, because the handoff will keep generating rework regardless of how many people are available to process it.
The common mistake
The common mistake is treating every slow step as friction. If the only real issue is elapsed waiting time with nothing else costing extra effort, "delay" is the more precise and less alarming word -- and using it correctly avoids making a simple queue sound like a broken process.
A simple test to apply
One reliable test: imagine the exact same wait, but instantly resolved by adding more capacity at that one step. If the problem genuinely disappears, that's a delay. If the same rework, confusion, or extra effort would still exist even with unlimited capacity thrown at it, that's friction, and the wait is just one visible symptom of it. This test is especially useful in a status update or a proposal, because it also tells you what to ask for -- more capacity for a delay, a redesigned step for friction.
Practice scenarios
Practice using friction in situations like:
- deciding whether a scenario's evidence supports friction or plain delay
- recognizing when an apparent delay is actually being caused by friction underneath it
- choosing between adding capacity (for delay) and redesigning a step (for friction)
Useful practice phrases:
- "This is a delay -- nothing else about it is hard, it just takes time."
- "This is friction, not just delay -- the step itself causes rework."
- "The wait looked like a queue, but the real cause was friction in the handoff."
A delay is a clock problem; friction is a step problem that happens to also cost time. Fixing the wrong one leaves the real cause untouched.
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.