Mental Models in HCI

Mental models are users’ subjective ideas of how a system works. In HCI, aligning those expectations with actual system behavior makes interfaces easier to learn and reduces errors.

Why mental models are crucial

When people use a new system, they build on experience and analogies. Mental models help them to explain functions, predict actions and avoid problems - for example when exploring an unfamiliar interface.
If this model is missing, users feel disoriented. If it is wrong, frustration arises: for example, when the “Save” button does not do what was expected.

How users form mental models: familiar patterns and feedback

People build mental models from prior experience, visible interface cues and the results of their actions. A shopping-cart icon suggests that selected items can be reviewed before purchase; a magnifying-glass icon suggests search. If the same icon instead opens a filter or immediately commits an irreversible action, the interface violates that expectation. Clear feedback then helps users update their understanding of how the product actually works.

Three ways an interface teaches users what to expect

Mental models do not appear all at once. Users combine what they already know with clues in the interface, then revise their assumptions as they use the product:

1. Transfer from familiar products: Someone who has used online shops expects a cart to hold items before checkout. A new shop can build on that expectation instead of explaining the pattern from scratch.
2. Interpret visible cues: A folder icon suggests that files can be grouped and opened. If selecting it immediately shares those files, the icon and action send conflicting messages.
3. Learn from consequences: After a user saves a document and sees “Saved just now,” they learn that changes are stored automatically. Without that status, they may keep looking for a separate Save button.

For example, a first-time user might assume that “Archive” deletes an email because both actions remove it from the inbox. A clear label, an archive location and an undo message teach the difference. Each later interaction reinforces or corrects that model.

Mental model, system image, and design model

Norman’s well-known model distinguishes three perspectives:

• Design model - the conceptual model designers build into the system
• System image - everything the system communicates, including its interface, documentation, and feedback
• User model - the understanding users develop from the system image and their experience

The system’s actual behavior is a separate consideration: it must be communicated through the system image so users can form expectations and understand the results of their actions. For example, a recycle-bin icon may suggest that a file is deleted even though it is initially moved to another storage location.

How design supports mental models

A good interface conveys functions intuitively. This is achieved through:

• Consistency - e.g. similar navigation as in known apps
• Affordances - such as buttons that look like real keys
• metaphors - such as “desktop”, “folder”, “recycle bin” or “shopping cart”
• feedback - for example through animations, sounds or status displays
• Error tolerance - e.g. “Undo” function or warnings before deletion

You can find out more about affordances here.

How to capture mental models

UX research uses various methods to make mental models visible:

• Card Sorting shows how users structure information.
• Interviews and Thinking-Aloud-Methods provide insight into thought processes.
• Concept Mapping visualizes explicit ideas.
• The comparison of user behavior with system logic uncovers model conflicts.

A practical workflow

1. Identify the key task and the behavior users should be able to predict.
2. Ask users to explain expectations before and during the interaction.
3. Compare their statements and actions with the actual system behavior.
4. Fix mismatches with clear labels, familiar patterns, feedback and reversible actions.
5. Re-test the changed flow with representative users.

These methods are closely linked to the pages on the Thinking-Aloud-Method and UX-Interviews.

Conclusion

Mental models are cognitive tools that we use to understand the digital world.
A user-centered design takes into account not only how a system works - but also how it is understood.
Because the better the system logic and mental models match, the more intuitive the use becomes.

Last modified: 1 November 2026