cognitive psychology
Conceptual model
What is a conceptual model in design?
A conceptual model is the story a design tells about how it works - the model of the system that its appearance, labels and behaviour project to the user. People build their own mental model from that "system image", so when the design communicates a clear, accurate model, people use it correctly; when it implies the wrong one, they form mistaken beliefs and misuse it with total confidence.
Also known as: conceptual model, system image, design model
Prefer to watch?
Watch the recap 0:51
The demo
A heating control. The same machine, presented two ways - and the way it's presented decides what people believe it does, and how they (mis)use it. Flip between them.
What this demo shows (text version)
A heating control is shown two ways. As a bare dial marked low-to-high, it projects the wrong "valve" conceptual model - it looks like a throttle, so people believe cranking it to maximum heats the room faster, then overshoot and fiddle. As a display showing the target temperature and the current temperature (and "heating…" while they differ), it projects the correct model: you set a goal and the system works toward it at one rate. People then use it correctly.
The machine is identical; only the system image - what the design presents - changed, and with it the mental model people infer. That's the lesson: you communicate how something works only through its appearance and behaviour, so design the conceptual model deliberately, lean on familiar metaphors, and make the state visible, or people will invent a wrong model and misuse the thing with confidence.
You don't get to put your mental model in the user's head directly - you communicate it through the design's appearance and behaviour (the "system image"), and they build their own model from that. So a confusing or misleading design produces a wrong mental model, and predictable misuse. Make the conceptual model the design projects simple, accurate and visible, so the model people infer matches how the thing actually works.
The bare dial invited the classic wrong model - "crank it to max and it'll heat faster" - so people misuse it and then blame themselves. Show the target and the current temperature, and the design quietly teaches the right model: it's a goal, not a throttle. Same machine; the difference is the story the interface tells about how it works.
Norman's chain is: the designer has a model, the user has a model, and the only thing connecting them is the system image - what the design actually presents. The designer can't transmit their intentions directly; everything the user understands, they infer from the interface. So if the system image projects a confusing or misleading model, the user's mental model will be wrong, no matter how clear it was in the designer's head.
The classic example is the thermostat. Many people hold a "valve" conceptual model - turn it all the way up and the room heats faster - because a bare dial implies it. In reality a thermostat sets a target temperature and heats at one rate, so the valve model causes overshooting and fiddling. A display that shows target-versus-current temperature projects the correct model and the misuse largely disappears.
So design the model deliberately and make it perceivable: use familiar metaphors and conventions (a strong conceptual model people already hold), match controls to how the system really behaves, and surface state so the model is visible rather than guessed. A good conceptual model is the difference between an interface people understand and one they superstitiously poke at.