> 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/1.-planning-and-preparation.md).

# 1. Planning and Preparation

* **Setting Clear Objectives -** Clearly define the goals of your satisfaction measurement initiative. Are you aiming to improve a specific aspect of your project, or are you conducting a general assessment?
* **Identifying Stakeholders -** Identify key stakeholders who will be affected by or can contribute to the satisfaction measurement process. This includes users, team members, and community leaders.
* **Choosing Appropriate Tools and Platforms -** Select tools and platforms that align with your objectives. Consider survey tools, analytics platforms, and communication channels that best suit your audience.
* **Legal and Ethical Considerations -** Ensure that your satisfaction measurement practices adhere to legal and ethical standards. Clearly communicate how user data will be used and protected.


---

# 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/1.-planning-and-preparation.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.