Made by the team at Orbit.
Reference
One way to demonstrate the impact of community activities is by calculating Natural Rate of Growth (NRG) and showing how community and DevRel contribute. NRG = 100 x Annual Growth Rate x % Organic Signups X % ARR from Products
Writer, fencer, and co-founder and CEO of Orbit
Wisdom
DevRel cannot be held responsible for the final outcome, whether that is a guest post, a partnership, a new hire or a converted customer. The value DevRel delivers is the connection itself—the opportunity for marketing or product or sales or another team to transform the DevRel qualified lead into a valuable business asset. That’s what you have to measure.
DevRel director @Camunda and author of The Business Value of Developer Relations
Wisdom
Having community insights at hand in GitHub issues and PRs is a great way to direct my open source efforts to new and/or inexperienced contributors, improving their contributing experience.
Software Engineer, Orbit
Add to Google Chrome
INSTALL
Wisdom
You don’t need everything you do to build community to be tied to revenue.
It’s okay to do things just to build the community and trust that the value will show up in ways you can’t measure.
In fact, it’s a requirement in order to build real community.
Founder of @cmx, VP Community @bevylabs
Wisdom
If the metrics change and you don't, stop measuring it. If you're not taking action in response to the metric going up or down (or qualitative getting better or worse), then you shouldn't be measuring it. You're wasting effort, and other functions will be more aware than you think.
DX Consultant | Developer Relations Manager, Apollo
Reference
Community managers should track the Love and Reach of their community as well as the distribution of Orbit levels, and the change in each over time.
Writer, fencer, and co-founder and CEO of Orbit
Reference
Weekly Active API Tokens: The mere act of generating an API key does not measure usage since even non-developers can view API keys without any real use for them. Since most APIs limit access to authenticated users, we are able to track how many distinct tokens are accessing our API platform on a given week.
CEO @MoesifHQ and API Engineer
Wisdom
The mission of a developer relations team following the orbit model is to facilitate high-quality word-of-mouth exchanges.
the developer advocate's advocate · co-founder / CTO @OrbitModel · formerly @algolia and @keen_io · Ruby · Rails · JAMstack · he/him
Wisdom
Developer marketing KPIs and DevRel KPIs are different. According to our survey, the top 2 DevRel KPIs were: 1. Registered developers accounts (48%) 2. Developer satisfaction score (48%).
On the other hand, the top 2 KPIs for developer marketing were: 1. Page or video views (55%) 2. Unique visitors or IP addresses (54%)
View the full results in the source below.
Marketing & Under The Hood of Developer Marketing Podcast Host @SlashDataHQ
Wisdom
Don't measure that which is already counted. If you try to use metrics that are already owned by another team/function, then you run the risk of: 1) competing against a team you should be impacting, 2) never being able to produce the same results as a team dedicated to that metric, and 3) Doing the same work that another function already does well.
DX Consultant | Developer Relations Manager, Apollo
Wisdom
Not all metrics are equally trusted. It turns out, the more degrees of separation between your metric and your company's north start metric (generally revenue related), the less likely it is to be trusted. Just because you show a report doesn't mean others trust the associated impact on the business. Sometimes you have to build trust in your metrics.
DX Consultant | Developer Relations Manager, Apollo
Made by Orbit with Gatsby, Framer Motion and Zeit.
Inspired by and forked from Inbox Zero.
Privacy Policy here.