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

# Guidance to adjust research based on execute-persuade spectrum

### Our evaluation approach should vary according to the position on the execute-persuade spectrum <a href="#our-evaluation-approach-should-vary-according-to-the-position-on-the-explore-exploit-spectrum" id="our-evaluation-approach-should-vary-according-to-the-position-on-the-explore-exploit-spectrum"></a>

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

{% tabs %}
{% tab title="Execution-dominant" %}
**Core cruxes** will most often be related to implementation matters that the entity we envision can keep control over.&#x20;

Consider how standard operating procedures can scale, how easy they are, and what known unknowns remain. Figure out what, if anything, remains outside of the entity's control.&#x20;

Front-load / prioritize:

* Theory of change and implementation matters
* Evidence&#x20;
* Process for scaling&#x20;
  {% endtab %}

{% tab title="Enablement and/or facilitation" %}
**Key cruxes** will most often focus on how exactly the capacity support would change things. For this, we have to have a good understanding of barriers and how the entity's actions map onto those.&#x20;

Consider how structural barriers interact with the proposed entity's efforts, and focus on how exactly the entity would gain access and be actually additional.&#x20;

**Front-load / prioritize:**

* Barriers and a deep understanding of how other non-capacity related barriers interact with the theory of change&#x20;
* Neglectedness
* Process for scaling / gaining access
* Evidence&#x20;
  {% endtab %}

{% tab title=" Agenda-setting" %}
Key cruxes will usually relate to how and why the entity will persuade actors to prioritize the intervention.&#x20;

A deep understanding of who key stakeholders are and what their motivations are is essential.&#x20;

[Stakeholder mapping is mandatory.](/ambitious-impact-eval/stakeholder-mapping.md)

Front-load prioritize:

* Stakeholder mapping&#x20;
* Case studies to inform tractabilty / evidence&#x20;
  {% endtab %}

{% tab title="Contested influence" %}
Key cruxes will usually relate to how and why the entity will be able to get attention in a contested space, and be strong or persuasive enough to beat other actors with conflicting goals. &#x20;

A deep understanding of who key stakeholders are and what their motivations are is essential.

[Stakeholder mapping is mandatory.](/ambitious-impact-eval/stakeholder-mapping.md)

Front-load prioritize:

* Stakeholder mapping&#x20;
* Case studies to inform tractabilty / evidence&#x20;
  {% endtab %}
  {% endtabs %}


---

# 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://research.ambitiousimpact.com/explainers-and-house-views/our-charity-taxonomy/guidance-to-adjust-research-based-on-execute-persuade-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.