> 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/ia-research-study.md).

# IA Research Study

An information architecture (IA) research study involves investigating and evaluating the organisation and structure of information within a system or website.&#x20;

It focuses on understanding how users navigate, find, and interact with information to achieve their goals. IA research studies employ methods such as user interviews, card sorting exercises, tree testing, and usability testing to gain insights into users' mental models, information needs, and preferences.&#x20;

By conducting IA research, businesses can identify opportunities to improve the organisation, labelling, and navigation of information, resulting in enhanced user experiences and improved findability of content. The findings from an IA research study inform the design and development of intuitive and user-friendly information structures that support efficient and effective information retrieval.

#### Further Reading

{% embed url="<https://www.nngroup.com/articles/ia-study-guide/>" %}

#### Further Viewing

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


---

# 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/ia-research-study.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.
