Conceptual Models and the System Image

Definition

A conceptual model is a simplified explanation — held in a person's head — of how something works; it need not be accurate, only useful. People cannot talk to the designer, so they build this model entirely from the "system image": everything they can perceive of the product (its controls, labels, documentation, prior experience with similar things). Norman diagrams this as a triangle — the designer's model, the product itself, and the user's model — connected only through the system image, so "the entire burden of communication is on the system image."

In the Book

The case study is Norman's own two-compartment refrigerator (Chapter 1, Figures 1.9–1.10): two controls, one labeled "freezer" and one "refrigerator," which strongly implies each independently sets the temperature of its named compartment. In fact there is one thermostat and one cooling unit — one control sets the thermostat, the other adjusts how much cold air is diverted to each compartment — so the two controls interact, the manual requires waiting 24 hours to see the effect of any change, and Norman reports it was "almost impossible" to set correctly even though he says he knew the correct model, because the product itself gave no way to discover which control did what. He contrasts this with a pair of scissors, whose operating parts are visible enough that the correct conceptual model is obvious without instruction. The chapter also traces conceptual models onto digital objects — files, folders, and "the cloud" are all conceptualizations that don't correspond to anything physically real, but make systems usable as long as their simplifying assumptions hold.

Why It Matters

This reframes usability failures as communication failures: a device isn't "hard to use" in the abstract, it fails to transmit an accurate model of its own operation through everything the user can perceive of it before and during use. It gives a diagnostic move that generalizes past physical products — whenever people are performing rote steps without being able to adapt when something breaks, that's usually the signature of a missing or wrong model, not a lack of information. Any system a person must operate indirectly (through an interface, through documentation, through someone else's account of it) faces the same triangle: what the builder intended, what was actually built, and the fragile channel — the "system image" — carrying one to the other.