> 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/your-managed-survey/step-6-discuss-clarify-and-plan/talentmap-survey-results-presentations/talentmap-report-faq/high-satisfaction-vs-low-engagement-or-vis-versa.md). # High satisfaction vs low engagement (or vis versa)? It is not unlikely to see a low satisfaction score and a higher engagement score (or vis versa) in survey results as these are two very different concepts. Engaged employees are deeply invested in their work and tend to go the extra mile to help the organization reach its broader goals. They also have a sense of connection and commitment to their organization. A satisfied employee simply enjoys their job. Satisfied employees may be happy with their work-life balance, compensation and their job security, but don’t feel the need to put in extra work and don't have a deep connection to their employer. Satisfaction is generally enough to retain employees, however it does not ensure that these employees are highly productive. --- # 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/your-managed-survey/step-6-discuss-clarify-and-plan/talentmap-survey-results-presentations/talentmap-report-faq/high-satisfaction-vs-low-engagement-or-vis-versa.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.