> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/implementation-guides/team-implementation-guide/phase-1-discovery-and-planning.md).

# Phase 1: Discovery and planning

Phase 1 of the Snyk team implementation: validate your plan, run discovery, and plan your rollout

## Discovery phase steps

* [Validate your Snyk plan](https://docs.snyk.io/implementation-guides/team-implementation-guide/phase-1-discovery-and-planning/validate-your-snyk-plan.md): confirm your license has been applied correctly.
* [Conduct discovery](https://docs.snyk.io/implementation-guides/team-implementation-guide/phase-1-discovery-and-planning/discovery.md): identify stakeholders, integrations, and applications to monitor.
* [Name your Organization](https://docs.snyk.io/implementation-guides/team-implementation-guide/phase-1-discovery-and-planning/name-your-organization.md): decide what to name your Organization.
* [Determine user roles](https://docs.snyk.io/implementation-guides/team-implementation-guide/phase-1-discovery-and-planning/determine-member-roles.md): decide who the administrators are.
* [Plan for success](https://docs.snyk.io/implementation-guides/team-implementation-guide/phase-1-discovery-and-planning/plan-for-success.md): decide how to judge the success of your rollout.
* [Choose rollout integrations](https://docs.snyk.io/implementation-guides/team-implementation-guide/phase-1-discovery-and-planning/choose-rollout-integrations.md): decide which integrations to implement initially.
* [Create rollout plan](https://docs.snyk.io/implementation-guides/team-implementation-guide/phase-1-discovery-and-planning/create-rollout-plan.md): create your high-level plan for rolling out Snyk in your business.

## General pre-rollout questions

Before you start the rollout, ask the following initial questions to help with planning. They are an alternative way to decide your rollout planning process.

### Who is involved?

* Who will manage and oversee the project?
* Who will champion Snyk?
* Who will be the administrators?

### What are your goals?

* Why did you choose Snyk?
* Why are you implementing it now?

### How will your users use Snyk?

How will you provision users and integrate Snyk with your platforms?

* Who will need access to Snyk?
* Who can grant Snyk access to platforms such as Git repositories?

### What will you name your Organization?

* What will you name the Organization in Snyk? The Organization name is public to all users.

### How will you measure success?

* What key performance indicators (KPIs) will you track?
* How will you know you are making progress?
* Are there key development projects that progress tracking should be aligned with, or at least included to measure progress against?


---

# 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.snyk.io/implementation-guides/team-implementation-guide/phase-1-discovery-and-planning.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.
