> For the complete documentation index, see [llms.txt](https://10x-impact-labs.gitbook.io/measuring-satisfaction/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-satisfaction/the-data/5.-analyzing-data.md).

# 5. Analyzing Data

* **Data Visualization Techniques -** Use charts, graphs, and other visualizations to present data in a clear and easily understandable format. Visualizations can highlight trends and patterns at a glance.
* **Identifying Trends and Patterns -** Look for recurring themes and patterns in your data. Identify areas of high and low satisfaction and explore correlations between different variables.
* **Utilizing Statistical Analysis -** If applicable, employ statistical analysis techniques to derive deeper insights from quantitative data. Consider consulting with a statistician to ensure the accuracy of your analyses.
* **Interpreting Qualitative Feedback -** For qualitative data, develop a systematic approach to analyze open-ended responses. Categorize feedback into themes and use quotes to illustrate key points.


---

# 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-satisfaction/the-data/5.-analyzing-data.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.