> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/ux-methods/discovery/user-mental-models.md).

# User Mental Models

User mental models refer to the cognitive frameworks or structures that individuals use to understand and interpret the world around them.&#x20;

These models are personal constructs that shape how people perceive, reason, and make decisions. Mental models are built through experiences, knowledge, beliefs, and cultural influences. They act as filters through which individuals interpret and navigate their environment. Understanding mental models is crucial in design and user experience as it allows designers to align their products or services with users' existing mental frameworks.&#x20;

By considering users' mental models, designers can create intuitive interfaces, anticipate user expectations, and provide seamless experiences. Incorporating mental models in design helps bridge the gap between the system's functionality and users' mental representation, resulting in products that are easier to understand, learn, and use.

#### Further Reading

{% embed url="<https://www.nngroup.com/articles/mental-models/>" %}

{% embed url="<https://uxplanet.org/user-mental-models-in-product-design-a902b6dab59d>" %}

#### Further Viewing

{% embed url="<https://www.youtube.com/watch?v=nAgXISssAws>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.designreference.xyz/ux-methods/discovery/user-mental-models.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
