Analytics/Goals/2014-15 Q1 EEVS Dashboard

Goal

Implement a dashboard to visualize key metrics defined by the research team and usable by product teams to drive goals and instrumentation.

• Metrics: the Editor Model, and number of daily {Active Editors, Edits and Pages Created}
• Broken down by all 882 projects and target site (desktop website, mobile website, apps)
• With a default view showing the Rolling Monthly Active Editors for the top 7 wikis.
• Teams immediately benefiting: Growth, Mobile, VE, Multimedia

Value Proposition

Executives and product teams will use the dashboard measure the impact of products on wikis and the community.

The dashboard is a starting point to get an overview on the health of the wikis and explore any emerging issues.

The editor model is a new and simple way of breaking down editor metrics into acquisition, activation and retention. This helps focus the goals of future product improvements.

Outcome

• Prototype Website
  • MVP - minimal feature set necessary to make the project useful
  • Experiment with visualization technologies
  • Propose an alternative to Limn Dashboards
  • Simple & easy navigation to any metric and wiki project (designed in collaboration with UX team)
  • Default view when loading the website of most commonly needed view
• Wikimetrics generates the data
  • available on a webserver, in JSON files, in a hierarchical directory structure
  • updated daily and historical data starting in 2007
  • New metrics:
    • Newly Registered Users
    • Rolling Monthly Active Editors
    • Rolling New Active Editors
    • Rolling Surviving New Active Editors
  • > > > #Edits and #Pages Created
  • > > > Metrics are broken down by desktop site, mobile site and apps

Notes

• Hosting: we chose to deploy in Labs and not production
  • pros: do not have to work with OPs to set this up, we can be more agile.
  • cons: do not get the monitoring and security that comes with setting this up in production