Mental model

What it is

The concept comes from cognitive psychology (Kenneth Craik in the 1940s, Philip Johnson-Laird in the 1980s) and was brought into UX by Jakob Nielsen and Don Norman. Norman distinguished the designer's model (how the designer thinks the system works), the system image (what the interface actually shows), and the user's mental model (what the user infers from the system image). Design succeeds when all three align.

Mental models are inherited. A user picking up a new file manager expects folders to nest, files to have names and extensions, and drag-and-drop to move things — because those conventions are learned from decades of prior interfaces. Fight the inherited model and the user has to learn a new one before they can act.

Why it matters

Interfaces that match the user's mental model feel intuitive; interfaces that don't feel broken even when they work correctly. The 'intuitive' experience isn't a mysterious property — it's model alignment. When users say a product is 'confusing', they're describing a mental-model mismatch: what they expected the system to do isn't what it did.

When to use it

Every design decision that involves user expectations — which is every design decision. Especially critical when introducing a new metaphor (e.g. how does 'workspaces' or 'boards' work?), when translating a domain concept (e.g. what does 'archive' mean in this product?), and when redesigning an existing product where users have already built a mental model of it.

What it looks like in practice

Interviews probing 'what did you expect to happen?' reveal mental models faster than any other research question. Session recordings of confused users show mental-model mismatch as hesitation, backtracking, or wrong-action retries.

A user who tries to click a card because it looks like a link has a mental model saying 'card-like things are links'. If the card wasn't intended to be a link, the designer has two choices: change the visual so it doesn't read as clickable, or make it clickable. Fighting the model — 'users should just learn' — reliably loses.

The archive-vs-delete distinction is a classic mental-model problem. Gmail's 'archive' broke the mental model of 'file it or bin it' and had to be explained through years of onboarding before it settled.

What people get wrong

• Assuming the team's mental model represents the user's. The team has context — code paths, roadmap, organisational history — the user doesn't.
• Introducing new metaphors when familiar ones would do. Novel metaphors have to be learned; every learning tax is a churn risk.
• Ignoring mental-model mismatch in analytics. Users who backtrack, retry, or abandon aren't 'confused users' — they're users encountering model mismatch. The mismatch is the signal.
• Assuming model mismatch is a training problem. If enough users share the same mismatch, it's the interface's problem to fix.

Learn next

Mental models sit at the centre of UX — they connect to affordance (what the user expects the element to do), to information architecture (what the user expects the structure to be), and to cognitive load (mismatched models raise extraneous load).

Reviewed 29 September 2026 · Editorial standards