> 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-5-analyze-interpret-and-report/compass-reports/reporting-faq/should-we-focus-on-dimensions-with-low-scores.md). # Should we focus on dimensions with low scores? **Not necessarily.** It is important to remain focused on what drives engagement rather than low scores. Engagement is what motivates your employees to be their best. It could be, for instance, that your organization scores low on one area, such as Work/Life Balance. However, if that area does not have a strong statistical relationship to Engagement, an investment of time and resources to improve that area will not have a large impact on Engagement. It is human nature to want to invest in the areas that score the lowest; however, if the focus is on improving engagement, the focus should remain on those areas that affect engagement the most. Investing in areas where the scores are low but have shown statistically do not have a strong relationship with engagement, will likely result in improved scores in that area and perhaps some internal complaining will subside, but little or no improvement in the organization's overall engagement scores. --- # 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://docs.talentmap.com/knowledge-base/step-5-analyze-interpret-and-report/compass-reports/reporting-faq/should-we-focus-on-dimensions-with-low-scores.md?ask=&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.