> 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/getting-started.md).

# Getting Started

TalentMap runs your employee survey as a seven-step program, from the first planning conversation to the actions your leaders take on the results. This page shows you what each step is for, what you finish with, how long it usually takes, and where to go next.

{% hint style="info" %}
**Two ways to use this knowledge base.** Follow the seven steps in order for a full TalentMap survey program. If you are building and launching your own survey in Compass, start with [Create and Launch Your First Pulse Survey](/knowledge-base/survey-design-and-deployment/getting-started-create-and-launch-your-first-pulse-survey.md) for the hands-on workflow, then use Steps 5 to 7 for reporting and action.
{% endhint %}

***

## How this knowledge base is organised

Articles are labelled by how much they cover, so you can pick the depth you need.

* **Overview**: orientation and conceptual understanding. Read it first when a feature or step is new to you.
* **Quick Start**: the minimum steps needed to complete the task.
* **Complete Guide**: the full workflow, configuration options, edge cases, and troubleshooting.

Each of the seven steps below has its own section in the left navigation with articles and an FAQ.

***

## The seven steps

<figure><img src="https://2141019757-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBpBg0aV8RJEUOP2B5Hh4%2Fuploads%2FEIp7PxNL6m2ysdV3TnML%2FScreenshot%202024-05-06%20at%201.45.13%E2%80%AFPM.png?alt=media&#x26;token=04fbcbd1-037e-4fa1-891e-db9adab2e300" alt=""><figcaption></figcaption></figure>

The steps run in order. Steps 2 and 3 usually overlap, and Steps 6 and 7 continue for as long as your leaders are acting on the results. Durations are typical planning ranges for an engagement survey and vary with organization size, stakeholder availability, and how many questionnaire revisions you need. See [Timelines and Deliverables](/knowledge-base/step-1-prepare-for-action/timelines-and-deliverables.md) for the full planning table.

### Step 1: Prepare for Action

* **Purpose**: agree on what the survey is for, who owns it, and who does what before anything is built.
* **You finish with**: a completed Strategic Alignment session, a kickoff call, and a named survey team on your side.
* **Typical duration**: as quick as a few days after contract, depending on stakeholder availability.
* **Start here**: [Executive Driven Survey Overview](/knowledge-base/step-1-prepare-for-action/executive-driven-survey-overview.md), then the [Prepare for Action FAQ](/knowledge-base/step-1-prepare-for-action/prepare-for-action-faq.md).

### Step 2: Develop Questionnaire

* **Purpose**: decide what you will ask, on what scale, and to whom, then sign it off.
* **You finish with**: a signed-off questionnaire with demographics and any custom items.
* **Typical duration**: 1 to 4 weeks, potentially up to 6 weeks.
* **Start here**: [Questionnaire Design](/knowledge-base/step-2-develop-questionnaire/questionnaire-design.md), then the [Questionnaire FAQ](/knowledge-base/step-2-develop-questionnaire/questionnaire-faq.md).

### Step 3: Pre-Survey Communication and Setup

* **Purpose**: get participants ready to hear about the survey and get Compass ready to send it.
* **You finish with**: an approved participant information file, whitelisted TalentMap email addresses, and a communications plan.
* **Typical duration**: 1 to 6 weeks, commonly in parallel with Step 2.
* **Start here**: [Participant Information File](/knowledge-base/step-3-pre-survey-communication-and-setup/participant-information-file.md), [Survey Communications](/knowledge-base/step-3-pre-survey-communication-and-setup/survey-communications.md), then the [Pre-Survey FAQ](/knowledge-base/step-3-pre-survey-communication-and-setup/pre-survey-faq.md).

### Step 4: Deploy Employee Survey

* **Purpose**: launch the survey, watch response rates, and handle participant questions while it is open.
* **You finish with**: a closed survey with the response rate you set out to reach.
* **Typical duration**: typically 2 weeks, rarely more than 3 weeks.
* **Start here**: [Monitor Response Rates](/knowledge-base/step-4-deploy-employee-survey/monitor-response-rates.md), then the [Survey Live FAQ](/knowledge-base/step-4-deploy-employee-survey/survey-live-faq.md).

### Step 5: Analyze, Interpret and Report

* **Purpose**: turn responses into scores, comparisons, and comments your leaders can read.
* **You finish with**: Compass reports available to your team, plus the presentations TalentMap prepares for you.
* **Typical duration**: 1 to 2 months for analysis and staged reporting.
* **Start here**: [Compass Reports](/knowledge-base/step-5-analyze-interpret-and-report/compass-reports.md), then [Compass Admin](/knowledge-base/step-5-analyze-interpret-and-report/compass-admin.md) for user access and configuration.

### Step 6: Discuss, Clarify and Plan

* **Purpose**: review results with HR and leaders, test assumptions, and choose what to act on.
* **You finish with**: an agreed set of priorities and a decision on where action planning happens.
* **Typical duration**: variable and not time-bound. It depends on how many leadership groups review the results.
* **Start here**: [TalentMap Survey Results Presentations](/knowledge-base/step-6-discuss-clarify-and-plan/talentmap-survey-results-presentations.md), then [Post-Survey Consulting Services](/knowledge-base/step-6-discuss-clarify-and-plan/post-survey-consulting-services.md).

### Step 7: Communicate and Take Action

* **Purpose**: tell employees what you heard and what changes, then track the actions.
* **You finish with**: results communicated to the organization and action plans in progress.
* **Typical duration**: ongoing. Many clients plan to roll results out in month 3 of the program and keep acting on them through the year.
* **Start here**: [Communicating Results](/knowledge-base/step-7-communicate-and-take-action/communicating-results.md), then [Action Planning in Compass](/knowledge-base/step-7-communicate-and-take-action/action-planning-in-compass.md).

***

## Where to find product help

* **Survey Design and Deployment**: build, translate, schedule, and launch surveys yourself in Compass. Start with [Create and Launch Your First Pulse Survey](/knowledge-base/survey-design-and-deployment/getting-started-create-and-launch-your-first-pulse-survey.md).
* **360 Feedback**: guidance for participants and leaders in a 360 program. Start with [360 Overview](/knowledge-base/360-feedback/360-overview.md).
* **Product Updates**: what changed in Compass and when. See [Product Updates](/knowledge-base/general/product-updates.md).

{% hint style="info" %}
**Need help?** Contact TalentMap support through the chat icon in Compass or email <support@talentmap.com>. If you have a TalentMap Project Manager, they are your first call for anything about your program.
{% endhint %}


---

# 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/getting-started.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.
