Mental Models
A mental model is a person’s internal, partial representation of how a system works and what actions will produce.
Direct explanation
What it means
People predict from experience, interface cues, and explanations. Their model can be useful without matching implementation; design should make the operationally important parts accurate.
When the interface teaches the wrong cause, scope, or state, users make reasonable but damaging predictions and cannot recover confidently.
Research anchor: Philip N. Johnson-Laird, 1983
Research and interpretation
What the research found
Mental-model theory proposed that people reason by constructing internal representations of possibilities rather than manipulating formal rules alone.
The construct remains influential across cognitive science and HCI, though different research traditions define and measure models differently.
Popular advice versus careful use
Common shorthand: Designers should make the interface match one universal user expectation.
Learn the audience’s current predictions and make the system’s important state and consequences easier to model accurately.
How designers apply it
- 01
Explain whether cloud files are local, synced, shared, or only linked.
- 02
Show permission inheritance before an admin changes a role.
- 03
Align navigation vocabulary with users’ domain concepts.
Original UI examples
desktop collaboration
Shared drive
Folder icons and a status panel distinguish owned, shared, and shortcut items.
People can predict what moving or deleting each item affects.
mobile health
Medication reminder
A skipped dose remains in history and does not silently move the next scheduled dose.
The timeline teaches an accurate relationship between confirmation and schedule.
A sync-status display
Less effective
Use one checkmark for saved locally, uploaded, and shared with collaborators.
Better fit
Label each state and explain what remains pending or visible to others.
Implementation detail can stay hidden if the user-facing consequences remain predictable.
Limits and failure modes
Mental models are inferred from behavior and explanation; they are incomplete, task-specific, and can change during use.
Common mistakes
- Treating the designer’s conceptual model as the user’s existing model.
- Adding a tutorial instead of correcting contradictory system behavior.
When it should not dominate
- To demand that users learn internal architecture they do not need.
- When a simple direct mapping already makes consequences obvious.
Responsible use
Accessibility
Use consistent language, explicit states, and multiple representations; include people who use assistive technology because alternate interaction paths can produce different system models.
On mobile: Preserve state across interruptions and make hidden background activity inspectable.
Ethics and context
Do not cultivate a false model of privacy, automation, ownership, or AI capability to make a product seem simpler or safer.
On desktop: Use persistent overviews for scope and relationships, with detail available on demand.
Designer checklist
- Ask users to predict the result before acting.
- Map labels and feedback to state, scope, and consequence.
- Investigate repeated errors as model evidence.
Check your understanding
Which statement applies Mental Models most carefully?
Practice and continue learning
See ideas in real interfaces
These external interfaces are editorial references, not examples created to demonstrate this principle.
Sources and further reading
- 01Open source
Mental Models
Philip N. Johnson-Laird · 1983 · Harvard University Press
Book · primary or original source
- 02Open source
The Design of Everyday Things: Revised and Expanded
Donald A. Norman · 2013 · Basic Books
Book · primary or original source
Continue the graph
Related principles
model
Conceptual Models
A conceptual model is the designed explanation of a system’s objects, relationships, actions, and state that the interface presents to users.
heuristic
Jakob’s Law
People bring expectations learned from other products, so familiar conventions often reduce the effort needed to begin using a new interface.
principle
Natural Mapping
A mapping feels natural when the arrangement or movement of controls corresponds clearly to the arrangement or behavior of their effects.