> 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/what-is-key-driver-analysis.md). # What is key driver analysis? Key Driver Analysis uses a statistical technique known as [Pearson correlation](/knowledge-base/step-5-analyze-interpret-and-report/compass-reports/reporting-faq/what-is-pearson-correlation.md) to identify patterns in the responses of employees. By using Pearson correlation, it is possible to identify which questions have the strongest and most meaningful association with your employee engagement score.
When you prioritize your intervention efforts based on the results of statistical analysis, the results are far superior to simply basing intervention efforts on the lowest scoring items in a survey. Typically the lowest scoring items (like compensation) have a very weak connection with employee engagement, and thus even large investments to improve these low scoring items do not result in large improvements in engagement. ### How does TalentMap determine key drivers for my organization? TalentMap has a scientific method for identifying key drivers of engagement for your specific organization. Our methodology takes into consideration the size of your organization, Pearson correlation, comparison data and overall performance 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/what-is-key-driver-analysis.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.