> 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/ideation/mood-boards.md).

# Mood Boards

Moodboards are a visual tool used early in the design process to establish the aesthetic direction of a project. Instead of focusing on specific layouts or functional details, a moodboard gathers a collection of images, colours, textures, and fonts to convey a particular feeling or atmosphere. This helps the design team and stakeholders align on a visual style before any actual building begins.

Using a moodboard is an effective way to bridge the gap between abstract ideas and concrete design. It allows everyone involved to see how different elements work together, making it easier to identify what resonates with the target audience. By testing these visual concepts early on, you can avoid costly changes later in the process and ensure that the final product has a consistent and intentional look.

Beyond just looking nice, moodboards serve as a point of reference throughout the lifecycle of a project. They act as a visual North Star, keeping the team focused on the agreed-upon aesthetic. Whether you are creating a new brand identity or refreshing a mobile app, this method ensures that the creative vision remains clear and that all contributors are working toward the same visual goal.

#### Further Reading

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

{% embed url="<https://www.interaction-design.org/literature/topics/mood-boards?srsltid=AfmBOoqVMoM-JCni_F1E2LE56HYbFmPlG6blkKtW6yNqS3WzWafYXJTO>" %}

{% embed url="<https://www.uxdesigninstitute.com/blog/mood-boards-for-ui-designers/>" %}

{% embed url="<https://www.eleken.co/blog-posts/a-great-starting-point-how-to-make-a-moodboard-for-ux-ui-design>" %}

{% embed url="<https://uxplanet.org/a-comprehensive-guide-to-creating-mood-boards-for-brand-identity-and-ux-design-projects-3243790ca5f9>" %}

#### Further Viewing

{% embed url="<https://www.youtube.com/watch?v=1A-tepzfhJw>" %}


---

# 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/ideation/mood-boards.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.
