Mental Model
A person’s internal explanation of how a system works and what will happen when they act.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/mental-model/
01What it means
A mental model is the understanding a user builds from prior experience, current cues, and observed results. It may be incomplete or technically inaccurate yet still guide expectations and behavior.[1][2]
- User mental model
- Beliefs about objects, actions, rules, state, and likely outcomesFormed from prior products, language, feedback, and experience
- Designed conceptual model
- The explanation the product communicates through structure and behaviorShould make important relationships and consequences predictable
- Implementation model
- Internal technical structureNeed not be exposed when it adds complexity without helping the task
People hold partial, changing explanations shaped by experience and cues; the interface should support successful prediction without requiring implementation knowledge.
02Why it matters
Products feel intuitive when their behavior supports useful existing expectations or teaches a coherent new model. Misalignment leads to errors that appear irrational only from the system designer’s perspective.
03When to use it
Use mental models during discovery, information architecture, onboarding, interaction design, and investigation of repeated user errors.
04How it works
- Research how users describe goals, objects, relationships, and sequences in their own words.
- Separate the user’s model from the implementation and from the team’s preferred terminology.
- Design a consistent conceptual structure that supports productive expectations.
- Use signifiers, mapping, and feedback to teach the model through interaction.
- Test predictions: ask what users expect to happen before they act.
05A practical example
People may think of cloud files as documents inside folders even though the storage system works differently. A product can honor that useful model while making sharing state and ownership explicit.
06Where it breaks
There is rarely one user mental model. Expertise, culture, tools, and context produce different expectations. Research descriptions are approximations, not literal maps inside a person’s head.
Common mistakes
- Treating the database structure as the user’s natural model.
- Using internal jargon that users do not recognize.
- Trying to correct users through documentation instead of improving product behavior.
07Sources
- Mental ModelsNielsen Norman Group · professional guidanceMental Models
- The Design of Everyday Things, Revised and ExpandedBasic Books / Don Norman · bookThe Design of Everyday Things, Revised and Expanded