What is the system image and why does it matter?

The system image is everything the product communicates to the user, the interface, behaviour, documentation, and labels. It matters because designers cannot speak to users directly; users build their mental model only from the system image, so a confusing image leads to a confused mental model.

Are interface metaphors always helpful?

Metaphors such as the desktop or trash can help users transfer familiar knowledge to a new system, which speeds learning. But they can mislead when the system's behaviour departs from the metaphor, so designers must use metaphors that match actual behaviour and avoid relying on them past their breaking point.

Conceptual Models and Mental Models

A conceptual model is the intended design of how a system works, communicated through its interface, while a mental model is the internal representation a user builds through experience; aligning the two is central to usable design.

Definition

A conceptual model is the way a designer intends a system to be understood, expressed through the system image, the visible interface and documentation; a mental model is the user's own evolving understanding of how the system works, used to predict its behaviour and plan actions.

Scope

This topic covers how users form internal models of interactive systems and how designers shape those models. It addresses the designer's conceptual model, the system image presented by the interface, and the user's mental model, along with how incomplete or inaccurate mental models produce errors and how metaphors and consistency support model formation. It does not cover the broader study of human cognition and memory, which belongs to the cognitive foundations of HCI within usability and evaluation.

Core questions

How do designers communicate a conceptual model through the system image?
How do users construct mental models from experience, instructions, and metaphor?
Why do inaccurate or incomplete mental models lead to errors?
How can interface metaphors help and sometimes mislead users?

Key concepts

conceptual model
mental model
system image
interface metaphor
model mismatch and error
predictive simulation
consistency
knowledge in the head vs in the world

Key theories

Designer model, system image, user model: Norman distinguished the designer's conceptual model, the system image that the product actually presents, and the user's mental model; because designers communicate only through the system image, a clear and consistent image is what lets users build accurate mental models.
Mental models as runnable representations: In cognitive science, mental models are internal representations that people run to simulate and predict how a system or situation will behave, which is why a good mental model lets users anticipate the effects of their actions.
Mental models in HCI: Users' mental models of computer systems are often partial, unstable, and superstitious yet still functional; design can support better models through visible structure, consistency, and apt metaphors.

Clinical relevance

When a system's conceptual model is clear, users can predict its behaviour, recover from errors, and transfer skills across products; mismatches between user mental models and system behaviour are a frequent cause of operator error in complex and safety-critical systems.

History

The notion of mental models entered cognitive science in the early 1980s through Gentner and Stevens's edited volume and Johnson-Laird's account of reasoning. Norman applied the framework to design, formalizing the designer model, system image, and user model and arguing that interfaces communicate the conceptual model only through what users can perceive and do.

Key figures

Donald A. Norman
Dedre Gentner
Philip N. Johnson-Laird
John M. Carroll

Seminal works

norman2013
gentner1983
johnsonlaird1983

Frequently asked questions

What is the system image and why does it matter?: The system image is everything the product communicates to the user, the interface, behaviour, documentation, and labels. It matters because designers cannot speak to users directly; users build their mental model only from the system image, so a confusing image leads to a confused mental model.
Are interface metaphors always helpful?: Metaphors such as the desktop or trash can help users transfer familiar knowledge to a new system, which speeds learning. But they can mislead when the system's behaviour departs from the metaphor, so designers must use metaphors that match actual behaviour and avoid relying on them past their breaking point.