# Tools and trials: overview

See, and coalesce ideas from the links below (and more)

## Discussion

Here, we propose methods for grouping, organizing, and categorizing these tools for motivating effective giving and action:

{% embed url="<https://daaronr.github.io/ea_giving_barriers/chapters/tools.html>" %}
Barriers project (Reinstein)
{% endembed %}

1. Theoretical frameworks --> tool categories
2. Certain outcomes are relevant to some tools only
3. Atheoretical 'trying different marketing colors' and tools that push several buttons

## Existing categorisation

{% embed url="<https://daaronr.github.io/ea_giving_barriers/chapters/tools.html>" %}
Barriers project (Reinstein)
{% endembed %}

{% embed url="<https://docs.google.com/document/d/1Sps58H0LKvoLvzSSa2Yav3kFO1vDSVzsYXoYyWzvol0/edit#>" %}
GWWC brainstorming
{% endembed %}

As well as

{% embed url="<https://airtable.com/shrUGJuhyxrKGMEUm>" %}

## Some tools and tests of high-interest (overview, quick presentations)

## Nick Fitz: "some quick types of different tests/questions EA orgs are interested in"

* identifiable victims vs statistical (etc), (DR: Some groups have principled objections to presenting identified victims; which ones do *not?*)
* emotional vs factual/statements,
* videos v images v text,
* positive v negative valence,
* opportunity v obligation,
* cause areas (Not sure what exactly this meant)
* different framings for specific EA orgs
  * e.g., for GWWC they want to test 1% v 10% pledge asks,
  * for CES they want to test saving-democracy v representation messaging,
  * for Humane League they want to test different types of animals, etc)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://globalimpact.gitbook.io/untitled/background/tools-and-trials-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.