# How to sort through feedback You will likely get a lot of feedback after talking with users. Some of it may even not be relevant to the issue you are looking to solve. Deciding what to do from the feedback can take some work. Write down all feedback, even feedback that is out of scope. You may decide to come back later in the future to something and having this initial feedback will be helpful. Weigh carefully how important a design change or element is to the user. Even if the change will be difficult to implement, it may be worth it. Conversely, something that is not very important to users but is easy to implement may also be worth doing. Weigh feedback in the context of the goals of your application. For instance, typically you want a user to go through an application as quickly as possible since time is valuable. However, it may be good to slow a user down in some cases, such as if you need them to think about the implications of an analysis before running it. --- # 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://ucsc-xena.gitbook.io/ux-resource-for-ucsc-genomics-institute/getting-feedback/how-to-sort-through-feedback.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.