I noticed when the term “Measuring Success/KPIs” comes up, it’s a hard discussion to have as not everyone has clearly defined these metrics or they may be struggling to define KPIs that quantifiably prove the value a Developer Relations (DevRel) organization contributes to the bottom line. . So as a group, we came up with a generic list that a DevRel team out there may find very helpful.
This is intended more as a discussion starter here on dev.to as every item is worthy of its own thread. Or if you have any information that would be valuable, please include it in the comments below, and I can add you as a contributor. (include your twitter handle).
The Seattle DevRel community came together to meet at the Microsoft Reactor to listen to a few talks, network, and learn from each other. On top of that, we did a group project where we compiled lists of the ways we measure success.
“What do you measure that benefits your team?” means the things you track that are valuable to your team, but not necessarily data that the higher ups need to see consistently. Then there’s the KPIs that align with company-wide KPIs. Although there were two questions asked, we realized that some metrics a DevRel team would track wouldn’t work for other teams in the company but they still worked for measuring their individual team's goals and contributions.
What do you measure that benefits your team? What do you measure that is valuable to higher ups? How does this align with company wide KPIs?
- Internally evangelizing and getting developers from other teams involved in speaking engagements.
- Defining what success looks like in different social media channels: impressions, likes, reposts, shares, etc. and assigning a value to each action.
- Partner networking, blogs (Sales Qualified Leads) grow usage down the road and turn into paying customers
- MQLs (Marketing qualified leads)
- Engagements for developer focused websites specific to language
- Traffic to your DevRel-managed websites.
- Number of speaking engagements and number of attendees in your talks
- Number of sponsored events / attendance. Leads per event.
- # of champions and engagement with their activities, growth of champions.
- # of partners or developers that are engaging with our content
- Code contributions by external developers and what people are actually doing.
- External growth and feedback
- What "Thought leadership" means for your product and how you measure it.
- Decrease the number of support requests while increasing the numbers of self-served users via the docs
- Customer sentiment favorability survey and what is the score/target for 16. onboarding experience (NPS)
- Growth/number of 3rd party applications/extensions (marketplace, developer activity)
- # of unique visitors to content/engagement of content (sample code, PRs, Tutorials, Bug submissions, live-stream content)
- Decrease time to activation: end of onboarding, time to deploying first project
- Increase time to deactivation
- Measuring post sign-up activities/engagement, usage beyond simply downloading
- Stackoverflow posts, forum activities, Slack forum, any collaboration tool. How many users there? How many questions there?
- Feedback into product roadmap, number of feature requests into product
- Number of user/paid user signups
- Number of 3rd party blog posts/tutorials about product (organic press mentions)
- Awareness of your company to developers you’re looking to hire
- Decrease customer churn
- Attributed SQLs/MQLs (Ex: Visited docs before becoming MQL)
- Organic social media mentions
- Number of Downloads
- Think of where DevRel sits in your organization. It may affect (OKR) 31. objectives down the road.
- PR Analyst involvement
- # of events planned / tracking industry engagements
- Number of partnerships with technologies to create integrations between both products.
- Influencers sharing/writing/mentioning about your product to their developer following
- DevRel solved recognized problems.
- Weekly SDK downloads
- Making sure what you're measuring aligns with company goals
- Awareness of what you are measuring and why
- Landing features that meet established customer needs (and getting the data to establish them)