> 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/card-sorting.md).

# Card Sorting

Card sorting is a research technique used to understand how users organise and categorise information. 

It involves participants sorting a set of cards or items into groups based on their perceived similarities or relationships. Participants may also provide labels or names for the groups they create. 

Card sorting helps designers and researchers gain insights into user mental models, information hierarchy, and navigation preferences. It aids in information architecture design, content organisation, and menu structure. 

By conducting card sorting sessions, organisations can uncover patterns in how users perceive and group information, informing the design of intuitive and user-friendly interfaces. 

Card sorting can be conducted through physical cards or online tools, and the results are analysed to inform the structure and layout of digital products, websites, or applications.

#### Further Reading

{% embed url="<https://medium.com/illumination/understanding-card-sorting-for-ux-2f33ef4e8e66>" %}

{% embed url="<https://www.interaction-design.org/literature/article/the-pros-and-cons-of-card-sorting-in-ux-research>" %}

#### Further Viewing

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

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

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

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


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.designreference.xyz/ux-methods/discovery/card-sorting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.