A user's internal representation of how something works, built from prior experience and observation. When an interface matches users' mental models, it feels intuitive; when it conflicts with them, confusion and errors follow.
Common contexts
- Running card sorting to understand how users group concepts before designing a navigation structure
- Analyzing support tickets to find recurring misunderstandings that reveal a mismatch between UI logic and user expectations
- Shadowing users in a contextual inquiry session to observe the workarounds they invent when the system doesn't behave as expected
Use when
Investigate mental models before designing a novel or complex interaction — understanding what users already believe about how something works tells you which conventions to preserve and which assumptions to challenge.
Avoid when
Don't assume that the mental model of early adopters represents all users — power users build accurate models quickly, and designing for them can leave mainstream users permanently behind.
You can't change a user's mental model with a tooltip — if your interface systematically conflicts with how users think, the fix is architectural, not instructional.
Real-world examples
- Venmo's social activity feed violated users' mental models of payment apps as private services; the resulting privacy scandals — when users discovered transactions were public by default — caused significant churn and regulatory attention.
- Skeuomorphic iOS icons (leather-bound calendar, yellow legal-pad notepad) deliberately mapped to physical objects to leverage users' existing mental models during the smartphone transition period.
- Apple's Mac Trash icon teaches users a mental model of temporary deletion: items stay visible in the Trash and are only permanently deleted on 'empty', reducing accidental permanent deletions versus Linux's rm.