> 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/what-size-group-is-required-to-do-driver-analysis.md).

# What size group is required to do driver analysis?

To measure engagement drivers using multiple regression analysis, there need to be approximately 30 individuals for every dimension measured. In a typical TalentMap survey, we measure 12 dimensions of engagement.

Accurately measuring all of the drivers requires 360 respondents. That said, for smaller sample sizes, a driver analysis could be done using a linear regression model instead of a multiple regression models, but it would not be an apples to apples analysis, and it would be inconsistent with how the drivers are measured for the company as a whole.

TalentMap uses linear regression analysis for smaller organizations and we find that a minimum sample size of approximately 30 people is needed to effectively do a driver analysis. However, multiple regression analysis is the preferred method when possible as it takes into consideration all the variables in the relationship and not just one variable at a time, painting a more accurate picture.


---

# 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/what-size-group-is-required-to-do-driver-analysis.md?ask=<question>&goal=<endgoal>
```

`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.