> 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/managers-and-leaders/start-here/what-are-the-drivers-of-engagement.md). # What Are the Drivers of Engagement? {% embed url="" %} TalentMap’s research proves that the dynamics that drive organizational engagement (i.e., employee connectedness to the organization) can be very different from those that drive team engagement (i.e., teams going above and beyond in their work). Although every organization is different and can have unique key drivers, there are a few drivers that are very common across most organizations, regardless of their size, region, sector or industry. How employees feel about their senior leadership and the organizational culture are almost invariably the two strongest drivers of organizational engagement. More specifically, inspiring and effective senior leadership and a caring, high-integrity, respectful, celebratory organizational culture that harnesses the intellectual capital of its employees are the two most important organizational dynamics that drive employee pride, optimism and morale. Regarding team engagement, the most common key drivers that will energize teams to go above and beyond are inclusion, inspiring and effective team leadership, performance management and the leveraging of employee insights and ideas. ### Sample Key Drivers ![](https://2153489382-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXPT9x2nGbXVrpeQoz4Oz%2Fuploads%2F2tz0RIJnE37PgMo532Qg%2Fmg-img-3.png?alt=media) --- # 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/managers-and-leaders/start-here/what-are-the-drivers-of-engagement.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.