---
# System prepended metadata

title: Developer Advocates @ The Graph
tags: [The Graph]

---

---
tags: The Graph
---

# Developer Advocates @ The Graph

## Welcome Nick :tada:


**Resources**
[Internal Advocates Handbook](https://www.notion.so/The-Graph-s-Advocates-c0b5c5e049f64b159be555b18c60d52e)
[Advocates from Twitter](https://docs.google.com/spreadsheets/d/1u_D59YXE5k6QD20kwYMw8AyPintCzbGyT0XNYWJjJaM/edit?usp=sharing)
[Notion Guide](https://www.notion.so/STAGING-Become-a-Graph-Advocate-b3e93afb4c3847ffa1c384942908b67d)
[Advocates Program Ideation Session](https://hackmd.io/GXMqpSo7SoSjqAih3Vw10g?view)

**Templates**
[Outreach Email Templates](https://hackmd.io/gI3lPsgYQPOgo_j3KfwC1g?view)
[Rejection Email Template](https://hackmd.io/gnxiiP1WQh6R2eWTSov75A?view)
[Advocate Email Templates](https://hackmd.io/jZHq7bR1SJufQSO-AQ4RvQ?view)


## Onboarding 


:books: Study the Community
---

### What is working

```
* Passionate and various profiles (devs, delegators, indexers, non-techncial) Understands the mission
* organic adoption, self-service exeperience 
* product-market-fit
* self-organization
* identifying and elevating contributors delegating and filling the right roles
* indexer experience - know when/where to place the right talent
* organic interest funneled to the right place
* proper funnels for each user
* subgraph really solved the pain-point, a community built even a year before
* internal & external members able to keep up with technical support - set intentions 
* various stakeholders are accounted 
```
:question: 


### What is a head scratcher
```
 hackathon purpose is transitioning from feedback loop to awareness 
 
 * struggle with in-person events, have not organized many, maybe no bandwidth
 * how to activate more activation from sub-communities
 * how do we scale events, ability for members to contribute and opportunities
 * awareness of community happenings (Graph related but not owned), sentiment analysis 
 * technical misinformation, prioritizing high-quality info
 * community is under-utilized, where do they go and grants
 * didn't follow-up on survey results
 * how to democratize to not bandwidth constraints
 * ambassadors lead community engagement
 * engaging delegators, capacity constraints, comms with non-tech GRT holders and how to engage with indexers to delegate to (esp those who don't know the protocol)
 * active channel moderation across social (technical Discord, forms) (social media are graph awareness)
 * onboarding non-technical(Graph Academy onboarding specific roles), more friendly, crypto wild-west and mistake and lose GRT, how to onboard crypto beginners. Currently have office hours for technical
     - prioritizing non-technical, why relevant
     - non-techncial are the most active voice (viral, fans, advocates)
```

--- 

:bulb: 

- community vs ambassador
- How do we seperate the funnels
- Explain and establish roles and incentives for these participants/community members
- Technical and non-technical ambassadors


:star: 
- index everything, how do we get there, grow the indexer community (run nodes) , curators signal, queries per subgraph
- more devs to build and integrate
- goal is not for The Graph Foundation / E&N to be the central part of failure, accessible language GraphQL easier adoption
- vision align with the graph, spread awareness of decentral
- empower strong contributors, position/leverage strong leaders, creating amabassador, enabling your biggest fans
- infrastructure focus, ambassadors contribute, technical focus, a lot of our users expand beyond devs
- spawn next gen of protocols
- laying the foundations before building the rest of the building
- Graph is uniting all protocols and dapps, integrations with top communities (expanding beyond Graph) 


---



:mag: Define Success
---
### What does success look like

- ID strong contributors to act in community building capacity, that they enjoy and sustainable 
- Independence, if people can start teaching people without really having to pull in the staff 
- scaling the culture, unique and drink the koolaid of the graph culture
- having a playbook, product quality franchise playbook, predictability, familiarity of the community 
- strong community of ambassadors that meet with each other
- creativity (a lot came from creators), spreads non-technical ideation
