> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/guides/quality-improvement/use-cases-by-persona/qa-engineers/contributing-to-release-informed-decisions.md).

# Contributing to Release Informed Decisions

SeaLights isn't just about numbers; it's about empowering you to become a trusted advisor in the decision-making process. This use case equips you to **leverage data-driven insights from SeaLights and translate them into clear, actionable information for stakeholders**. By effectively communicating testing results, risks, and recommendations, you'll **support proactive risk management, foster informed release decisions, and build trust as a data-driven quality champion.**

***

## **Step-by-Step Tutorial**

<details>

<summary>1. <strong>Gather &#x26; Analyze Data</strong></summary>

* Utilize SeaLights' Test Gaps Analysis to analyze coverage status and risk assessments.
* To shift focus beyond unit testing and gain insights into broader coverage aspects, a Proof of Testing report excluding unit test data can be valuable.
* Deep-dive into critical gaps, understanding their potential impact and mitigation strategies.

</details>

<details>

<summary>2. <strong>Tailor Your Message</strong></summary>

* Consider the needs and interests of different stakeholders (developers, product managers, executives).
* Focus on key metrics and insights relevant to their decision-making.
* Translate technical jargon into clear, concise language everyone can understand.

</details>

<details>

<summary>3. <strong>Present with Impact</strong></summary>

* Prepare visually engaging presentations and highlight key findings and recommendations, focusing on the "why" behind your insights.
* Encourage questions and engage in open dialogue to address concerns and ensure understanding.

</details>

<details>

<summary>4. <strong>Proactively Support Decisions</strong></summary>

* Offer data-driven alternatives and risk mitigation strategies for various release scenarios.
* Collaborate with stakeholders to define acceptable risk thresholds and decision criteria.
* Remain informed of business goals and priorities to align testing efforts with overall objectives.

</details>

<details>

<summary>5. <strong>Track &#x26; Measure Impact</strong></summary>

* Monitor the impact of your data-driven insights on release decisions and quality outcomes.
* Adapt your communication approach based on feedback and evolving needs.
* Share success stories of informed decisions that led to improved quality and risk management.

</details>

By embracing data-driven communication and partnering with stakeholders, you'll transform from a bug finder to a strategic contributor, building trust and ensuring quality remains a core value in every decision made. Remember, data is your power – use it wisely to influence, inform, and drive positive change for your software and 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sealights.io/knowledgebase/guides/quality-improvement/use-cases-by-persona/qa-engineers/contributing-to-release-informed-decisions.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.