> For the complete documentation index, see [llms.txt](https://docs.talentmap.com/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talentmap.com/knowledge-base/step-2-develop-questionnaire/questionnaire-design/determining-areas-of-importance.md). # Determining Areas of Importance We have developed a way to determine key drivers of engagement for not only large companies but also medium and small organizations, therefore reducing the need for the important questions. Asking your employees to describe the level of importance they feel toward each issue is more complicated than it appears. Measuring levels of importance can be done, but you need to take a statistical approach. Rather than asking your employees to rate the importance of each issue, you should group related issues and solicit feedback regarding their overall satisfaction (or lack thereof). Then, you can use data analysis software to draw conclusions about levels of importance based upon high and low correlations between the individual issues and overall engagement. --- # 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://docs.talentmap.com/knowledge-base/step-2-develop-questionnaire/questionnaire-design/determining-areas-of-importance.md?ask=&goal= ``` `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.