> For the complete documentation index, see [llms.txt](https://wiki.beabee.io/community-journalismus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.beabee.io/community-journalismus/english/community-centred-methods/feedback-surveys/general-tips-for-your-feedback-survey.md).

# General Tips for Your Feedback Survey

## Length

Keep surveys short. The longer they take, the more participants drop out.

Five minutes or 5 to 10 questions are ideal. Let participants know right at the start how long it will take to complete the survey, and stick to this promise.

## Mix question types

Mix open and closed questions. Closed questions, such as yes/no, scales, or multiple choice, are quick to answer and easy to evaluate. They provide precise answers to specific questions. However, to really understand what your community thinks, open questions are crucial. They offer deeper insights into the minds of participants and help you better understand their wishes and preferences.

However, open-ended questions are more difficult to evaluate because they require interpretation. Not everyone can clearly articulate their opinion, and they take longer to complete. As a result, participants tend to drop out when there are too many open-ended questions. Consider which questions should be mandatory. We recommend making a maximum of one or two open text fields mandatory.

Combine quantitative and qualitative elements by offering an optional text field on a scale to explain the selection.

## Sensible procedure

Structure your survey logically. Group questions with similar themes together and avoid jumping between topics. Start with simple closed questions before moving on to open text answers.

## Address

Adapt the tone of your survey to that of your publication. If you use formal language with your users, do the same in the survey. Explain the benefits of participating: 'Help us shape our offering!' This will motivate many of your valued users.

## Transparency

Be transparent about how you will handle the feedback. Explain how long the survey will run and when you will share the results. After evaluating the survey, share your conclusions and any changes you plan to make. If the survey does not go as hoped, be honest. Avoid making participants feel exploited or that their feedback is worthless.

***

<p align="center"><strong>Get involved:</strong></p>

<p align="center"><a href="https://starthub.correctiv.org/crowdnewsroom/your-question-for-our-wiki" class="button secondary" data-icon="message">Ask a question</a> or  <a href="https://starthub.correctiv.org/crowdnewsroom/your-contribution-to-our-wiki" class="button secondary" data-icon="pencil">Make a contribution</a> or  <a href="https://starthub.correctiv.org/crowdnewsroom/your-feedback-for-our-community-journalism-wiki" class="button secondary" data-icon="comments">Give feedback</a></p>


---

# 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://wiki.beabee.io/community-journalismus/english/community-centred-methods/feedback-surveys/general-tips-for-your-feedback-survey.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.