Developer relations is an integral part of many software companies that hope to win the hearts and minds of developers. You may refer to it as developer evangelism or community outreach but ultimately, it’s a motion dedicated to ensuring that:
In my opinion, this is absolutely the right order to be driving on, since it’s important to always think of the needs of the community.
But the problem with developer relations is that it’s a subjective, somewhat nebulous field that in most cases doesn’t involve tangible “things“. This can make it hard to measure how successful you or your team are and if you’re hitting the mark with your community.
From my experience and through many discussions with my peers, the typical developer advocate tends to focus on several key outreach mechanisms to engage with developers. These are:
The need to scale a message means that tactics one through five will get the most attention, allowing advocates to reach the largest possible audience. They’re less personal but do afford a big megaphone. Tactics six through nine offer opportunities for more direct one-on-one interaction and engagement, with the chance to meet with community members in person, work with influential developers to ensure they have an opportunity to affect your product direction, and generally put a face to a name.
Of the tactics listed above, the easiest to measure success on are the top five. In most cases, analytics can offer insight into your motions, allowing you to determine how many people were interested in what you had to say. Tools like Twitter Analytics, Google Analytics and Bitly offer tremendous insight into how well your outreach and engagement efforts are doing. The data offered can have a profound impact on how you adjust your tone and message, especially in these semi-autonomous media where anything can be misconstrued and left to interpretation.
For example, my post about ngrok really went over well and, based on the analytics, I can say that it was something that really resonated with my audience:
I’m less concerned about the engagement rate and percentage than I am about the number of impressions—in this case 5,744 impressions. That’s a fairly decent reach and shows that a number of developers were interested in this.
When we get to the lower end of the list, beginning at number six, it’s hard to quantify how well you’re doing, mainly because these are subjective motions that tend to have qualitative value and thus need to be measured as such.
What I mean by this is that it’s very difficult to measure quantitatively the impact, immediate and long-term, that your participation in one of these motions might have. Sure, you can say that you spoke at an event and it was attended by 300 people. But does that really tell you whether your message landed or that you affected product sales? Not really, and this is where the issues come in with many companies that consider developer relations solely as a cost center and not a value-add. The pointy-haired guy wants hard numbers for something that’s more of a soft skill.
In my opinion, measuring this needs to be done through social media tracking of a specific key message you’re trying to land. This means that if you’re participating in an event, you should have an idea of what your goals are so that they can be measured afterwards by analyzing feedback on social media, especially Twitter. Twitter is by far the best medium for gathering qualitative measurement of your engagements. The community uses it extensively to discuss the good and bad of what they see, so if your message lands well, Twitter will know about it in most cases.
Tools like Sprinklr help to offer insight into this and can help you gather information that you can use to measure your success. I personally use TweetDeck’s multi-column capability to track keywords that are important to me, especially at events or during announcements.
As I mentioned, these motions are typically measured qualitatively, which means you need to ensure you save tweets or articles that highlight your motions, whether they’re positive or negative. Yes even negative feedback is valuable and should be used to determine how well you’re engaging with the community and if your company or product is of interest. This tweet regarding my ngrok post is a great example of this:
It’s equally important to ensure that the influencers you work with have clarity about your vision and direction. Most developer advocates have lists of influential developers with whom they have regular conversations and briefings so they can get a pulse of what’s trending and whether their company’s product is actually solving a need.
Tracking how influencers feel is incredibly important because it tells you if they’re understanding your vision and what their sentiment is towards your product and company. Because these influencers have a big megaphone and the ears of the community, being able to proactively engage them at the right time ensures they’re getting the most accurate information to share with their followers. And trust me, they will be vocal for both the good and bad. They’re in a position of trust and thought leadership and rightfully need to express their true feelings about a topic.
Measuring your interactions with them, again, is typically qualitative and from the perspective of a long-tail scenario, since most influencers will take their time to ensure the information is worthwhile to discuss or promote. This is why it’s very hard to measure. The best tool I’ve found for this is Onalytica, which helps to offer engagement opportunities with influencers.
I’d actually really love to hear from other developer advocates on this topic. I know there are plenty of other ideas out there on how to effectively measure engagements, and it’d be great to be able to pool it altogether. I’m hoping you’ll jump in on the comments and offer up your experience and perspective so that we can all benefit and do our jobs better.
Or my team and colleagues:
This article is part of the web dev tech series from Microsoft. We’re excited to share Microsoft Edge and the new EdgeHTML rendering engine with you. Get free virtual machines or test remotely on your Mac, iOS, Android, or Windows device @ http://dev.modern.ie/