Mental Model
A mental model is a person's internal picture of how a system works; interfaces feel intuitive when they match it and confusing when they don't.
Key takeaways
- Learn how users already think about the task before designing the flow.
- Use familiar metaphors and terms from the user's world, not your org chart.
- When the system must work differently, make the difference explicit.
Origin
Psychologist Kenneth Craik proposed in 1943 that the mind builds 'small-scale models' of reality to predict events. Don Norman applied the idea to design in the 1980s, contrasting the designer's model, the system image and the user's model in The Design of Everyday Things (1988).
How to apply it
- Research how users currently think about the task through interviews, card sorting and observation.
- Use terms and structures users already know rather than internal jargon.
- Show the consequences of actions clearly before and after they happen.
- Use onboarding and empty states to build the right mental model for new concepts.
- Test with real users to find where their expectations and the system diverge.
How Science of Apps uses this law
15 checks in every investigation rely on Mental Model, for example: “Do option screens require a deliberate confirm rather than auto-advancing on tap?”
Get your product investigated