# Feature friction analysis improves UX decisions Comparing the steps, context switches, and hidden controls required to complete the same task exposes interface friction that feature lists miss, making those task-level differences a better guide for UX decisions. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds when two interfaces support the same user goal and the task path can be observed or reproduced. - Step counts are evidence, not the whole verdict: one clear step can impose less cognitive load than several ambiguous ones, and expert shortcuts can hide novice friction. ## Links - [[3. Resources/Literature Notes/Media Library - Command Center and Media Tools]] — applies-in: moving frequent media actions into a command center cuts task steps and interface hunting. - [[3. Resources/Literature Notes/Media Library - Image Editing Interface]] — applies-in: unifying crop controls and thumbnail states makes the editing path more coherent. - [[Developer-Tool Adoption Tracks Cognitive-Load Reduction Not Feature Count]] — extends: task-path friction is the interface-level form of the cognitive overhead that determines whether capable users adopt a tool. - [[3. Resources/MOCs/Product & Startup Instincts MOC]] — applies-in: the MOC lists this note under Permanent additions (synthesis 2026-07-21 — run 6). ## Source - [[3. Resources/Readwise/Articles/Iterating on Notes in WordPress]]