Mental Models

Customers interact with digital products and services daily. Intuitive operation should be a given—or so the expectation goes. Yet companies still experience support requests, abandonments, and user frustration—even when their systems are built "logically." The question is: Why do users struggle with seemingly simple interfaces, what invisible expectations shape understanding—and what does the evidence tell us?

Studies

The Thermostat Misunderstanding

Donald Norman documented a classic mental model problem in everyday life in 1983. He observed how people operated their heating thermostats. Most turned the thermostat to maximum to heat a room quickly—then back down later. This revealed a false mental model: They believed the thermostat worked like a gas pedal (higher setting = faster heating). In reality, it works like a switch (setting = target temperature, heating speed constant). The striking part: Although nearly everyone owns a thermostat, the majority had a fundamentally incorrect understanding—leading to inefficient energy consumption. Norman showed that people don't change their behavior when their mental model is wrong. They adapt their behavior to their model, not to reality.

The Text Editor Experiment

David Kieras and Peter Polson conducted a revealing experiment at the University of Arizona in 1985. Forty students learned a new text editor—half using a system-consistent interface, the other half using an interface aligned with their existing mental models. The system-consistent interface employed technically logical commands (DELETE sends characters to a buffer, RESTORE retrieves them). The model-consistent interface used familiar metaphors (CUT and PASTE, like scissors and glue). After one hour of training, the first group made 47% more errors. One day later, they made 73% more errors. The most striking finding: the system-consistent group needed an average of 14 repetitions to execute a task without errors, while the model-consistent group needed only 4 repetitions. Technical consistency alone does not guarantee usability—alignment with users' mental models is more critical.

Principle

Which principle for Customer Experience Design can be derived from this? The central principle is: Design systems according to users' mental models, not technical logic. Since people understand new interfaces through analogies to familiar systems, designers must know and respect their target audience's existing expectations. This becomes particularly critical with innovative products or complex functions, where the temptation to prioritize technical efficiency over user understanding is greatest. Successful customer experience only emerges when system design aligns with users' mental models—otherwise, even small deviations lead to confusion and abandonment. The following guidelines show how to implement this principle in practice.

Guidelines

Metaphors from the User's World

Use terms, symbols, and interaction patterns from your users' real world, not from the technical implementation. A bank customer understands "transfer money" better than "initiate transaction." A doctor understands "open patient record" better than "load data set." Identify the dominant metaphors in your target domain and map them consistently throughout the interface.

Test expectations before the design

Test mental models before you design, not after. Ask users: "If you wanted to do X, where would you click? What would you expect to happen next?" Classic usability tests only reveal where your design fails. Mental model interviews reveal why it fails. The method: Show mockups without explanation, let users think aloud, and identify expectation gaps between the user's model and the system model.

Consistency with user expectation

When technical consistency conflicts with user expectations, prioritize the expectations. For example, "Save" means permanent storage in some systems but temporary caching in others. The technical distinction is irrelevant—what matters is the expectation within that specific context. A cloud document doesn't require manual saving (it auto-saves), while a local document does. Same underlying function, different mental models, different design solutions.

Feedback for Model Correction

When users hold an incorrect mental model, correct it through immediate feedback rather than explanations. Show them the direct consequences of their actions. For example, users often believe that more search terms yield better results. Instead of creating a help page about Boolean logic, display real-time feedback as they type: "Your search with 5 terms has 2 results. With 3 terms: 47 results." This approach allows users to learn through experience rather than documentation.