> 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/plan-for-success.md). # Plan for success How to define success metrics and KPIs to measure the impact of your Snyk implementation ## Determine success metrics with Snyk Implementing Snyk provides an opportunity to enhance your application security. But how do you know if you're getting the most out of it? Key Performance Indicators (KPIs) are essential measurements that track Snyk's impact and help guide your security journey. KPIs give you valuable insights by monitoring key metrics at each adoption phase - from raising awareness to preventing new issues. They help you: * Assess progress toward security goals * Identify areas needing improvement * Demonstrate Snyk's value to stakeholders Tracking metrics aligned to each stage provides tangible insights into what's working well and where improvements may be needed. KPIs help optimize your use of Snyk and progress your application security program. ## Example metrics These are just some potential examples of success metrics to consider. Analyzing relevant data points at each stage can provide insight into what's working well and identify areas for improvement. ### Gain visibility * Percentage of Projects that have been successfully scanned for vulnerabilities * The number of critical and high-severity vulnerabilities identified * Mean time to complete the initial scan for a Project * Progress in prioritizing vulnerabilities by severity level ### Prevent new issues * Percentage of pull requests or builds that are failing based on Snyk automation * Reduction in new vulnerabilities introduced after automation is turned on * Time taken to address blocked pull requests and resolve them ### Build awareness * Number of developers who have been introduced to Snyk * Percentage of Projects that have been tested with Snyk during this phase ### Fix backlog * Percentage of existing vulnerabilities that have been resolved * Mean time to fix vulnerabilities from the backlog * Number of auto-fix pull requests raised and successfully merged * Progress in using Jira integration for managing vulnerabilities and tracking fixes --- # 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/plan-for-success.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.