DevRel Scribbles
  • What are Scribbles?
  • Index
  • Developer Advocacy
  • Developer Advocates
  • Life as a developer advocate
  • Modernising Red Hat’s enterprise developer program
  • Engaging 9-year-old software developers
  • Making 22-year-olds love 26-year-old software
  • Dogfooding developer products: gathering insights from internal hackathons
  • How far does your ethical responsibility stretch for the tech your devs create?
  • Outside the lecture theatre
  • How do you design programs for diversity?
  • Build the Platform Your Developers Actually Want
  • Measuring dev rel programs far beyond marketing activities
  • Developer Evangelism
    • Developer Evangelists
    • How to rock a technical keynote
    • The Art of Slide Design
    • The Art of Talk Design
    • The Art of Story Design
    • Dev events beyond 2021
  • Developer Experience
    • The Power of Content
    • Building a Developer Community in an Enterprise World
    • How to lose a dev in three ways
    • Developer relations, why is it needed?
    • The hierarchy of developer needs
    • GitHub is your documentation landing page
    • Docs as engineering
    • Commit messages vs. release notes
    • A11y pal(ly)- crafting universally good docs
    • Inspiring and empowering users to become great writers, and why that’s important
    • Solving internal technical documentation at Spotify
  • Community Management
    • Building community flywheels
    • DevRel = Community Management?
    • Creating high-quality communities
    • How to grow a healthy Open-Source community?
    • Managing communities at scale
    • Using community to drive growth
    • Useful community success metrics
    • Communities aren't funnels
    • How to mobilise your community during a pandemic
  • Managing a DevRel Team
    • Developer Relations + Product
    • Distributed developer relations
    • Understanding company goals
    • DevRel Qualified Leads (DQL)
    • Path to success for DevRel
    • How to move up in your organization
    • Four pillars of DevRel
    • Building your DevRel dream team
    • Managing the burnout burn-down
    • I messed up and I’m going to get fired
    • How to report on community relationships without being creepy about it
    • How to scale a developer relations team
  • Misc
    • Is developer relations right for you?
    • Tooling your way to a great DevRel Team
    • Planning your DevRel career
    • Success metrics as narratives
    • Get executive buy-in or else
    • Introduction to the AAARRRP devrel strategy framework
    • Strategy for developer outreach
    • Connecting dev rel and product
    • Performance DevRel
    • Ultimate cheat codes for healthier travel
Powered by GitBook
On this page
  • Summary:
  • Scribbles:
  • Foundational Categories-
  • 3 Functions of Developer Relations-
  • Developer Advocacy
  • Developer Experience
  • Community Management
  • Internal Community
  • How to find balance b/w the 3

Was this helpful?

Export as PDF
  1. Managing a DevRel Team

Path to success for DevRel

Scribble from Mary Thengvall's amazing blog "The DevRel Path To Success: Awareness, Enablement, Engagement", which talks about what are the key elements of a developer relations team.

PreviousDevRel Qualified Leads (DQL)NextHow to move up in your organization

Last updated 3 years ago

Was this helpful?

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-

  • Awareness

    • Making sure that developers know about the product, making them aware of the targetted product's existence.

  • Enablement

    • Documentations, guides, tutorials, existing libraries, use-cases, etc. to enable the developers to use your product.

    • Making developers understand that using your product solves their problems can be a huge plus point for them to adopt the product.

  • Engagement

    • Engaging with the community.

3 Functions of Developer Relations-

  • Developer Advocacy

  • Developer Experience

  • Community management

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.

  • Making sure the team is aware of relevant feedback from the community.

Developer Experience

  • Responsible for standardization, accessibility of documentation for developers.

  • ^ allows the team to put a finishing touch after a fantastic talk from the developer advocate at a tech conference.

  • Gives people the confidence to know that the product can solve their problems with the help of fantastic guides and resources available.

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

    • serve the community better

    • better communicate with customers

    • write, speak and code in public.

  • 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.

  • Prioritizing your task and working across teams to accomplish goals.

The DevRel Path to Success: Awareness, Enablement, Engagement — Mary Thengvall - Community BuilderMary Thengvall - Community Builder
Blog
Logo
Click to zoom,.