Reading/Strategy

The Reading vertical at the Wikimedia Foundation will be formulating its supporting strategy for the.

There will be a series of meetings in August and September 2015 to determine potential strategic positions, enumerate conditions that would be necessary to arrive at those strategic positions, and construct a set of tests to determine in principle whether such necessary conditions can be met in principle.

The strategy formulation approach is based on the work of A.G. Lafley.

The tests will rely upon a blend of prototype testing and quick user surveys. The tests will be implemented and conducted in October and November 2015 (the first two months of FY 2015-2016 Q2), with final Reading strategy communicated in December 2015.

The strategy timeline is outlined below. While the core team attending these meetings will be Reading vertical members plus representatives from Community Engagement and the Team Practices Group, this will be a collaborative and consultative process where we aim to validate and prioritize ideas with the community. After each meeting, minutes will be loaded onto MediaWiki.org and the mobile-l, wikitech-l, wikimedia-l, and wmfall mailing lists will be emailed to solicit feedback on the talk pages pertaining to the meeting minutes.
 * Wednesday, 5-August-2015: Kickoff. Review of organizational strategy and the strategy formulation approach to be used for Reading. The next day when notes go out, a request will be included for community members to provide potential strategic position input through 8-September-2015.
 * Wednesday, 26-August-2015: Q2 feature, part 1. Decide whether a feature should be promoted from beta/apps to stable web (potentially just mobile web) in Q2, and which one if so.
 * Thursday, 27-August-2015: Review existing state Reading strategy.
 * Tuesday, 1-September-2015: Formulate potential future state strategic positions. In the following week, continue review of community provided strategic positions.
 * Wednesday, 2-September-2015: If a determination was made to promote a feature in Q2, finalize feature to be promoted from beta/apps to stable web Q2 and load to goals page.
 * Tuesday, 8-September-2015: Construct tests that would validate whether strategy assumptions could be met. As an example, suppose one potential strategy is to...
 * Friday, 11-September-2015: In person review of proposed tests.
 * Monday, 14-September-2015: Communication of tests.
 * September and October: ad hoc meetings as tests are implemented and rolled out and the outcomes measured.
 * Thursday, 3-December-2015: Department meeting to review test results in whole. Revision of strategy cascade based on test results. Finalize strategy communication plan. Agree on capabilities and management system for new strategy. Review to determine teams or departments that may need additional "cascades".
 * Thursday, 10-December-2015: Review strategy with WMF ED and management.

As the strategy will be crystallizing in the early part of December 2015, it will make sense to align FY 2015-2016 Q3 goals to this strategy and share those goals around the same time.