Research:Growth and diversity of Technology team audiences

From Meta, a Wikimedia project coordination wiki
Jump to: navigation, search
21:40, 6 November 2017 (UTC)
Duration:  2017-November — 2018-February

This page documents a research project in progress.
Information may be incomplete and change as the project progresses.

Program 4 of the Technology Department's 2017-18 Annual Plan involves improving the support that the Wikimedia Foundation provides to technical communities inside and outside the Wikimedia Movement who build upon and use our software products and platforms. These users include "including code contributors, documentation contributors, bug reporters, API consumers, volunteers who build innovative solutions to on-wiki workflow issues, researchers who examine the data generated by the Wikimedia projects, value-added vendors who provide services and support based on Wikimedia free and open-source software products, and true 'third parties' who install and use FLOSS software produced by the Wikimedia movement on their own computers for various reasons."

Outcome 2 of this program involves measuring the adoption of Wikimedia technology by these communities. The Technology department currently lacks a set of broadly-accepted, reliable, and meaningful measures for tracking the adoption of our technology by members of these communities—which limits our ability to:

  1. learn how well we are currently serving their needs and how and how much they are currently using our platforms and products,
  2. identify opportunities to grow our audiences, and serve our existing audiences better, and
  3. measure adoption on a per-team or per-product basis over time, including evaluating the impact of any future interventions we make to grow or more fully support our audiences.

This project is the first step towards developing these kinds of metrics. For each of the teams we work with on this project, we seek to answer the following questions:

  1. Which audiences are you currently serving? Who else do you believe you should be serving?
  2. How does your work support the audiences you currently serve? How could you serve these audiences better?
  3. How are you currently measuring adoption from these external consumers? If you don't, do you have any notions of size/adoption rate?
  4. What kinds of audiences are you serving (e.g. individuals vs institutions/organizations)? What is the geographical distribution of these audiences?


This study will consist of interviews with team leads in Tech involved in building platforms with an externally-facing audience and get them to articulate who their core audience is, and how to characterize adoption of their platforms.

At least initially, this research will not involve interviews with members of all Tech department teams. Rather, we will focus on teams that have well-defined external audiences, beyond other WMF teams/departments, and in some cases beyond the Wikimedia Movement altogether. We are conceiving external audiences for Tech teams as researchers, developers, data consumers who build other platforms or products on top of the software products (e.g. MediaWiki), research/analytics resources (including publications, specifications, dashboards, data APIs and datasets), and platforms (e.g. ORES, Toolforge, WikiData Query Service) we develop and maintain.


  1. October 2017: Develop interview protocol
  2. November 2017 - January 2018: conduct interviews with team leads
  3. January - February 2018: Analyze and report results

Teams involved[edit]

This list includes teams for which we have already identified products or platforms that have external audiences. This list may change during the course of our study, as we refine our definitions of audiences, products, and adoption.

  1. Analytics
  2. MediaWiki Platform
  3. Research
  4. Scoring Platform
  5. Search Platform
  6. Services
  7. Cloud Services


Once your study completes, describe the results and their implications here. Don't forget to make status=complete above when you are done.

See also[edit]