"There's just a lot of friction lately" gives a reader nothing to act on: not which system, not which handoff, not which team. The sentence fails because it names no process, step, or relationship at all -- it reads as an unfalsifiable complaint nobody can investigate or fix, not a diagnosis.
The word's real strength turns into its most common misuse
Friction's real strength is that it can flag a problem before the exact cause is confirmed. That strength turns into the word's most common misuse the moment nothing at all gets named. A vague complaint borrows the credibility of a precise diagnostic word without doing any of the diagnostic work.
Compare the two:
Vague: "There's just a lot of friction lately." Precise: "There's friction in the vendor-onboarding process -- new vendors wait an average of two weeks for system access."
"Engineering has been dealing with friction" says nothing; "engineering has been dealing with friction in the deploy pipeline, specifically the manual approval step" says something a team can act on.
"The whole project feels like friction" is a mood, not a diagnosis; "the handoff between design and engineering is where the friction is" points at a specific place to look.
The fix is always the same move
The fix doesn't require knowing the root cause yet -- that's exactly the point of the word. It requires naming the process, step, or relationship the drag is attached to, even if the deeper "why" is still under investigation. "There's friction in the handoff between sales and onboarding" is a legitimate, precise use of the word, even before anyone has figured out why that handoff is slow.
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 →Not the same as being brief
This is a different failure from simply being brief. A short, specific sentence -- "friction in the handoff" -- is fine and often preferable to a long one. The problem is naming nothing at all, not naming too little detail. Three words that point at a real place beat a full paragraph that points at nothing.
Why this matters in a status update specifically
A status update exists so someone can decide what to do next. "There's a lot of friction lately" gives a reader no lever to pull -- no system to check, no owner to ask, no metric to watch. The moment you name the process or step, the same sentence becomes something a manager, a peer, or an incident channel can actually act on.
A habit worth building
One reliable habit: before sending a friction observation, ask yourself whether a colleague reading it cold, with no other context, could point to the specific system, step, or handoff you mean. If the honest answer is no, the sentence needs one more piece of information before it's ready to send -- not a longer explanation, just the name of the actual place. That single addition is usually the difference between a complaint that gets acknowledged and forgotten, and an observation that gets picked up and fixed.
Practice scenarios
Practice using friction in situations like:
- catching a vague, cause-free friction complaint before sending a status update
- rewriting a mood-based complaint into a diagnosis a team can act on
- naming a process or step even when the root cause isn't known yet
Useful practice phrases:
- "There's friction in the vendor-onboarding process, not just friction in general."
- "The friction is in the deploy pipeline's manual approval step."
- "I don't know the root cause yet, but the friction is in this specific handoff."
A precise diagnosis doesn't require knowing the cause yet -- it only requires naming the place. That's the one habit that separates a real friction observation from a complaint.
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.