"Marketing creates friction" can sound like an accusation. First identify the specific cause. It may be a handoff, an ownership gap, a technical boundary, a policy, or a team's decision. Name the cause supported by evidence.
Name the campaign handoff, not the department
Choose the diagnosis that points to a testable structure.
Ready to go beyond the quiz on "Friction"?
Take the full learning path: hear it in real workplace contexts, watch short explanations, learn its nuances and when to use it, then practice using it yourself.
Start learning for free →Now see if you can use it naturally yourself.
Try it yourself
You know how to use "Friction," too.
Keep going with the full learning path — more workplace contexts, related expressions, and continued practice.
Continue with "Friction" →There's more to "Friction" than it seems.
You've got part of it, but the full learning path goes deeper into its nuances, workplace contexts, and when it sounds natural — then gives you practice using it yourself.
Learn "Friction" in depth →Where the habit comes from
English grammar makes it easy to put a team in the subject position. That choice can turn a process problem into a broad accusation. Before naming marketing, identify the action or condition creating the friction. The cause may be an unclear decision right, a technical boundary, or conflicting incentives. In that case, name the structure instead of the whole team.
Naming the structure instead of the people
Instead of "Support keeps creating friction for engineering," say: "There's friction in the escalation handoff -- support and engineering don't have a shared definition of which bugs qualify as urgent."
Instead of "Legal is the friction in every deal," say: "There's friction in the contract-review step, because legal and sales are working from different versions of the standard terms."
"The friction isn't coming from either team -- it's that nobody owns the handoff once a deal closes."
Want to actually use "Friction" naturally at work?
Understanding it is one thing. Practice its nuances, see how it works in real workplace situations, and use it yourself with feedback.
Start the "Friction" learning path →Why this is more than a tone fix
This move does more than soften the tone. It replaces a broad claim with a diagnosis people can test. A polite sentence can still blame the wrong group. Identify the gap and explain how it affects the work. Both teams can then discuss the same problem constructively.
What this changes downstream
The two versions point toward different next steps. "Marketing creates friction" suggests that marketing's behavior must change. "There's friction in the handoff" points to a process improvement. The teams might assign an owner, clarify authority, or align two systems. An accurate cause makes the next action easier to choose.
When a person actually is the cause
A person or team can cause friction. Evidence may show a specific decision, delay, or repeated behavior. If so, state the action and its effect. Do not turn one event into a claim about every team member.
If the cause is a handoff or system gap, name that instead. This wording is not only more diplomatic. It is more useful because it explains how the problem occurs.
Practice scenarios
Practice using friction in situations like:
- rewriting a person-blaming complaint into a structural diagnosis
- naming an unclear handoff or ownership gap instead of a team's name
- keeping a cross-team observation professional rather than accusatory
Useful practice phrases:
- "There's friction in the handoff, not friction caused by that team."
- "Nobody owns this step yet -- that's the friction, not either team."
- "The friction is a tooling boundary, not a person's mistake."
Rewrite a legal-team accusation
A broad accusation can hide the actual cause. A specific diagnosis supports a practical fix.
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.