Loading…
Loading…
Users have preexisting beliefs about how things should work.
stellae.design
Users bring expectations shaped by past experiences. When your design matches those expectations, everything feels intuitive; when it doesn't, confusion and frustration follow.
Users transfer expectations they have built from one familiar product to another. When a new design aligns with their existing mental model, they can navigate it without learning; when it conflicts, they must rebuild their understanding from scratch.
File manager using folder/file metaphor
Familiar hierarchy with drag-and-drop, matching users' desktop experience
File manager using abstract tag-based organization
Novel system that doesn't match how users think about file organization
Mental models determine how quickly users can become productive with a new interface. When a design contradicts established expectations, users make errors, feel lost, and often abandon the product entirely. Aligning with existing mental models dramatically reduces the learning curve and support burden.
Operating systems use folders, files, and a trash can to mirror the physical office environment users already understand. This metaphor lets first-time computer users organize documents without learning abstract file-system concepts. The alignment with physical-world mental models was key to mainstream computer adoption.
Online stores adopted the shopping cart metaphor from physical retail. Users immediately understand they can add items, review their selection, and proceed to checkout. This familiar flow reduces the cognitive overhead of transacting online.
Snapchat's early interface relied on hidden gestures with no visible affordances — swiping in various directions to access different features. New users had no mental model for these interactions and frequently missed core functionality. The app eventually added navigation bars to align with established expectations.
Google Docs preserved the familiar toolbar and document layout from desktop word processors while adding real-time cursors and commenting. By respecting users' mental model of document editing, Google only needed to teach one new concept — simultaneous collaboration. This incremental shift made adoption far smoother than a radically new editor would have.
• Teams sometimes assume their own mental model of the product matches the user's, leading to 'obvious' navigation that only makes sense internally. Another common mistake is over-indexing on a single competitor's model without verifying that users actually share that expectation. Mental model research from one demographic can also be incorrectly generalized to an entirely different audience.
| Check | Good Pattern | How to Test |
|---|---|---|
| User research on expectations | Card sorts and task analyses reveal how users naturally group and access information, and your IA reflects those findings. | Run open card sorts with 15-20 representative users. Compare their groupings against your planned navigation structure and measure agreement rates. |
| Familiar interaction patterns | Core interactions (navigation, search, forms) follow conventions users already know from comparable products. | Conduct a first-click test or unmoderated usability test with new users. Measure whether users attempt the correct action on the first try without guidance. |
| Terminology alignment | Labels and categories use the language your users use — not internal jargon or technical terms. | Run a tree test or highlighter test to verify that users associate your labels with the right content. Aim for a direct-success rate above 70%. |
When you are deliberately creating a new category of product where no strong mental model exists yet, or when existing mental models lead to harmful behaviors that need to be unlearned — for example, security workflows that must override convenience habits.
Was this article helpful?