> 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/cognitive-tools/ux-laws-principles/behaviour/three-pillars-of-user-delight.md).
# Three Pillars of User Delight
A model for designing products that appeal to users' instincts (visceral), feel effective (behavioural), and create positive memories (reflective).
The Three Pillars of User Delight are a set of principles that help designers create products that users will love. These pillars are Visceral Delight, Behavioural Delight, and Reflective Delight.
* **Visceral Delight** is the feeling of joy that comes from experiencing something beautiful or well-crafted. It is the first impression that a user has when they see or touch a product. For example, a user might be delighted by the look and feel of a new smartphone.
* **Behavioural Delight** is the pleasure that comes from using a product that works well. It is the satisfaction that a user feels when they can easily accomplish their goals with minimal effort. For example, a user might be delighted by how quickly and smoothly they can navigate through an app.
* **Reflective Delight** is the feeling of happiness or satisfaction that comes after using a product. It is the sense of accomplishment or pride that a user feels when they have achieved their goals. For example, a user might be delighted by how much they have learned or accomplished after using an educational app.
#### Further Reading
{% embed url="" %}
{% embed url="" %}
---
# 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/cognitive-tools/ux-laws-principles/behaviour/three-pillars-of-user-delight.md?ask=&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.