# Path to success for DevRel

{% embed url="<https://www.marythengvall.com/blog/2021/3/9/the-devrel-path-to-success-awareness-enablement-engagement>" %}
Blog
{% endembed %}

## Summary:

* Foundational Categories- ***Awareness***, ***Enablement*** and ***Engagement***
* Functions of DevRel - ***Developer*** ***Advocacy***, ***Experience*** and ***Community*** ***Management***
* ***Understanding the balance b/w the three*** functional categories

## Scribbles:

### Foundational Categories-&#x20;

* ***Awareness***&#x20;
  * Making sure that developers know about the product, making them aware of the targetted product's existence.
* ***Enablement***&#x20;
  * Documentations, guides, tutorials, existing libraries, use-cases, etc. to enable the developers to use your product.&#x20;
  * Making developers understand that using your product solves their problems can be a huge plus point for them to adopt the product.
* ***Engagement***&#x20;
  * Engaging with the community. \ <br>

### 3 Functions of Developer Relations-&#x20;

* Developer Advocacy
* Developer Experience
* Community management<br>

![Click to zoom,.](/files/-MeIli_OskvJQwrt-8RI)

### Developer Advocacy

* Responsible for making sure the community is ***aware***
* Producing content like blog posts, live streaming, public speaking/talks, etc.
* Building relations ships in the tech industry.&#x20;
* Making sure the team is aware of relevant feedback from the community.<br>

### Developer Experience&#x20;

* Responsible for standardization, accessibility of documentation for developers.&#x20;
* ^ allows the team to put a finishing touch after a fantastic talk from the developer advocate at a tech conference.&#x20;
* Gives people the confidence to know that the product can solve their problems with the help of fantastic guides and resources available.&#x20;

### Community Management

* Working with the most engaged community members.
* ^ those who run meetups, speak at events on the company's behalf.
* Goal is to build a stronger community of people as well as connections.

### Internal Community

#### Internally -> Co-workers

* Awareness OF
  * team's existence
  * the feedback that the community is willing to provide
  * types of processes that can be provided
  * DevRel qualified leads
* Enabling to&#x20;
  * serve the community better&#x20;
  * better communicate with customers
  * write, speak and code in public.&#x20;
* Engaging co-workers with the community with conferences, social media, forums, etc.

#### Externally ->

* Awareness OF
  * existence of various products and projects
  * team and mission
  * resources
* Enabling THEM
  * get up and running quickly and easily
  * successful in their role
  * try new things along with amplification of work
* Engaging
  * using forums, slack, social media, conferences, meetups
  * contributing and collaborating to move members up the pyramid of engagement

### How to find balance b/w the 3

* Understand company goals
* Find allies in your company
  * Awareness in the marketing dept.
  * Enablement in product and engineering.
  * Engagement in support and customer success team.&#x20;
* Prioritizing your task and working across teams to accomplish goals.&#x20;


---

# 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://scribbles.devrel.page/managing-a-devrel-team/path-to-success-for-devrel.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.