> 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/testing/surveys.md).

# Surveys

Surveys are research tools used to collect data and feedback from users regarding their opinions, preferences, and experiences with a product or service.

Surveys typically involve a series of structured questions that users respond to, providing quantitative or qualitative data. The questions can cover various aspects, such as user satisfaction, usability, feature preferences, or demographic information. User surveys are administered through online platforms, email, or in-person interactions.

They allow designers and researchers to gather insights directly from users, understand their needs and expectations, and identify areas for improvement.

Surveys can help validate hypotheses, measure user satisfaction, and inform design decisions. By analysing survey responses, organisations can gain valuable insights into user preferences and make data-driven decisions to enhance their product or service. User surveys provide a scalable and efficient means of gathering feedback, enabling organisations to make informed improvements and iterate on their offerings.

#### Further Reading

{% embed url="<https://www.nngroup.com/articles/survey-best-practices/>" %}

{% embed url="<https://www.nngroup.com/articles/10-survey-challenges/>" %}

{% embed url="<https://www.nngroup.com/articles/keep-online-surveys-short/>" %}

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

#### Further Viewing

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

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

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


---

# 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/testing/surveys.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.