Complexity describes many interacting elements or moving parts in a system. Friction describes the resistance or effort a person or team actually experiences going through it -- complexity can exist without producing felt friction, and friction can arise from a simple process executed poorly.
Two claims that often travel together, but aren't the same
These two aren't the same claim, even though they often travel together. A system can have many interacting parts (complexity) and still feel smooth to use, if all those parts are well-designed and mostly invisible to the person going through it. Conversely, a genuinely simple, three-step process can feel like a struggle (friction) if even one of those steps is confusing or poorly built.
Complexity without much friction: "The pricing engine has a lot of interacting rules under the hood, but the sales team barely notices -- the interface hides almost all of it."
Friction without much complexity: "It's a simple three-field form, but the error messages are so unclear that people give up halfway through."
When both are present together
Both together: "The expense system is genuinely complex -- five approval paths depending on amount and category -- and that complexity is exactly what's producing the friction employees feel filing a report."
Complexity and friction can also be causally linked -- the complexity is the reason the friction exists -- without being the same observation. Naming both separately is more precise: complexity explains why, friction names what the user actually feels.
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 the mix-up leads to the wrong redesign
Diagnosing "complexity" when the real, actionable issue is felt friction points a redesign effort at reducing moving parts, when the actual fix is reducing the effort someone experiences -- and the reverse misdiagnosis is just as common. A team that hears "this is complex" might respond by trying to eliminate rules or paths, which can be expensive and sometimes impossible if the underlying business logic genuinely needs them. A team that hears "this is causing friction" is pointed instead at the interface and the experience -- often a cheaper, more targeted fix that leaves the necessary complexity intact but hidden.
The question that separates the two
The mistake is assuming a complex-sounding system must be the source of friction, or that a simple-sounding one can't be. What matters is the effort actually felt, not how many moving parts exist underneath it. Before calling something "complex," ask whether anyone is actually struggling because of it -- if not, the complexity may be well-managed and not worth touching at all.
Why this distinction changes the conversation
Naming the two separately also changes who owns the fix. A complexity problem often belongs to whoever designed the underlying rules or logic; a friction problem often belongs to whoever designed the interface or the step-by-step experience of using it. A proposal that says "this is too complex" when the real issue is a confusing form can end up in the wrong team's queue entirely. Naming the felt friction specifically -- and, separately, whether the complexity behind it is actually necessary -- routes the fix to the person who can actually make it.
Practice scenarios
Practice using friction in situations like:
- distinguishing many moving parts (complexity) from actual felt effort (friction)
- recognizing when complex underlying logic is producing real friction for a user
- avoiding a redesign that removes complexity without actually reducing felt friction
Useful practice phrases:
- "This system is complex, but it doesn't create much friction for the user."
- "This form is simple, yet it's producing real friction because of the error messages."
- "The complexity is exactly what's producing the friction people feel."
Complexity is what a system has; friction is what a person feels going through it. A fix aimed at one won't necessarily touch the other.
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.