Interaction Quality

Mental Model

A user’s internal understanding of how a system, service, task, or concept works.

Concept facts

A mental model is a person’s internal representation of how something works, what actions are possible, and what outcomes to expect.

Also known as
User understanding, internal model, conceptual understanding, system expectation
Used in
Interface design, usability testing, onboarding, navigation design, content design, service evaluation, product education
Interpret with
User expectations, prior experience, task success, cognitive load, feedback, terminology, learnability, and conceptual model alignment

Plain-language explanation

A mental model is how a person thinks a system or service works. It may be accurate, incomplete, or partly wrong, but it guides what the person expects to happen.

In UX work, mental models matter because users do not interact only with what designers intended. They interact through their own assumptions, prior experience, language, and expectations. A person may misunderstand where to click, what a label means, what a confirmation message implies, or what step comes next because their mental model does not match the system’s structure.

Designers and organizations create conceptual models through structure, labels, feedback, examples, and interaction patterns. A strong interface helps users form a useful mental model without needing to understand internal technical or organizational logic.

Why it matters

A mismatch between the user’s mental model and the system model can create confusion, errors, repeated checking, low confidence, or abandonment. Users may choose the wrong path not because they are careless, but because the system’s labels or structure suggest the wrong meaning.

Mental models are especially important in services where users must understand eligibility, payment, status, confirmation, application stages, or role-based access.

Mental model analysis helps teams identify whether a problem is caused by interface layout, terminology, feedback, information structure, or deeper service logic.

Use contexts

  • Usability testing
  • Navigation and information architecture review
  • Onboarding and learning flows
  • Service journey evaluation
  • Content clarity review
  • Dashboard and workflow design
  • Error and confidence analysis

Application guidance

Evaluate mental models by examining what users expect, where expectations break, and how they explain the system in their own words. Look for mismatches between user language and system labels, between expected and actual outcomes, and between visible structure and hidden rules.

Do not ask only whether users “understand” the system. Ask users to explain what they think will happen next, why they chose an option, or what a message means.

Use the findings to improve labels, grouping, feedback, onboarding, examples, and confirmation states.

Practical example

A mobile financial service user assumes that a failed transaction means no money was deducted. The system, however, places the transaction in a pending state while network confirmation is delayed.

The user’s mental model does not match the transaction model. Clearer status language, pending-state explanation, and recovery guidance can reduce duplicate attempts and support calls.

Interpretive boundaries

  • A mental model is not always accurate or complete.
  • Mental models change through interaction and feedback.
  • A user’s mental model should not be treated as a fixed profile or persona.
  • Mental model findings require interpretation and should be linked to task evidence.
  • Designers cannot directly see mental models; they infer them from behavior, explanation, errors, and expectations.

Applied at Userhub

Mental model analysis is relevant when Userhub evaluates whether people understand how a digital service, application flow, course journey, dashboard, or institutional platform works.

See Userhub UX Lab for applied UX research and evaluation context.

Sources and references

  • Johnson-Laird, P. N. (1983). Mental Models: Towards a Cognitive Science of Language, Inference, and Consciousness. Harvard University Press.
  • Norman, D. A. (1983). Some observations on mental models. In D. Gentner & A. L. Stevens (Eds.), Mental Models (pp. 7–14). Lawrence Erlbaum Associates.
  • Staggers, N., & Norcio, A. F. (1993). Mental models: Concepts for human-computer interaction research. International Journal of Man-Machine Studies, 38(4), 587–605. https://doi.org/10.1006/imms.1993.1028
  • Norman, D. A. (2013). The Design of Everyday Things (Revised and expanded ed.). Basic Books.

—

Cite this entry

APA

Userhub. (2026). Mental Model. UX Reference. https://userhub.com.bd/reference/mental-model/