{"id":4616,"date":"2017-09-28T21:18:38","date_gmt":"2017-09-28T21:18:38","guid":{"rendered":"http:\/\/redmonk.com\/jgovernor\/?p=4616"},"modified":"2017-09-29T11:54:41","modified_gmt":"2017-09-29T11:54:41","slug":"glitch-developer-engagement-and-telemetry-as-a-service-aka-marketing-automation-comes-to-dev-rel","status":"publish","type":"post","link":"https:\/\/redmonk.com\/jgovernor\/glitch-developer-engagement-and-telemetry-as-a-service-aka-marketing-automation-comes-to-dev-rel\/","title":{"rendered":"Glitch – developer engagement and telemetry as a service aka marketing automation comes to dev rel."},"content":{"rendered":"

\"\"<\/a><\/p>\n

I have written before about the fairly shabby reliance on vanity metrics<\/a> in traditional developer relations programs. Marketing wants big numbers, so you just end with a big blunt instrument “number of users” figure.<\/p>\n

“Check out our Developer Portal – we have 4m registered users…”<\/p>\n

But what the vendor fails to say is they have no idea how often these developers use the site, who is doing the work, what bounce rates are. Far better would be to state a smaller number, but have smarter KPIs around engagement. If only 2000 people are doing most of the work in your community, then optimise for them, and be honest. It may not sound so good on a press release, but you’re more likely to get net promoters if you make the user experience amazing for a committed community. The ROI of Dev Rel is seemingly one of the great unsolved business software problems.<\/p>\n

Today Fog Creek software released Glitch for Platforms<\/a> –\u00a0 a tool specifically designed to improve developer adoption of your API. According to Anil Dash, CEO of Fog Creek,<\/p>\n

“For a lot of Dev Rel people, really proving a return on investment is, well, a pain in the ass. If what you\u2019re doing is working, explaining Dev Rel success can feel like a waste of time. Why spend precious time proving what you already know is the right thing to do? If your efforts haven\u2019t worked yet, then metrics can be even more scary\u200a\u2014\u200awhy show your peers data on something that hasn\u2019t clicked?<\/p>\n

The answer is simple: Good metrics can help Dev Rel get the same respect, support and resources that Sales, Marketing and Support already take for granted. You deserve the tools you need to get the Dev Rel job done.<\/p>\n

But so far, we haven\u2019t had good metrics or return on investment for Dev Rel because it\u2019s a really tough problem. This is obvious when we see so many of our most talented peers discussing it in their conference talks and blog posts. Fortunately, they all reach a pretty strong consensus about what\u2019s needed.<\/p>\n

The key is to find the metrics that matter. Ones that help you make smart decisions about your Dev Rel strategy.”<\/p>\n

I would quibble with the idea marketing metrics are all that great, but it’s clear budgets are flowing to the marketing department, partly at least because of a perception that digital marketing has solid numbers behind it. Fog Creek is trying to deliver a comparable experience for Dev Rel.<\/p>\n

I think it’s interesting that, rather than trying to be totally automated, with a needy, spammy, “growth hacking” mindset, Glitch leans into collaboration. Your developer advocates can collaborate with developer prospects using a real time pair programming user interface, to help them get familiar with your API or service. This is a far cry from RTFM in tech, where the documentation is often pretty awful. Early Glitch users are a Who’s Who of organisations developers today are seeking to emulate – Slack, Facebook, Trello, Botkit, and Algolia.<\/p>\n

Josh Dzielak, who Dev Rel Lead at Algolia is unambiguous about Glitch<\/p>\n

\n

My thoughts on Glitch for Platforms on @ProductHunt<\/a> https:\/\/t.co\/aPYBTJrn1Y<\/a> pic.twitter.com\/RuDZTSx9WE<\/a><\/p>\n

— Josh Dzielak (@joshed_io) September 28, 2017<\/a><\/p><\/blockquote>\n