Growth/Growth 2014/Quarterly Planning

The following are notes from the Quarterly Product Planning (Janurary-March 2013) for the Editor Engagement Experiments team. This is not a roadmap, but is rather a description of the team's thinking at the beginning of the quarter. Since our last intensive planning session was in the fall, it was a particularly good time to stop and look farther forward in to the future than the next few development cycles.

Background
This summary of the quarterly plan for E3 was developed by the team in early January. Partially in preparation for the Quarterly review, we collaborated on a followup to our last round of prioritization, which led to the development of our current work.

Features
Subject to the results of data collected and the associated performance metrics for each project, E3 currently plans on tackling the following features development over the next three months.

Account creation
Rationale: This is a productization and infrastructure project based on A/B testing of account creation that is now complete. The most successful test version has been expanded to be given to all English Wikipedia users for several months, but making a permanent version of the user interface and analytical modifications is a necessity. In addition to the user-facing portions of account creation, we have found a great deal of use in the ability to tag users who come from particular funnel or event.

Breakdown:
 * Productization of the new Agora-style UI
 * I18n and l10n
 * An associated login redesign
 * Campaign support, which is three broad parts:
 * User tagging
 * Bucketing
 * MediaWiki tags

Guided tours
Rationale: Guided tours is a general purpose tool for educating users about Wikipedia interfaces and community processes. In particular, it is able to easily be adapted to support other key E3 initiatives like the onboarding process, helping teach users about the mechanics of editing or show them where to find additional tasks.

Breakdown:
 * Productization and l10n
 * A guided tour for GettingStarted
 * Other guided tours in support of onboarding, TBD
 * Support for community-created tours and other feature tours

Onboarding (GettingStarted)
Rationale: Onboarding (GettingStarted) is the primary user-facing project of Editor Engagement Experiments. By directly serving potential new editors compelling tasks, this is our most direct route to increasing the base of new editors on Wikipedia.

Breakdown:
 * Post-edit task assignment, including any necessary integration with Echo and adding a way for users to navigate back to GettingStarted
 * Special:GettingStarted optimization, including...
 * SuggestBot productization (i.e. a recommender system and task repository)

Related features work deferred for now
These ideas came up as options during discussion, but were deferred to either another quarter or depend on data to suggest whether they are good avenues or not.


 * Developing onboarding support for key alternate user flows, such as article creation and editing of semi-protected pages
 * Support for custom signup experiences and post-registration landing pages via campaigns
 * Redesign of GettingStarted in to an editor dashboard
 * Work on the wikipedia.org portal to drive signups and aid returning users

Infrastructure, analytics, and metrics
Rationale: the following two pieces of infrastructure are critical to the team's ability to measure the effectiveness of individual products, in relation to the active editors target.

EventLogging

 * More robust campaign support (e.g. )
 * Real-time monitoring/alerts
 * Preliminary support for funnel analysis/automated statistical testing
 * Documentation (seriously!)

Metrics API

 * Cohort metric visualization (with analytics team support)
 * First public release/announcement
 * User tag repository redesign and tag update jobs