> 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-1-prepare-for-action/executive-driven-survey-overview/strategic-alignment-session.md).

# Strategic Alignment Session

An online strategic assesment is given by one of TalentMap's highly experienced consultants to clients with the objectives of:

* Gaining a thorough understanding of the business context which led to the decision to conduct an employee survey 
* Bringing the Executive Team up to speed with exactly what is about to take place during the upcoming employee engagement survey. The session will cover the following topics:

1. **Facilitated discussion** - Business context leading to the decision to conduct an employee engagement survey:
   * Industry trends and pressures
   * Change management in the organization
   * Turnover and morale
   * What are the expectations for the engagement survey?
   * What specific issues need to be addressed?
2. **Presentation**
   * Employee engagement: what's real and what's myth?
   * Benefits of Employee Engagement
   * How do we measure employee engagement? (The questionnaire)
   * The TalentMap Seven Step Survey Process, and managers' roles at key points during the process
   * Survey Deployment
   * Best practices for maximizing response rates
   * Examples of reporting
   * FAQs

Book some time with your consultant using the link provided by your Project Manager to prepare for this session, as well as for the actual session itself.


---

# 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-1-prepare-for-action/executive-driven-survey-overview/strategic-alignment-session.md?ask=<question>&goal=<user_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.