Conceptual Models
A conceptual model is the designed explanation of a system’s objects, relationships, actions, and state that the interface presents to users.
Direct explanation
What it means
It is the model a product offers, not the model users necessarily hold. Good labels, mappings, constraints, and feedback help users build a compatible mental model.
A coherent model makes features predictable across screens; contradictory metaphors and state rules force users to memorize exceptions.
Research anchor: Donald A. Norman, 2013
Research and interpretation
What the research found
Cognitive and design work established models as representations used to explain and predict system behavior.
Conceptual-model design remains foundational in HCI, though models are evaluated through user understanding rather than one universal formalism.
Popular advice versus careful use
Common shorthand: A diagram shown in onboarding gives every user the intended model.
Express a coherent model through the product’s language and behavior, then test whether users can predict important state and consequences.
How designers apply it
- 01
Define workspace, project, and organization scope consistently.
- 02
Model messages as sent objects with delivery states.
- 03
Explain automation as rules, triggers, and runs rather than magic.
Original UI examples
desktop SaaS
Automation builder
Triggers, conditions, actions, and run history use one stable vocabulary.
Users can predict why a workflow ran or did not.
mobile social
Shared album
Ownership, membership, and link access are distinct visible concepts.
People can predict who sees a photo and what removing it does.
A cloud-file workspace
Less effective
Mix folder, tag, shortcut, and shared-space behavior under one identical icon.
Better fit
Give each object a stable identity and explain move, delete, and sharing consequences.
Implementation detail may stay hidden if user-facing consequences remain coherent.
Limits and failure modes
Users build partial, varied mental models and may not adopt the designer’s intended explanation.
Common mistakes
- Documenting a model the interface behavior contradicts.
- Changing vocabulary between product, help, and support.
When it should not dominate
- To expose internal architecture unrelated to user goals.
- When direct feedback already makes a simple action fully predictable.
Responsible use
Accessibility
Keep terminology, structure, and state consistent across visual and assistive interfaces, help content, and alternate input paths.
On mobile: Preserve object and state identity across compact screens and interruptions.
Ethics and context
The model must not overstate AI agency, privacy, ownership, or system certainty.
On desktop: Use persistent overviews and inspectable relationships for complex scope.
Designer checklist
- List core objects, relations, states, and actions.
- Check terminology and behavior across surfaces.
- Ask users to predict consequences.
Check your understanding
Which statement applies Conceptual 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
The Design of Everyday Things: Revised and Expanded
Donald A. Norman · 2013 · Basic Books
Book · primary or original source
- 02Open source
Mental Models
Philip N. Johnson-Laird · 1983 · Harvard University Press
Book · primary or original source
Continue the graph
Related principles
model
Mental Models
A mental model is a person’s internal, partial representation of how a system works and what actions will produce.
principle
Natural Mapping
A mapping feels natural when the arrangement or movement of controls corresponds clearly to the arrangement or behavior of their effects.
model
Information Scent
Information scent is the perceived value of a cue for predicting whether a path will lead toward the information a person seeks.