SUMMARY: Interface friction is the drag created when a surface asks users or operators to do extra interpretation before they can act.
Friction can be useful when it slows dangerous behavior. Most friction is not that noble. It appears as misaligned controls, vague labels, buried routes, inconsistent access states, stale navigation, crowded archives, and pages that technically work while quietly wasting attention.
The cost compounds. A reader who cannot find the next surface leaves. A moderator who cannot read the pattern repeats the same cleanup. A crawler that sees weak structure may index the page but miss the route.
Friction Types
Label friction: titles, links, or buttons that do not name the action or topic clearly.
Route friction: useful pages that exist but are hard to reach from related material.
Trust friction: login, registration, forum, or chat states that do not make the user’s position clear.
Scan friction: lists, archives, or rooms that require too much reading before the signal appears.
Countermeasure
Pair friction review with signal bridges. A bridge creates the route. Friction review checks whether the route can actually be followed.
Operator Rule
When a surface works but still feels slow, inspect the interpretation cost.
Field assessment: friction is often the first symptom of a system outgrowing its labels.