> ## Documentation Index
> Fetch the complete documentation index at: https://closedloop.sh/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Find and validate product evidence

> Narrow product insights and context, then trace each finding back to the customer and original source before acting.

This guide shows you how to move from a broad evidence feed to a source-backed finding you can use in a product decision.

## Choose Insights or Context

Insights and Context can come from the same customer conversation, but they answer different questions:

| Open         | Use it to answer                                                                                                                   | What you find                                                          |
| ------------ | ---------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| **Insights** | What actionable product problem, request, bug, or improvement did customers report? Who reported it, and how severe is it?         | Individual product-feedback records organized by category and severity |
| **Context**  | Why is a customer making a decision? What is affecting a deal, retention, competitive evaluation, product-market fit, or workflow? | Strategic observations organized by category and strength              |

For example, if a customer says that exports are too slow, so their team uses spreadsheets and may not renew:

* **Insights** captures the product problem: slow exports.
* **Context** captures the surrounding business situation: the workaround and retention risk.

<Tip>If the answer should be a product problem or request, start in **Insights**. If it should explain a customer decision, risk, or workflow, start in **Context**. You can review both when the question spans both.</Tip>

## Prerequisites

* At least one connected source has finished processing
* You know the customer, product area, or question you want to investigate

<Steps>
  <Step title="Narrow the evidence">
    Search for the customer or topic, then apply the available filters. Start with the smallest useful scope and clear filters that do not change the decision.
  </Step>

  <Step title="Open a result">
    Select an item and read the full detail, not only the list-row summary. Confirm the customer, date, source, and surrounding context.
  </Step>

  <Step title="Trace it to the source">
    Open the transcript or external source when available. Check that the extracted product insight accurately reflects what the customer said and that the quoted evidence supports the conclusion.
  </Step>

  <Step title="Choose the next action">
    If the evidence supports a product decision, use it in your Roadmap review. If you need to know when the topic appears again, keep the filters active and create a Watch.
  </Step>
</Steps>

## Verification

You should be able to name the customer, identify the original source, and explain how the evidence supports the product decision.

## Troubleshooting

* **No results:** Clear filters one at a time and expand the date range.
* **Expected source is missing:** Check its latest imports in [Data Log](/docs/guides/data-log).
* **The extracted meaning looks wrong:** Use the correction or archive action available in the detail view instead of relying on the item.

## Related

* [Monitor a topic with a Watch](/docs/guides/watches-and-inbox)
* [Prioritize product work with Roadmap](/docs/guides/opportunities)
* [Understand evidence types](/docs/concepts/insights)