> 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/prepare-for-action-faq/who-will-be-responsible-for-different-aspects-of-the-project.md).

# Who will be responsible for different aspects of the project?

We believe in a collaborative approach with clear responsibilities. Here's a breakdown of who typically handles different aspects of the project:

1. **TalentMap Team**:
   * **Project Manager**:
     * The primary point of contact for any questions or concerns
     * Oversees the day-to-day logistics
     * Works closely with your team
     * Manages timelines, milestones, and project schedules
     * Handles email communications and coordination
     * Manages some back-end tasks such as programming and sending out the survey
   * **Organizational Psychologist/Executive Consultant**:
     * Assists with questionnaire design
     * Helps your leadership team understand survey results
     * Provides expert guidance throughout the process
     * Typically involved in early stages (strategic alignment & survey design) and later for results interpretation
   * **Survey Team**:
     * Handles technical aspects of survey deployment
     * Manages data collection and analysis
   * **Developers and Analysts**:
     * Work behind the scenes to ensure smooth technical operation
2. **Your Organization's Team**:
   * **Executive Team**:
     * Participates in kickoff call (optional) and alignment meetings
     * Supports and endorses the survey process
   * **HR Team / Project Lead**:
     * Acts as the main point of contact for TalentMap
     * Coordinates internal logistics (e.g., providing participant information file)
     * Assists with internal communications
   * **IT Department**:
     * May need to be involved for firewall or email delivery issues
   * **Managers and Team Leaders**:
     * Help communicate the survey to their teams
     * May be involved in action planning post-survey
3. **Shared Responsibilities**:
   * **Survey Design**: Collaborative effort between our organizational psychologist and your team
   * **Communication Strategy**: We provide templates and guidance, but your team typically handles the actual communication
   * **Action Planning**: We provide tools and guidance, but your team leads the implementation

Here's a typical timeline:

* Month 1: Strategic Alignment, Kickoff, survey design, logistics planning
* Month 2: Pre-survey communication, survey deployment (usually 2 weeks in the field)
* Month 3: Data analysis, results interpretation, action planning

We're flexible and can adjust roles and responsibilities based on your organization's needs and preferences. Our goal is to guide you through the entire process, leveraging our expertise while respecting your knowledge of your own organization.


---

# 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/knowledge-base/step-1-prepare-for-action/prepare-for-action-faq/who-will-be-responsible-for-different-aspects-of-the-project.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.