> For the complete documentation index, see [llms.txt](https://docs.talentmap.com/site-faq/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/site-faq/faq/general/shouldnt-we-focus-on-areas-with-low-scores.md). # Shouldn’t we focus on areas with low scores? Not necessarily. It is important to remain focused on what drives engagement. Engagement is what motivates your employees to be their best. It could be that one area of the organization, for example, Work/Life Balance, scores very low within the organization. If that area is not found to have a strong statistical relationship to Engagement, it would mean that any investment of time and resources to improve that area will not have an 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. Investing in areas where the scores are low, but have shown to statistically not have a strong relationship with engagement, would likely result in seeing an increase in those scores rise, and perhaps some internal complaining about that area would stop; however, you would not see the organization’s engagement scores improve. --- # 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/site-faq/faq/general/shouldnt-we-focus-on-areas-with-low-scores.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.