Growth/Growth 2014/2013-14 Goals

This document contains more detailed explanation and rationales for the our 2013-14 goals.

Our Annual Plan target
To quote from the Annual Plan itself:

"By end of June 2014, we expect to achieve a sustainable increase in the Total Active Editors core metric (registered users across all projects who make >= 5 contributions in the content namespace, de-duplicated) by 2.4K per month, adjusting for seasonality and length-of-month. This target is deliberately conservative about the estimated impact of larger scale feature changes (Visual Editor, Echo, Flow, etc.) because we cannot make realistic assessments about their likely impact at this time. It is therefore primarily driven by current data on our continuing editor engagement interventions."

How the target was created
To expand on the contents of the Annual Plan document, we generated our target by looking at the current rates of new active editors we gain with our team's onboarding features, and then observing how many additional editors we would gain if we made certain increases in our activation rates. For example, consider the following planning scenario, using only English Wikipedia as a test case...

Why we need goals, in addition to the Annual Plan target
Most Wikimedia engineering and product development teams have set specific features as their commitment in the Annual Plan. For instance, Flow and VisualEditor have described dates and product requirements for shipping certain software to users. Our team has taken a unique approach in making growth -- including a specific number of additional active editors -- our goal.

While this provides us with a clear mission, it does not provide much detail about how we aim to meet our target.

Our product framework
We use a systematic approach to choosing products to test and build, with the following hierarchy that starts very general and becomes more specific.


 * 1) The user lifecycle and areas of focus, which are:
 * 2) * Acquisition: how to attract more readers and anonymous editors to signup
 * 3) * Activation: how to help more newly-registered users become active editors
 * 4) * Retention: how to help active contributors stay that way
 * 5) * Reactivation: giving formerly active contributors a reason to return
 * 6) User experience problems: for each of these areas of focus above, we can list current problems users face
 * 7) Experimental solutions: for each problem or set of problems, we can hypothesize solutions to test
 * 8) Products: if a solution works, then we can develop it in to a mature, permanent feature of Wikipedia