"Marketing creates friction" reads as an accusation. In most cases, the actual cause of friction is structural -- an unclear handoff, an ownership gap, or a tooling boundary -- not a person or team's fault, and naming the structure instead of the people keeps the observation professional rather than accusatory.
Where the habit comes from
ESL learners often default to person-blame language when the actual cause of friction is structural: an unclear decision right, a tooling boundary, or conflicting incentives between two teams, none of which any one person or team chose on purpose. The instinct to name a subject for the sentence is natural -- English sentences want a subject doing something -- but "marketing" isn't the right subject when the real cause is a gap between marketing and another 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 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 this is more than a tone fix
This is a different move from simply softening the tone. The rewritten sentence isn't just gentler -- it names a different, more accurate cause. A softened version of "Marketing creates friction" that still blames marketing hasn't actually fixed the underlying error, even if it sounds nicer. The real fix is diagnostic: find the structural gap, name that gap, and let the two teams work from a shared, accurate description of the problem.
What this changes downstream
The distinction matters because the two phrasings point toward completely different next steps. "Marketing creates friction" points toward fixing marketing's behavior -- a conversation that puts one team on the defensive and usually goes nowhere. "There's friction in the handoff because ownership isn't defined" points toward fixing a process -- assigning ownership, clarifying a decision right, aligning two systems -- something both teams can act on together without anyone needing to feel blamed first.
When a person actually is the cause
None of this means a person or team is never the cause -- sometimes the evidence genuinely does point at a specific decision one team made. The point is to check the evidence before defaulting to blame language. If the actual cause is an undefined handoff, an unclear decision right, or two systems that don't talk to each other, naming that structure is more accurate, not just more polite -- and it's the version of the sentence a reasonable reader is more likely to trust, because it explains the mechanism instead of just assigning fault.
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."
A structural cause and a person to blame can look identical from a distance. Naming the actual structure is what turns a complaint into something two teams can fix together.
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.