Request for Feedback: Community Team Stats Dashboard

A few days ago, @iandunn asked for feedback on the idea of Stats Dashboard from all the make teams. During today’s Asia/EMEA version of the Community Team Meeting, participants understood that the question is actually quite big as our team has so many areas, numbers and metrics that could be monitored in the dashboard.

Instead of figuring out the ideas metrics for our team in the comments of the original post and making the comments threads long over there, let’s have the initial discussion here in our own blog.

First thing is to get some kind of idea whether operational, analytical, strategic or some combination of those dashboard types would be best for our needs. Here’s a good outline of what different types of dashboards do (usually) mean.

The second discussion is about what metrics we would like to have in the dashboard? There’s already reports in the WordCamp Central, our support tool Help Scout has some reporting possibilities, meetup.com APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. is used to track organisers and events in our chapter meetups but those details are not in the public Central reports. It’s highly possible that I’m forgetting some reports and usage of data we are already doing. But more interestingly, are there some other things we don’t measure in any way currently that could be beneficial to us?

Please share your feedback especially on the questions:

  1. What metrics should be in the Community Team dashboard?
  2. Are there some metrics that would be helpful to have in the dashboard, but shouldn’t be public for some reason?
#stats