# Surveys 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="" %} #### 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: 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: ``` GET https://help.swarmia.com/features/run-developer-experience-surveys.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.