> For the complete documentation index, see [llms.txt](https://ambitious-impact.gitbook.io/ambitious-impact-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ambitious-impact.gitbook.io/ambitious-impact-docs/explainers-and-house-views/our-charity-taxonomy/guidance-to-adjust-research-based-on-explore-exploit-spectrum.md).

# Guidance to adjust research based on explore-exploit spectrum

## Our evaluation approach should vary according to the position on the explore-exploit spectrum

* Ideas can be placed along the [explore-exploit spectrum](/ambitious-impact-docs/explainers-and-house-views/our-charity-taxonomy.md).
* Researchers should be mindful of this position when deciding what to front-load and how to approach the research.

## Key areas of focus / things to front-load

| Exploit                                                                                                                                                           | Explore                                                                                                                    |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| <ul><li>Detailed cost-effectiveness model</li><li>Evidence review - with special focus on external validity.</li><li>Track record by other implementers</li></ul> | <ul><li>Theory of change and assumptions</li><li>Expert interviews</li><li>Understanding the problem and drivers</li></ul> |

## Reporting standards

**Exploit**

* Implementation matters should be clear in the report. Our preferences for how to implement the intervention and what matters for fidelity should be stated.
* Cost-effectiveness should have clear costing and effect sizing.
* Evidence review should focus on the track record and evaluations pertaining to the idea. Internal and external validity focus.

**Explore**

* Be very clear stating what the known unknowns related to the idea are, and how different resolutions to those unknowns would affect our view on the idea
  * For instance, you can add a table with headers "Question", "How we think this can be investigated", and "Why it matters" to the remaining uncertainties section.
* Cost-effectiveness does not need to be detailed, but rather should focus on:
  * what drives cost-effectiveness
  * uncertainty / monte-carlo driven approach
  * plausible range is good enough
* A clear view on what the problem is, and what barriers matter. Clear leading candidates for a theory of change.


---

# 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://ambitious-impact.gitbook.io/ambitious-impact-docs/explainers-and-house-views/our-charity-taxonomy/guidance-to-adjust-research-based-on-explore-exploit-spectrum.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.