Skip to content
Tutorials Center
My learning

Topics

Lesson 6 of 36 ยท UX Fundamentals

Mental Models and Conceptual Models

Learn how users form mental models, how designers' conceptual models differ, and how affordances, signifiers, feedback and mapping help the two match.

Why do people try to pull a door that says PUSH? Why does a thermostat confuse some people but a light switch does not? The answer is mental models: the pictures people carry in their heads about how something works. When a design matches the user's mental model, it feels obvious. When it does not, people blame themselves, though the design is at fault.

Three models

Donald Norman, whose book The Design of Everyday Things shaped the field, distinguishes three models.

  • The user's mental model: what the person believes about how the thing works.
  • The designer's conceptual model: how the designer thinks it works, and what the product is built on.
  • The system image: what the product actually shows and does, through its interface and behavior.

The designer cannot talk to each user. All communication goes through the system image. If the interface reveals the designer's model clearly, users build a matching mental model. If it does not, they invent their own, often wrongly.

flowchart LR
  A["Designer's conceptual model"] --> B["System image<br/>(the interface)"]
  B --> C["User's mental model"]

The user never sees the designer's intent, only the interface.

Examples

Many people believe pressing an elevator button repeatedly makes it come faster. The real system usually registers the first press. This false mental model is harmless in the lift but risky in other places. Another example is the "Save" icon: many younger users have never held a floppy disk, yet the symbol survives because of convention. The mental model has been learned from other software, not from the physical object.

A useful design habit is to borrow existing models. A shopping cart, a folder, a trash can, a tab: these metaphors let people transfer knowledge. But a metaphor can mislead when pushed too far. A digital "folder" can contain a file in several places, unlike paper.

Affordances and signifiers

An affordance is a relationship between an object and a person: what actions are possible. A chair affords sitting. A flat plate on a door affords pushing; a handle affords pulling.

A signifier is the signal that tells you where the action is possible. In screens, real affordances are often invisible, so signifiers carry the load: a button that looks raised, an underlined link, a slider handle, a text cursor in a field. When people do not know what is clickable, the cause is usually a missing or weak signifier.

Feedback and mapping

  • Feedback: immediately show the result of an action. A pressed button changes shade; a message appears after sending.
  • Mapping: the relationship between controls and their effects. A stove with four burners and four knobs in a matching square layout has natural mapping; four knobs in a line do not. On screens, put a control near the thing it changes, and keep the order of switches in the same order as the items.
  • Constraints: limit the wrong actions. A date picker that blocks past dates in a booking form prevents errors.

Help users guess right

Signifier Show what can be done
Feedback Show what just happened
1 / 2

A stand-in: comparing models

This stand-in compares a user's expectations with what a product does. It is a teaching toy: it lists beliefs and checks them against actual behavior, and the mismatch list is where a designer should add signifiers or feedback.

JS Mental model mismatch checker (stand-in)

Press Run (or Ctrl + Enter) to see the console output here.

No output.

In practice you find user beliefs by asking people to explain how they think something works and by watching their first guesses in a test.

Designing for the user's model

  • Ask and observe before designing. Interviews reveal how people describe their task in their own words (see User Interviews).
  • Use the user's vocabulary in labels and menus.
  • Keep behavior consistent so one learned rule applies everywhere.
  • Show system state so people can correct a wrong guess quickly.
  • Test first-click behavior: where people click first shows their model.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is a mental model?

    Mental models live in users' heads and guide their expectations.
  2. 2. What is the system image?

    It is the only channel by which the designer's model reaches users.
  3. 3. A flat button with no border looks like plain text and users do not click it. Which concept is weak?

    The signal showing the action is possible is missing.
  4. 4. Which is good mapping?

    Matching the layout of controls and effects lets people predict results.

Summary

  • Users bring mental models; designers have conceptual models; the interface is the system image that connects them.
  • Affordances are possible actions; signifiers show where they are.
  • Feedback, mapping and constraints help people guess right and recover.
  • Learn users' models through interviews and observation, and borrow familiar metaphors carefully.

Next: Cognitive Load and Hick's Law