> For the complete documentation index, see [llms.txt](https://10x-impact-labs.gitbook.io/measuring-user-satisfaction-toolkit/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://10x-impact-labs.gitbook.io/measuring-user-satisfaction-toolkit/best-practices/top-tips/2.-designing-effective-surveys.md).

# 2. Designing Effective Surveys

* **Crafting Relevant Questions -** The success of your survey depends on the quality of your questions. Craft questions that are clear, concise, and aligned with your objectives.
* **Choosing the Right Survey Type -** Select the survey type that best suits your goals. For example, use Likert scales for nuanced feedback or Net Promoter Score for a quick assessment of overall satisfaction.
* **Survey Length and Timing -** Balance the depth of information you seek with the time investment required from participants. Consider the best timing for your surveys to capture real-time feedback. 
* **Pre-testing Surveys -** Before launching your survey, conduct pre-tests with a small group to identify potential issues with question clarity or survey flow.


---

# 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://10x-impact-labs.gitbook.io/measuring-user-satisfaction-toolkit/best-practices/top-tips/2.-designing-effective-surveys.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.