Based on discussion in issues #293 and #332.
This image is taken from the Measuring Developer Relations article written by Shawn @swyx Wang. This article encompasses our vision of KPIs.
As described in #326, there are many metrics that we can measure, and it's hard to choose one North Star metric for DevRel. North Star metrics are for companies, not for teams.
Ultimately, DevRel's goal is to get more active users, and we should measure this metric's growth. But this is not a KPI that DevRel can use as it stands because we're not the only team doing work that influences this metric. It would not be fair to rely on this sole indicator to evaluate our performance.
As explained in the article and in our manifesto (even if it needs some rework), we're embracing the 3C's approach. (In the article, "Product" is our equivalent of "Code"). And I think that we need the equivalent of a North Star metric for each of these pillars of our initiatives. This means one master KPI for Community, for Content, and for Code/Product, and other metrics that can be useful to track.
| ID | KPI desc | Data | Chart |
|---|---|---|---|
| 0 | Monthly active databases (considered as our users: MAU) | From telemetry data | Amplitude (private link) |
The main KPI is community health. This can be measured through community members' activity, the size of the community, the number of discussions... It's hard to define the precise metric to track. Fortunately, the Orbit model provides the right tools: the size of each Orbit. Here we focus on Slack. We could argue that the community is also on GitHub, Stack Overflow... if needed, we will re-assess these metrics again.
Community dashboard on Amplitude (private link)
| ID | KPI desc | Data | Chart |
|---|---|---|---|
| 0 | Size of each Orbit | From orbit report. Following how Orbit defines its orbit repartition, it's also interesting to look at the average love score for each orbit | Amplitude (private link) |
| 1 | Presence for each orbit and for the whole community | computed, as described in #327 | Amplitude (private link) |
| 2 | Number of Discord community members | Currently on Notion - source: Discord (private links) | chart (private link) |
| 3 | Number of Discord community members active in the last 30 days | Currently on Notion - source: Orbit (private links) | chart (private link) |
| 4 | Number of messages and discussions | Currently on Notion - source: Discord (private links) | chart (private link) |
| 5 | Number of Champions | WIP |
The main KPIs are analytics on the Ressource Center. The main current difficulty is that the Ressource Center doesn't exist yet, and we haven't done much work about it. In the meantime, we can rely on other metrics.
Content dashboard on Amplitude (private link)
| ID | KPI desc | Data | Chart |
|---|---|---|---|
| 0 | Analytics on the resource center | WIP | |
| 1 | Number of UGC (blog posts, tutorials, ...) | Currently on Notion - source Notion list (private links) | TODO |
| 2 | Number of events and attendance | Currently on Notion - source UGC Notion list and Events Notion list (private links) | TODO |
| 3 | Number of workshops and attendance | Currently on Notion (private link) | TODO |
| 4 | Number of newsletter subscribers, opens and clicks | Currently on Notion - source: Mailchimp (private links) | chart subscribers - chart engagement (private links) |
| 5 | Number of Twitter followers, mentions, and engagement | Currently on Notion - source: Twitter (private links) | chart followers - chart engagement (private links) |
| 6 | Number of Linkedin followers, mentions, and engagement | Currently on Notion - source: Linkedin (private links) | chart followers - chart visitors(private links) |
| 7 | Number of blog posts created and audience | Blog posts currently on Notion - source: Meilisearch blog / audience source: Fathom | chart blog posts creation (private link) |
| 8 | Number of demos created | Currently on Notion (private link) | TODO |
| 9 | Number of use cases | Currently on Notion (private link) | TODO |
| 10 | Domain authority | Currently on Notion - source: Moz (private links) | TODO |
The main KPI is the number of Meilisearch instance launches (edit: previously I preferred downloads, but launches seem more relevant). Distribution is critical, and this measures if it's done right.
Code/product dashboard on Amplitude (private link)
| ID | KPI desc | Data | Chart |
|---|---|---|---|
| 0 | Number of Meilisearch instance launches | from telemetry data | Amplitude (private link) |
| 1 | Number of contributors | from Orbit (private link) | asked in #327 |
| 2 | Number of contributions | from Orbit | Amplitude (private link) |
| 3 | Number of GitHub Stars | from Github | Amplitude (private link) |
| 4 | Number of integration users | from telemetry data | chart SDK - chart plugins (private links) |
| 5 | NPS/Sean Ellis question | not done yet at Meilisearch |