“What actually is Developer Relations?” is a question that I see almost every week as I’m compiling tweets and articles for DevRel Weekly. The confusion doesn’t stem from the fact that it’s never been defined (narrator: “It has!”), but rather from the fact that if you ask 10 different people in the tech industry for a definition of Developer Relations, you’re likely to get 12 different answers.
While most Community Professionals may think that coming up with what KPIs should be measured is a difficult task, I’ve actually seen more failure in how the KPI measurement is executed and how the data is reported.
When a community fails, more often than not, it’s because there’s no perceived value to the company. Your boss may one day ask you “what’s the value that this community brings to the organization—why do we even have a community?” Unfortunately, if you aren’t prepared and don’t have quantifiable results that clearly reflect the value of your community, you may soon end up forced to close the community or worse, without a job.
How’s your community doing these days? Would you describe it as healthy? What would it even mean to attach the word “health” to an online community?
In today’s post, I want to help you define what it would look like for your community to be one marked by health and wholeness. Then we’ll explore some key areas of community health and learn how to treat any problems you may find.
The idea of an online community has garnered a fair amount of attention over the past few years, especially since providing top-notch customer experience (CX) has become a priority for many organizations. In fact, increasing customer engagement through improved CX is one of the top business priorities of 2019, and an online community is one of the most effective ways to do this.