> For the complete documentation index, see [llms.txt](https://help.swarmia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.swarmia.com/features/run-developer-experience-surveys.md).

# Surveys

See what truly affects developer experience and productivity by viewing relevant survey results alongside your system data.

When engineers voice their frustrations and suggest improvements, you start to understand what is behind the metrics and get concrete ideas on what to improve. For example, you might learn that long epic cycle times are caused by interruptions, unclear priorities, or missing technical validation.

{% embed url="<https://youtu.be/28YwYav3oY4>" %}

#### Read more on our blog

* [Minimizing noise and bias in developer surveys](https://www.swarmia.com/blog/minimizing-noise-and-bias-in-developer-surveys/)
* [35 questions to ask in your developer experience surveys](https://www.swarmia.com/blog/developer-survey-questions/)
* [Complementing engineering metrics with developer experience surveys](https://www.swarmia.com/blog/complementing-engineering-metrics-with-developer-experience-surveys/)
* [How to run developer survey retrospectives in your team](https://www.swarmia.com/blog/developer-survey-retrospectives/)


---

# 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://help.swarmia.com/features/run-developer-experience-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.