Slack community channel for developer relations

Trending amongst API companies is the tendency to invite developers to a Slack community channel. Whilst it may appear to be automatic for advocates in developer relations to create Slack community channels, it may not be for all. Marketing, sales, product management or CEOs who do not wear jeans may be dumbfounded by the idea of Slack community channel.

There are multiple motivations for a Slack community channel. Two of these motivations are salient amongst all considerations. These are metrics where a Slack community channel is a dynamic metric over typically static metrics and centralization.

Dynamic metric

Key to developer relations is metrics. Metrics often arise in tandem with developer relation schemes like Twilio’s where developer advocates are either conference faring nomads or else curators of quickstarts, tutorials, how-tos, x-with-ys, third party integrations, generic functionalities, or blogging in general. Metrics for these item is obvious: page views, conversions from page views to sign ups, registrations, apps, or API calls…