It’s 2023, and it’s time for a new presentation repertoire! Here are the talks I plan to create and deliver *new* this year.
Measuring Developer Relations has been a topic of discussion, debate, confusion, and uncertainty for the duration of DevRel’s existence as a discipline. How do we measure Developer Relations?
Over the course of my career leading Developer Relations (from manager to executive roles), I have seen dozens of articles and presentations sharing philosophies for measuring DevRel, or suggestions for hundreds of different metrics to track. However, there are very few resources that tell anyone exactly how to measure Developer Relations in a quantifiable, wholistic sense.
In this article I share my Keystone DevRel Metrics framework to demonstrate how you can measure Developer Relations and also communicate the business value of DevRel to stakeholders.
To effectively drive sustainable developer growth and engagement for products that serve developers, I created the Developer Empowerment flywheel. When connecting with developer audiences on behalf of an organization, driving developer growth and engagement needs to be cross-functional, measurable, and scalable.
Let’s dig into the developer audience and what developers are looking for when we evaluate products, technologies, and even the very companies that market to us. How can Developer Relations teams form a positive and lasting connection with their developer audience?
The battle over which department Developer Relations belongs in continues to be long and ongoing. Does DevRel belong in Product? Marketing? Engineering? Any of the above? None of the above?
The goal of this article is to provide an explainer sharing my thoughts on what Developer Relations is, what its core tenets are, and what important questions DevRel works to provide answers to.