Wikimedia Foundation Annual Plan/2016-2017/revised/el

Overview

In order to support community review, please provide a brief description of your organization's work in the upcoming funding period

We at the Wikimedia Foundation are proud to present our full annual plan for the upcoming fiscal year, 1 July 2016 to 30 June 2017, to the Wikimedia community. This year, we are sharing our Annual Plan using the Funds Dissemination Committee format, in order to receive feedback on the plan within the FDC review process.

The Wikimedia Foundation provides critical support for the Wikimedia projects and communities. We maintain the technology that allows people to contribute and share free knowledge with the world. We provide tools and resources, both monetary and programmatic, to support the health of the Wikimedia community. We protect the independence of the Wikimedia projects and volunteers, and raise awareness for the importance of our movement, projects, and mission in the world.

This year’s plan focuses on improving support for--and consultation with--community, responding effectively to changing user needs, and addressing challenges facing our movement. We are investing in areas that we believe the Foundation is uniquely positioned to address, including readership and reach, volunteer retention and engagement, and support for knowledge creation. We will deepen and expand work in our newly clarified strategic directions, while strengthening the core work that supports our communities and projects. These directions distill to reach, communities, and knowledge, and were refined through a public consultation held through mid March 2016. This annual plan accompanies the presentation of the Foundation’s 2016-2018 strategic direction document.

Reach; everyone should be able to freely share in the free knowledge on our projects. We are making it a priority to reach new readers and contributors around the world and improve the experience for all, including those on mobile devices. To do this, we will better understand and respond to the needs of our global readers and contributors through research, new technologies, effective programs, strategic partnerships, and more.

Communities; volunteers and open collaboration are the pillars of the Wikimedia movement. It is the efforts of the global community of volunteers that have made Wikimedia possible, and the community’s health and sustainability are essential to our future. We will increase volunteer retention and engagement through improved programs, experiences, and resources for community members. We will invest in capacity and leadership building to support the continued growth and health of Wikimedia communities.

Knowledge; sharing in the sum of all knowledge is the vision that inspires Wikimedians around the world. 15 years of volunteer work created the world’s largest and most beloved shared knowledge resource. We will increase and diversify knowledge by developing high-priority curation and creation tools and services for user needs. We will support programs and partnerships that increase the quality, breadth, and diversity of free knowledge in our projects.

These strategic priorities will guide the Foundation’s work for the next 18 to 24 months. They can be reviewed in greater detail in our 2016-2018 strategic direction document.

This fiscal year introduces another change for the Wikimedia Foundation, as we reverse some of the recent growth in our overall budget. In 2016-2017, we will focus on incorporating fiscal responsibility and financial planning as an aspect of our overall approach to movement sustainability. Our teams are committed to being efficient with funds, focusing our investments on key programs and initiatives that reflect our strategic priorities, and improving efficiency and reducing costs in our core workflows. We will begin building our endowment to secure the Wikimedia vision in perpetuity.

About our programs

Our department dedicated to community support, Community Engagement, will focus on strengthening effective programs, improving services to community, and facilitating the health of the movement. Community Engagement will foster long-term movement sustainability by helping build supportive, engaged communities by facilitating mentorship in community leaders, supporting high-impact programs such as GLAM, and making it easier for community to access financial and learning resources. Their work primarily serves the second strategic priority, increased volunteer engagement.

The Technology department supports all three strategic priorities. In the coming year, they will create and improve essential contributor services, and undertake research for better insight into the needs of different communities and contributors. They will maintain and improve the performance, security, and reliability of our projects, to ensure their accessibility to users around the world. They will drive essential updates to our architectures and release processes to allow us to build better contribution tools and reader experiences.

Improving and maintaining people’s experiences on our projects is the work of the Product department, enabling our reach, communities, and knowledge priorities. In the next year, they will help people create and discover richer content on the projects more easily, keep people reading and engaged on different devices and platforms, make editing and contributions easier and more intuitive in more languages, support key community tools, and allow people to donate easily and securely. Product allows people from around the world take part in the progress we are making.

Strategic Partnerships, within our Advancement department, supports our strategic priority of reaching more people, through building and managing partnerships that support movement outreach and knowledge sharing around the world. Through the recently reintroduced Global Reach team, they will refine and carefully grow the Wikipedia Zero program, and explore and develop new forms of partnerships in areas of low readership and awareness. They will also manage relationships with key tech partners to support and strengthen our apps and preloads, and create opportunities for corporate contributions.

The Communications department develops and sustains awareness and appreciation of the Wikimedia movement and mission among the global general public. They will design and implement strategic outreach initiatives toward the first priority of reach, to raise awareness of our projects in places where readership and editorship are low. They continue to develop projects and materials to build on the brand that has gained tremendous value because of the trusted work of volunteers. They will also use strategic messaging and campaigns to extend the reach of specific products and narratives that support our mission where people already know and use Wikimedia projects, such as mobile web, apps, and the visual editor.

The Legal department not only supports and protects the Foundation with world class representation and counseling, they also run a number of programs to support the Wikimedia communities. In the coming year, the Legal team will continue supporting community members who have been subject to unfair litigation, defend against challenges to content on our sites and unreasonable requests for user information, advocate for policy that supports our movement values and work, and ensure the use of our trademark supports open culture and our mission.

The non programmatic work by Fundraising, Legal, Talent and Culture, Finance and Administration represents a minority percentage of our budget, but is crucial to the strength of our organization, the health of our culture, and every success of the Foundation.

We are excited to share our plans for the year with you. We look forward to gaining further insights, refining our methods, clarifying our directions, and iterating for improvement and results in all of our work. Throughout everything, we are focused on our vision: A world in which every single human being can freely share in the sum of all knowledge.

Financials: FY 2015-16

The purpose of this section is to give the FDC an idea of how your organization is receiving funds and spending funds toward your current plan.

Table 2 - Program and Non-Program Expenses Summary (all amounts in USD)

Description			FY15-16 Plan	FY15-16 Projection
Program Expenses
	Staffing		24.944.635	23.207.612
	Non-Staffing
		Data Center CapEx	2.209.000	2.309.000
		Data Center OpEx	2.667.793	2.265.304
		Grants	6.300.000	5.361.610
		Outside Contract Services	2.349.395	2.516.490
		Legal Fees	1.350.000	1.417.200
		Travel & Conferences	2.498.591	2.498.591
		Other expenses	1.776.782	1.723.453
	Sub Total Program Expenses		44.096.196	41.299.260
Non Program Expenses
	Staffing		10.290.038	9.040.070
	Non-Staffing:
		Donation Processing Fees	2.400.000	2.500.000
		Outside Contract Services	2.295.498	2.328.403
		Legal Fees	599.000	599.000
		Travel & Conferences	602.624	602.624
		Other expenses (Facilities, Insurance, FF&E, All Hands, Recruiting, Staff Development, Personal Property Taxes, and Etc.)	4.716.644	4.990.643
	Sub Total Non-Program Expenses		20.903.804	20.060.740
Total Annual Operating Expenses			65.000.000	61.360.000

Note: The financial data presented here is not broken out by the specific programs described in the narrative below. One of the Finance department’s FY16-17 objectives is to assess and adapt our existing financial workflow(s) and associated systems to budget and monitor program costs.

Table 3 - Expenses by Departments Summary (all amounts in USD)

Description	FY15-16 Plan	FY15-16 Projection
Community Engagement	6.605.181	6.438.138
Grants	6.300.000	5.361.610
Product & Technology	25.943.064	24.665.267
Communications	2.417.574	2.084.649
Legal	4.055.259	4.046.388
Advancement (Fundraising/Partnerships)	7.422.570	6.874.502
Talent & Culture/Team Practices	3.853.475	3.543.535
Finance/Administration/IT	7.202.036	6.970.261
Governance	1.200.841	1.375.650
Total Annual Operating Expenses	65.000.000	61.360.000

==

Programs: upcoming year's annual plan

==

For each program, please include your targets for each of the global metrics in this table

All global metrics are required (except the optional metric for total number of images/media uploaded), but you may list a target of zero if there are metrics you do not expect results for. You are welcome to provide your other metrics in the detailed program section below.

Global metrics are based on two of the primary strategic goals set out in the 2010-2015 Wikimedia strategic planning process: participation (editors) and content (articles). The Wikimedia Foundation continues to support these metrics as sensible, effective means of measuring the impact community and affiliate programs have in these two areas.

Historically, the Foundation has prioritized metrics of participation (contributors) and reach (readers) as primary metrics. Over the past year, the Foundation has begun to move toward department and team-specific measurements, in order to enable more granular program and product accountability. This has been accompanied by focusing many programs on the strategic priority of reaching more people through the Wikimedia projects.

The FY16-17 Annual Plan has highlighted the need for the Foundation to clarify its approach to global metrics, in addition to the measurable indicators set out for our programmatic goals. We are exploring how to best measure the efficacy our work and anticipate being able to provide clearer metrics in future annual planning.

Please list your goals and objectives for each program. Please be sure your objectives meet all three criteria for each program.

• Be sure the objectives listed are each SMART: specific, measurable, attainable and relevant, and include time-bound targets.
• Include both qualitative targets and quantitative targets, and remember to highlight your baseline metrics.
• Provide any additional information that is important to our understanding of this program. For example, you may include needs assessments, logic models, timelines, tables, or charts. Share how this program will contribute more broadly to movement learning, or explain how your program aligns with important Wikimedia priorities such as increasing participation and improving content on the Wikimedia projects.

Impact of FDC's review on the Foundation's Annual Plan

FDC comments that have been integrated into the plan revision

First, we appreciate the diligence and thorough review that the FDC did of the Foundation’s plan. Every team has reviewed these comments and integrated changes as appropriate. These include further clarification of key programs, goals, and objectives. To see these changes in detail, please refer to Appendix 3 for a summary of FDC recommendations and the revision diff for a complete list of changes.

About FDC comments that have not been integrated directly into the plan

While we have been able to extensively integrate program-level recommendations, we were not able to integrate some of the FDC recommendations for new programs in this revision. Specifically, these include:

• Governance – external assessment of WMF governance: The Wikimedia Foundation has taken this suggestion under advisement, and following discussion with the Board of Trustees during the May 2016 Board meeting, we are looking into a possible external governance review. Under the guidance of the Board, the Foundation is compiling a list of possible third parties that could conduct such a review. Any final decision whether to proceed will rest with the Foundation’s Board of Trustees. The recommended scope and timing– before a permanent Executive Director is hired – is also noted. The Board intends to further discuss this recommendation during their June 2016 meeting.
• Strategy – long-term movement strategy: The new Wikimedia Foundation strategy, introduced on April 1 2016, is intended to guide the Foundation’s efforts for 18-24 months. The Foundation recognizes this plan is intentionally limited in duration and scope. It is intended to take the Foundation through the FY2016-2017 Annual Plan, and offer continuity and guidance to the permanent Executive Director in their preparation of the FY2017-2018 Annual Plan. The Foundation agrees with the FDC that the strategic plan for our work in the coming 18 months does not supplant the need for a movement strategy. The expiration of the 2011-2015 strategy, the growth and evolution of our movement, and changes in global connectivity and knowledge seeking all underscore the need for our movement to develop a united vision for our future. The Foundation views FY2016-2017 as an opportunity to scope the development of such a movement strategy. We will conduct discovery into the needs, resources, stakeholders, timelines, and other variables necessary to develop a successful strategy, with the intention that strategy development process would occur under the tenure of a permanent Executive Director.
• Financials – detailed project budgets: The Foundation’s process for developing an Annual Plan continues to evolve. Starting in January 2016, our new Chief Financial Officer, Jaime Villagomez, worked with departments across the Foundation to meet our scheduled deadlines, with improved information sharing, resource allocation, and accountability. During this process, we identified the need to improve our ability to prepare more detailed breakdowns of resourcing by department and program, on a budget and staffing basis. We are already actively reviewing previously provided FDC feedback and our systems and procedures in order to improve this process for the next round of planning, in order to more effectively prepare and provide more discrete financial reporting. The Foundation is committed to serving as a model for the other movement organizations and a catalyst to encourage all movement partners to attain these high standards.

==

About the Foundation's programs

== ===

Understanding the Foundation’s budget across programs

===

We have developed a few visualizations that may make it easier for readers to understand the overall scope of each department’s work and budgets. In future Annual Plans, we intend to provide more detailed financials on project or program basis.

This first chart illustrates how the Foundation employees are distributed among departments (includes all staff, both programs and non-programs). Roughly half of Foundation staff are working in Product or Technology. Their efforts ensure the projects are maintained, supported, and continuously improved.

Distribution of staff (programs and non-programs) - 277 total.

The next two charts show how the budget is divided by department, specifically for Programs.

Program expenses by department

Program expenses make up $43,025,748, or 68%, of the Foundation’s overall budget. For the $6,800,890 in Community Engagement non-staff expenses, $5,460,000 (roughly 80%) is allocated to community grants. Of the $5,868,775 in non-staff expenses for the Technology department, $4,689,177 (roughly 80%) is earmarked for data center expenses. .

Program expenses by department (Staff, Non-Staff)

The balance of the budget, $19,974,252, or 32%, is devoted to non-program support. This includes all fundraising expenses, administrative and development expenses to support Foundation operations. Note that of the $3,956,238 in non-staffing expenses for Advancement, $2,240,000 (roughly 57%) is for donation processing fees.

Non-program expenses by department (Staff, Non-Staff)

Research across the Foundation (user-centric focus)

The Foundation’s work continues to evolve to be more effective, measurable, and focused on user needs. As part of this evolution, we have increased our emphasis on user insight, research, and analytics. These efforts range from community surveys to generative research to analytics.

Currently, our research and insights functionalities are distributed throughout the organization so that people are best integrated into the areas they serve. This section outlines the framework of responsibility, so that readers can better understand how research is divided across departments and coordinated. Specific FY16-17 programs, goals, and objectives are listed under the particular departments and teams named. While it may not always be explicit in the program descriptions, departments and teams have ongoing communications to showcase work being done and new insights as they are derived.

• Under the Technology department, the Research group has the primary responsibility for research in the Foundation. This group consists of two main teams. Their efforts primarily inform Product and Engineering decisions, but they work with other departments as needed on specific projects.
  • Research Design: This team is tasked with understanding if the design of products and user interfaces meets the needs of our users. This team provides Product teams with evaluative and usability research to develop high-quality products that meet the needs of specific user groups. They conduct generative design research to gain more knowledge about our users and their needs, generating rich data in the form of interviews, surveys, usability studies, and field notes. These insights inform the development and prioritization of tools and features.
  • Research and Data: This team’s mandate is to design and test new technology using research methods and to produce scientifically rigorous knowledge about Wikimedia's users and projects. The team designs and evaluates algorithms, including the development of AI as a service for Product and community developers. They also expand formal research collaborations with academia and industry, leveraging the collaborative insights of researchers and institutions interested in the Wikimedia projects.
• The Community Engagement department also has teams that work directly with community to survey and gather insights, in order to best build programs and services that help support community efforts.
  • Support and Safety: This team provides support on Foundation initiatives with a focus on community consultations, governance, and training. This is the team responsible for major Foundation consultations with the community, such as the Strategy and Annual Plan consultations, as well as the Harassment survey. Insights from this team’s efforts are used to better meet community needs programmatically.
  • Program Capacity and Learning: This team’s mission is to develop a growth and sustainability model for community programs. The model focuses on movement learning, gaining community insights through shared data and partnerships with Wikimedia affiliates in sharing best practices and mobilizing peer learning.
  • Technical Collaboration: This team helps developers to build features in collaboration with our communities. They are organized in two subteams based on primary audiences: Community Liaisons (contributors) and Developer Relations (developers).
• Under the Product department, Community Tech is the team that focuses on the needs of active Wikimedia contributors for improved, expert-focused curation and moderation tools. The creation of the Community Tech team is a direct outcome of requests from core contributors for improved support. This team runs its own annual survey with community, the Community Wish List.

• The audience teams within the Product department are in charge of defining metrics to measure and analyze the impact of new features and products that pertain to their corresponding audience.

More details: Research FAQ

===

About the structure of the plan

===

The annual plan’s programs are displayed by department. For the most part, this structure gave us the most control for developing the programs, goals, and objectives in a manner that follows internal review cycles. However, this means that certain large initiatives, such as the New Readers’ initiative, are spread across multiple departments’ goals. When this occurs, the work with other departments is noted, and the individual programs focus on that department’s involvement and goals for the overall initiative. In future annual planning, we will re-evaluate if this is the best structure, or if there is a way to improve the presentation of cross-departmental initiatives.

==

Community Engagement

==

The Wikimedia community is the core of the movement. Community needs, priorities, and feedback are essential factors informing the Wikimedia Foundation strategy. A primary focus of the Community Engagement department is facilitating community health by ensuring the Wikimedia communities are thriving, that community needs are understood by the Foundation, and that community members have access to critical resources. This year, Community Engagement will contribute to all three strategic priorities: 1) Understand our users to better serve their needs, 2) Increase volunteer retention and engagement, and 3) Increase and diversify contribution of quality knowledge.

Creating supportive, engaged communities is key to our long-term sustainability. The contributors who create and curate free knowledge are the animating force behind the Wikimedia movement, and critical partners to the Wikimedia Foundation. We need to collaborate with contributors to keep the projects healthy, open, and accessible to readers and new volunteers around the world. We want long-time contributors, new volunteers, and institutional partners to have access to the tools and experiences that make engaging with Wikimedia easy and rewarding, and in turn increase the volume and diversity of knowledge on the Wikimedia projects. Community Engagement is the primary conduit to direct conversation with the community and is divided into four teams: Program Capacity & Learning, Support and Safety, Community Resources, and Technical Collaboration. The department focuses on increasing communities’ own capabilities and leadership with better resources, mentorship programs, and program tools. It seeds community programs with millions in grants for community-led projects. It works with product and technology to support communication with communities and help ensure we build the right tools and support resources. It nurtures community health and safety. It offers a conduit for information to readers and community about efforts and accomplishments of movement volunteers and Foundation initiatives. It also seeks to share the word not only about what people are doing to support the movement, but also about what they are learning about effectively doing this work, to share the benefits of their experience.

Collectively, the four teams that comprise Community Engagement positively affect people across the Wikimedia projects. Volunteer retention is essential to the sustainability of our movement, and Community Engagement addresses volunteer support at the points where users frequently decide whether to keep engaging, and for how long. They provide access to resources that strengthen community members’ work, support community members in experimenting with projects that can have short-term and long-term impact, and make the community safer and healthier. In an integral way, the four teams connect the community with the Foundation and connect the community to itself.

Here are highlights of Community Engagement’s goals and targets for FY16-17, which we believe will have positive multiplier effects around the Wikimedia projects and the community at large:

Program 1: Develop community leadership and mentorship

Team: Program Capacity & Learning

Community leaders are an invaluable resource for our websites and the Wikimedia movement. These leaders initiate ideas, contributions, and events – and encourage other contributors – that create new momentum for the movement. Volunteers are essential to the long-term sustainability of the movement, so building better pathways to leadership is critical. To grow content and contributors, following preliminary already active conversations at movement events and planned at Wikimania to define community leadership, we will support the development and recognition of peer mentors in communities – doing this through investment in learning, development, and recognition of regional and thematic program leaders. This will include capacity development and infrastructure support for peer leadership and knowledge sharing with access points defined in consultation with the AffCom to grow peer mentoring for best practices in planning, implementing, and evaluating Wikimedia projects and programs.

Goal: Bolster community leadership development through Peer Leadership Academy

In 2016-17 our team will continue our shift to scalable, train-the trainer style of learning in order to develop community leadership for peer mentoring.

• Objective 1 – Peer leadership development: By the end of FY16-17, support 300+ community leaders’ engagements in direct leadership development activities.
• Objective 2 – Boost peer mentoring engagement: By the end of FY16-17, have community mentors leading mentoring activities with peers (as presenters or peer collaborators) in 80% or more of Wikimedia Foundation sponsored workshops and learning sessions at existing movement events.
• Objective 3 – Scale learning and evaluation teaching and best practices through community leadership: Expand reach through community mentors and provide specific development supports for learning, evaluation, program design and community listening (see more details).

Program 2: Introduce training modules for functionaries and event organizers regarding issues management

Team: Support and Safety.

Introduce a new online training platform and module to help functionaries better manage issues.

Goal 1: Create a training platform for functionaries

Functionary and community governance groups – including stewards, admins, global admins, and Arbitration Committees – play a crucial administrative and editorial role on all our sites, especially in curtailing harassment of volunteers and arbitrating and resolving disputes. To help these functionary and community governance groups better coordinate their work, we will facilitate in the development of a training platform and will guide the establishment of a module based around the critical area of addressing harassment.

• Objective 1 – Survey key groups: In FY16-17, consult with functionaries (stewards, global admins, Arbitration Committees, admins), community members, and outside academic and industry experts to advise on scope, content and delivery choice of the platform – whether it is through Wiki pages/templates or a MediaWiki extension. Then implement and configure the platform with the participation of at least 10 community members.
• Objective 2 – Develop training platform and module on community challenges: In FY16-17, guide the establishment of a new training platform and module on handling harassment that will help functionary and community governance groups deal with community challenges. (Location of modules may vary according to the needs of the functionary groups they will serve, based upon survey of groups impacted, but the modules should be accessible, prominent and open to the appropriate audiences/communities.)
• Objective 3 – Produce translated versions of harassment module: By the end of FY16-17, have the module translated to at least 10 major languages.

More details: After the module’s creation, continue surveying functionaries and community members to determine satisfaction with the platform, the module, and the module-building process. Measure the guides’ success by pageviews and other metrics that will be determined at a later date.

Goal 2: Create a module on the training platform that helps organizers manage our ‘event ban policy’

We are dedicated to creating safe online spaces for users – regardless of gender, gender identity and expression, sex, sexual orientation, disability, physical appearance, race, ethnicity, national origin, age, political affiliation, religion or community status – to meet, interact, learn and collaborate. We are also committed to ensuring our users’ offline experience at Wikipedia events. In 2016-17, we will guide the creation of at least one safety-focused content module on our new training platform, and this module will focus on helping community groups more successfully identify and de-escalate situations before they grow out of control and implement the new event ban policy as a useful tool. That policy establishes guidelines and procedures for identifying and handling users who are banned from Wikimedia Foundation-sponsored or funded events.

• Objective 1 – Survey key groups: In FY16-17, consult organizers (editathon organizers, GLAM partners, etc.) and outside experts, to advise on the best method to deliver and implement the module in FY16-17.
• Objective 2 – Measure success, conduct follow-up surveys: After the module’s creation, continue surveying event organizers to determine their satisfaction with the module, the platform, and the module-building process. Support and Safety will also work with Community Resources to have 100% of events-related grantees take the module.
• Objective 3 – Expand the module's reach: By the end of FY16-17, work with the community to have modules translated to at least 10 major languages.

===

Program 3: Develop capacity-building tools and resources for core Wikimedia programs

===

Team: Program Capacity & Learning

The Program Capacity & Learning Team (PC&L) includes the Education Program, the Wikipedia Library, and Learning & Evaluation. Their work supports the development of community capacity to design and implement core movement programs including Global Education, GLAM, and Wikipedia Library, which connect people to people and people to content. PC&L initiatives help program leaders grow and scale core Wikimedia movement programs, through supporting leaders to share and learn which strategies work and which strategies have failed, and develop effective solutions faster.

====

Goal: Develop program and events dashboard and central Wikimedia resource center

====

Currently, community members must search many pages and places to stay informed about Foundation activities and resources. In collaboration with other teams in Community Engagement and other departments at the Wikimedia Foundation, we will create a single point of reference - the "Wikimedia Resource Center” – to bring important, timely information into one (more easily translated) place. We will also develop a Program and Events dashboard that will allow program leaders to design, deliver, and evaluate programs with ease through semi-automated, supportive tools and infrastructure. The dashboard will provide an easy way to oversee a program (education, writing contests, etc.) with key data, such as participants, articles created, and more. This goal also includes supporting grantees and the FDC decision-making process through improved data management and tools for reporting program outcomes.

• Objective 1 – Create minimum viable product for the programs and events dashboard: By the end of FY16-17, create a Minimum Viable Product of a Programs and Events Dashboard across at least 10 projects or languages (with at least two for emerging communities). The Dashboard will be modeled on the Dashboard that the Wiki Education Foundation uses for its U.S. and Canada courses.
• Objective 2 – Develop a Wikimedia resource center: Develop a Wikimedia Resource Center that allows community leaders to design, deliver and evaluate core programs more efficiently – through semi-automated tools and infrastructure. This resource center project will work to create a single-point-of-entry to various Foundation teams’ existing tools and resources and to bring knowledge exchange systems to a centralized location to reduce searching for shared movement resources.

More details: See here

• Objective 3 – Maintain infrastructure and content supports: Continue to maintain support to curate and develop content for program learning and evaluation as well as other infrastructure supports including the Wikipedia Library Card platform (see more details and existing KPIs).

===

Program 4: Allocate resources to effective community-led projects

===

Team: Community Resources

Allocate resources to effective community-led ideas, programs, technologies and gatherings across the Wikimedia movement by improving the accessibility of Foundation grant programs.

====

Goal: Implement our grants Streamlining Plan

====

Community Resources provides funding and other resources to mission-allied organizations and people around the world, with the goal of increasing the quantity, quality, diversity, and reach of our knowledge sites. In the summer of 2015, we held a community consultation about restructuring WMF grants – and based on what we heard from over 200 people, began making changes to our grants program. In FY16-17 we will complete this changes, resulting in newly structured grants programs that will streamline how potential grantees apply for grants, and how grants are managed. We will endeavor to clarify eligibility requirements, track and share grants budgets spent and note what remains, and seek to coordinate with affiliates who run their own grant programs.

• Objective 1 - Meet community needs during the restructuring transition: In FY16-17, maintain 10 core grantmaking workflows to support 50,000 individuals directly or indirectly per quarter, and with 50% of total grants going to emerging communities.
• Objective 2 - Improve WMF’s support system for grantees: In FY16-17, transition 100% of grantees and committees from 2 existing grant programs (Project and Event Grants, Individual Engagement Grants) to 3 more clearly defined, specialized programs (Project Grants, Rapid Grants, Conference & Travel Support), reducing time between first proposal submission and approval when compared to the old structure (baseline will be established in FY16-17 by analyzing historical data).
• Objective 3 - Evaluate and adapt: Evaluate the outcomes of grants awarded and continue to adapt and improve our systems as we learn. We expect to see a 10% increase in applicant, committee, and grantee satisfaction with support received, against a baseline of 55% indicating experience is above average or excellent, and 21% indicating below average.

===

Program 5: Give more support to GLAM partnerships

===

Team: Program Capacity & Learning

Through the community’s Galleries, Libraries, Archives and Museums (GLAM) initiative, cultural institutions around the world share knowledge of their resources through collaborative projects with experienced Wikipedia editors. More than 100 institutions have participated in the initiative, which will become even more viable with Wikimedia Foundation support. Deepening support of GLAM is one of the ways we hope to achieve our third strategic priority: Increasing and diversifying the contribution of quality knowledge.

====

Goal: Improve access to GLAM knowledge and support

====

We will formalize our support in FY16-17 with tools and programmatic support, technical consultation to GLAM program leaders, and facilitating connections between potential GLAM partners and local communities. By the end of FY16-17, we will improve access to GLAM-Wiki knowledge by facilitating community curation of existing GLAM-Wiki documentation, as demonstrated through user feedback, and integrating the documentation into our new Wikimedia Resource Center.

• Objective 1 - Complete technical consultation: By the end of FY16-17, complete a structured GLAM-Wiki consultation to understand technical needs and develop a plan for resourcing technical support to community leaders and organizations that engage with external partners on GLAM-Wiki initiatives.
• Objective 2 - Develop resources on best practices: By the end of FY16-17, identify existing GLAM-Wiki leadership development strategies, and curriculum within existing GLAM-WIKI communities, and develop “best practices” for training new GLAM-Wiki Leaders within currently unsupported communities, especially communities without affiliate support.
• Objective 3 - Develop and maintain responsive staff support systems: In FY16-17, maintain quick response times and active consultation on community-led GLAM partnerships and grant initiatives (see more details).

===

Program 6: Support Affiliations Committee and affiliate partnerships

===

Team: Program Capacity & Learning

Provide staff support to the Affiliations Committee (AffCom) and affiliate partners. Program Capacity & Learning will work with Wikimedia Foundation affiliates, giving them guidance on applications, learning, and reporting.

====

Goal: Maintain and improve staff support to the Affiliations Committee and affiliate partners

====

In FY16-17, we will improve support to the Affiliations Committee (AffCom), a community-run committee that advises the Wikimedia Foundation Board of Trustees on the recognition and review of movement affiliates such as chapters, thematic organizations, and user groups. We will continue support to WMF annual plan grantees and affiliates on evaluation design and survey strategies.

• Objective 1 - Maintain quick response time: Throughout FY16-17, maintain initial staff review and response time of five business days or less for new affiliate applications to AffCom.
• Objective 2 - Maintain mentoring and consultation support: Throughout FY16-17, maintain mentoring and consultation support for learning and evaluation for annual plan grants including, grantee SMART target consultation, survey and learning supports, proposal review, and technical consultation, review, and development support to program evaluation systems (see mentoring and consultation KPIs)
• Objective 3 - Increase AffCom engagement and support to affiliate partnerships: In FY16-17, work to leverage AffCom as community leaders and mentors along with our existing service to bolster support for Affiliate Partnerships.

More detail: See Support to AffCom and Affiliates.

===

Program 7: Improve collaboration with communities in product development

===

Team: Technical Collaboration

The Technical Collaboration team helps developers build features in collaboration with our communities. We support Foundation’s Product teams, volunteer developers, tech ambassadors, and other contributors who want to get involved in the planning, development, and deployment of Wikimedia software features. We act as liaisons between non-technical communities and developers, and we organize developer outreach programs and events, in order to create software tools and other products to be used by Wikimedia communities.

====

Goal 1: Continue Community liaison support for Foundation Product goals

====

• Objective 1 - Liaise with communities: Throughout FY16-17, when requested – allocate community liaison support for Foundation Product initiatives related to quarterly goals.
• Objective 2 – Participate in audience planning: Throughout FY16-17, participate in the planning process of Foundation Product teams, offering crucial feedback for our Product releases.
• Objective 3 – Facilitate all major product conversations: Throughout FY16-17, facilitate in and – when appropriate – moderate all major conversations involving Wikimedia communities and WMF Product teams.

====

Goal 2: Create a systematic approach to community engagement for product development teams

====

In 2016/17, the Technical Collaboration team will support the Foundation in its commitment to engage the community earlier and throughout the product development process, through systematic communication, discussion, and decisions.

• Objective 1 – Initiate a guideline for technical collaboration between WMF teams and the communities: By the end of FY16-17, in collaboration with communities, initiate a “Technical Collaboration Guideline” that allows Product teams and Wikimedia communities to work together in a systematic way by establishing best practices for community involvement in the product development and deployment cycle.
• Objective 2 – Facilitate wide adoption of the community engagement guideline: By the end of FY16-17, work to have all Foundation Product teams and a majority of the top 20 most-active Wikimedia projects integrate their technical decision processes with the community engagement guideline, as evidenced by community decisions and requests, as well as their processing by WMF teams.
• Objective 3 – Integrate community engagement more closely with early Foundation product development stages: By the end of FY16-17, work to integrate community engagement more closely into the pre-release stages of product development, when Product researches, conceives, and plans a new release. In parallel, decrease the frequency of major discussions associated with the Release stage of a product.

===

Program 8: Connect volunteer developer work with community technical needs

===

Team: Technical Collaboration

====

Goal: Connect free software developers with the 2015 Community Wishlist Survey maintained by the Community Tech team

====

In the fall of 2015, the Foundation invited contributors to submit proposals for what the Community Tech team should do to improve or produce curation and moderation tools for active contributors. That wishlist provides a jumping-off point for the efforts of the Foundation Technical Collaboration team.

• Objective 1 – Encourage volunteer focus on addressing community priorities: By the end of FY16-17, work with volunteer developers to complete 10 technical community requests that have strong demand.
  
  
• Objective 2 – Encourage hackathon and outreach work into community requests: By the end of FY16-17, help Foundation hackathons and outreach programs, such as Google Summer of Code, to increase their impact by focusing their work toward popular community requests.
• Objective 3 – Better connect developers with tasks and mentors: By the end of FY16-17, improve the ability of new volunteer developers to find useful tasks and mentors easily, increasing the focus on deploying useful features. Progress will be measured with a community health survey for Wikimedia technical spaces.

===

Program 9: Identify support gaps and provide targeted resources

===

Team: Community Resources

====

Goal: Proactively identify gaps and provide targeted resources to communities to address those gaps

====

(e.g., addressing systemic bias, harassment, reach, and support to emerging communities)

• Objective 1 – Source new ideas: Run two Inspire campaigns per year through IdeaLab to source ideas focused on strategic themes, resulting in 100 ideas from 200 participants and 10 grant proposals per campaign.
• Objective 2 – Improve community capacities through pilot programs: Pilot, evaluate, and grow the most effective strategies for improving the capacity of 10 communities with low awareness and usage defined in the Community Capacity Development Project. Pilots will need to demonstrate significant capacity improvement compared to a baseline, where each baseline will be defined for each pilot (e.g., Tamil technical skills pilot will see a 10% increase in number of community members engaging in technical work; Brazilian community will form a media response team).

===

Program 10: Maintain quick public response time and expand community surveys

===

Teams: Support and Safety (Goal 1) Program Capacity & Learning (Goal 2)

Continue responding rapidly to public questions around safety and support, while broadening WMF’s surveys to better understand the community’s needs.

====

Goal 1: Respond efficiently and effectively in workflows

====

Support and Safety (SuSa) supports the Foundation, communities and public through community consultations, governance, training, public-WMF correspondence management, executive staff and functionary support, and legal team support. More specific details about the team’s core work can be read at Support and Safety#What we do. Rapid review and appropriate response to enquiries and effective engagement with staff, community, and the public ensures that its work is carried out at a high level.

• Objective 1 – Maintain rapid response time: During FY16-17, maintain a two-day initial response time (outside of weekends and staff holidays) to email requests about WMF initiatives through the answers@ and business@ systems. We expect around 1,000 requests in the year.
• Objective 2 – Conduct follow-up surveys: Ensure that Support and Safety’s work is effective and useful, the team will survey affected groups to determine how satisfied they are with our help.

More details: Throughout the year, Support and Safety will among other core duties support the Wikimedia Foundation’s non-engineering staff in meeting its community-facing questions and needs and support the Executive Director in engaging with the global community, handing complicated correspondence, and emerging issues. Support and Safety will liaise with key community groups, such as the Ombudsman Committee, Stewards, and Arbitration Committees and will work with the Wikimedia Foundation’s Legal team on public requests for such actions as copyright takedowns, requested investigations, and community support. The Support and Safety team has a history of ad hoc survey of groups served to ensure that it is effectively and usefully liaising with these groups, both internal and external, but will create a more systematic and regular system of surveying the teams with which they work to ensure that resourcing is effective.

====

Goal 2: Support Foundation efforts to understand community needs

====

The Program Capacity & Learning team supports the use of listening tools to learn about the needs and ideas of audiences and stakeholders. Examples of listening tools are surveys, community consultations, conference sessions, and participatory budgeting (e.g., Community Wishlist, Inspire campaign). In this way, the team builds capacity for decision-making practices that are engaging, data-driven, and collaborative. (more details)

• Objective 1 – Implement Community Engagement Insights: In FY 2016-17, develop Community Engagement Insights – surveys of communities that will measure Foundation performance and gather community needs. Community Engagement Insights aims to increase Foundation understanding of communities needs and confidence in decisions for next year's annual planning. The usefulness and success of the survey will be measured using pre-post surveys. More specifically, the Learning and Evaluation team members are working to develop a coordinated system for surveys that gather information and input from different communities the WMF serves. The plan will include quarterly and annual surveys which will be coordinated across teams and include identified accountability goals and measures. These surveys will inform annual planning for the following fiscal year. Note that *survey support* to communities actually falls under Program 1, Objective 3, as part of building leadership capacity as outlined in our supplemental plan's logic models

===

Program 11: Protect our users, staff, and public

===

Team: Support and Safety

Continue protecting the wellbeing of our users, staff, and the public as they engage with our sites and at Foundation-supported events.

====

Goal: Maintain rapid response time and effectively resolve issues

====

In FY16-17 Support & Safety will maintain staffing support for threats to the safety of people and the projects, including immediate threats to life, limb or property; threats to child safety; inappropriate images; user investigations such as for global or event bans; and inquiries from law enforcement. We will coordinate this work as appropriate with Legal staffing, event organizers, and law enforcement and related entities, including the United States’ Federal Bureau of Investigation, the National Center for Missing and Exploited Children, and the Secret Service.

• Objective 1 - Maintain emergency response time: During FY16-17, maintain a three-hour initial response time to emergency requests made through our emergency@ inbox. These emergencies include threats to life, limb or property made on our projects or at affiliated events.
• Objective 2 – Maintain non-emergency response time: Create an appropriate mechanism to track non-emergency safety inquiries coming through other inboxes (ca@, individual inboxes) and ensure a two-day initial response time (outside of weekends and staff holidays).

Product

About Product

Our user-centered approach

The Product department, alongside the community, builds, improves and maintains the user facing features on all the Wikimedia projects. The software, interfaces, apps, and other systems and applications the team supports are essential means by which contributors and readers connect with our sites. The work of the team’s three “audience” groupings – Discovery, Reading, and Editing – is interrelated and enables a channel for progressive engagement with the users of the Wikimedia projects.

In the past year, we have begun to engage in a more user-centered approach. This discipline ensures that we do initial research to better understand our users’ needs, then we prototype and iterate to build quality products and functionality that better meet our users’ needs. To do this, we partner with the Technology department, specifically the Research group, that includes the Design Research team and the Research and Data team, so that we can deliver scalable, reliable experiences to our users leveraging innovative technology and research.

====

What we do

====

Hundreds of millions of people come to our projects to find information. We’re making this experience significantly easier – and much more efficient. From discovering the information they are looking for, users read articles and engage with other information – millions of pages that explain the world that we live in. A portion of these millions of readers decide to go further and become contribute to our projects – write and edit articles that need expanding, add media that gives context to words, make suggestions of other editors. Discover. Read. Edit. This is the pathway of engagement that Product’s Discovery, Reading, and Editing teams are committed to maintaining and improving in the 2016-17 fiscal year. Their work will be complemented by Product’s Community Tech team, which supports editors with key technical tools, prioritized through consultation and community discussion.

The progression that drives Product’s work can be visualized this way:

====

Our focus for FY16-17

====

In FY16-17, Product will maintain the essential underpinnings while making them better – exposing more cross-project content through efforts in Discovery, creating better reading experiences through the Reading team, and improving the experience of contributing to our sites through the Editing team. Our work in FY2016 - 2017 will continue to support critical features (APIs, parsers, editing tools, etc.) while experimenting on new ways to support our strategic priorities. These could include new designs, new interfaces, and new approaches to encourage more people to read, edit, and discover knowledge through our projects. Throughout our product development process we will work with Community Engagement to ensure that these activities involve community consultation and co-operation.

Product is doing all this amid a changing landscape: Editing on the projects is plateauing, readers increasingly reach us via mobile devices, structured data is more important than ever. At the same time, we must continue to invest in the core tools that encourage and empower readers and contributors to come back again and again. (See Current Trends - Feb. 2016 for more information.)

The following top Product FY2016-2017 programs and goals are intended to increase our understanding of our users, so that we can better anticipate and serve their needs. Ultimately, we believe these efforts will increase reader and contributor retention and engagement, and increase and diversify the knowledge contained in the Wikimedia projects. These efforts are cutting across Product’s work in FY16-17.

===

Program 1: Increase engagement and retention by employing user-centered design

===

To best serve our readers and contributors, the Product team has been integrating a user-centric design approach into its product development process. More simply put, this means that we are conducting user research before we begin work, and then we are prototyping and iterating to ensure we are delivering the most useful products and features. Because the efforts are designed with the input from actual readers and contributors, we can more effectively meet their needs.

The Design Research team works hand-in-hand with the Product teams, to ensure that all product programs are built with a focus on the end-user. The team conducts generative design research to gain more knowledge about our broad set of users and their unmet needs, informing what products to build for users and why. For example, this includes the ongoing persona research as well as user research to discover unmet needs and behaviors of current users. The product team then uses this information to build features that better meet how people want to use our projects.

Team: Discovery, Reading, and Editing

====

Goal 1: Use research-centered approach to drive product development

====

By employing a sound discipline of user-centered design in all our product development, we will better meet our users’ needs. This goal is directly linked to our first strategic priority: understand our users to better serve their needs, in order to effectively engage and retain both readers and contributors. It also provides insight into what triggers people to move from reading to contributing and highlights blockers to contribution.

The Foundation has already built capabilities around user research in the product audiences in the current fiscal year, and this program reflects the continuing impact of user focus across product development. This goal will have a high degree of collaboration with the Design Research team in the Technology group.

• Objective 1 – Improve how readers and editors interact with content by applying research during product development: Throughout the year, use a variety of generative and evaluative research methods across the product audiences to deepen our understanding of user behavior and the success of our solutions in addressing our goals. These methods include usability testing, concept evaluation, user segmentation, design ethnography (generative research), benchmarking, heuristic evaluations, surveys, and community engagement and feedback. We will apply these methods as appropriate to each project and continue to expand these capabilities across the product organization.
• Objective 2 – Summarize, process, and apply output of New Readers research project: In FY15-16, we are performing ethnographic research in three countries under-served by Wikimedia projects: Mexico, Nigeria, and India. Synthesize this research and share it with product teams and the community in FY16-17 as a core component of the project.

More detail: A detailed explanation of this research and how it fits into the New Readers project itself is in this FAQ including research and analysis done on these projects to date, New Readers FAQ

===

Program 2: Maintain and improve content discovery

===

Team: Discovery

====

Goal 1: Maintain key search functions and enhance capacity

====

This goal supports the primary mechanism that readers, editors, and third parties use to find our movement’s content. It continues our existing commitments for all public-facing interfaces and increases required for organic growth.

• Objective 1 – Maintain search APIs: Throughout the year, maintain support of all the Application Programming Interfaces (open search, prefix search, full text search, “more like,” etc.) that users rely on to find knowledge on our sites. As measured by search-return times, maintain: a 1.1-second-or-less return time for 99 percent of prefix search/open searches; a 4-second-or-less return time for 99 percent of full-text searches; a 2-second-or-less return time for 99 percent of “more like” searches; and a 2-second-or-less return time for 99 percent of geo-data searches. During the next year, we expect users to make more than 1.6 billion search queries through these APIs, which provide direct, high-level access to the content in our websites. This will continue to support our existing large API consumers, including our own like the Wikipedia Android and iOS apps.
• Objective 2 – Increase server capacity: By the end of FY16-17, upgrade Wikimedia’s existing Elastic Search infrastructure to 36 servers in Virginia and 36 servers in Dallas, from the current infrastructure of 29 and 24, respectively. Increase WikiDataQuery (WDQS) service server capacity to 4, from the current infrastructure of 2. These increases will allow for organic growth and maintenance of SLA’s for desktop, mobile, app, and API users.

====

Goal 2: Improve search on Wikimedia projects

====

Our goal is to help users more quickly find relevant content within our projects so that the Foundation can better meet the needs of users. Our efforts will be based on quantitative user and feature testing.

• Objective 1 – Improve search interfaces: By the end of FY16-17, significantly improve users’ search engagement of on-wiki search results by evolving the user interface to include imagery and metadata. This follows improvements that were made in 2015-2016, including the “completion suggester” that rolled out in March 2016 and gives users more relevant as-you-type suggestions on content.
• Objective 2 – Increase relevancy of search results: By the end of FY16-17, improve our search result relevancy by incorporating new methods that affect result ranking, surface cross-project, cross-language results, and explore improving Commons media search through structured data in partnership with WMDE. These efforts will allow people to discover relevant content more easily on the Wikimedia projects, and better expose content across the projects to encourage broader participation.

====

Goal 3: Evolve content discovery and interactive tools on Wikimedia projects

====

Work on these tools helps WMF with two of its strategic priorities, by increasing and diversifying knowledge and forms of presentation and by increasing volunteer retention and engagement through new opportunities for curation and creation.

• Objective 1 – Launch maps service: By the end of FY16-17, launch maps service for Wikipedia, which will allow users to discovery content visually, allow for map creation and increased user engagement. Maps server count will be increased by 8 from the current infrastructure of 4 to support launch. The initial target is to track basic usage statistics, e.g. count of articles with maps, interactions, and map link clicks. Once we begin to collect data, our next goal is to track "stories" - e.g. Maps Analytics (WIP).
• Objective 2 - Connect Wikimedia projects: Create improved ways for our community to interlink interactive content across projects, allowing for easier content discovery and syndication. Products under discussion include Graphs, improvements to WDQS, and partnerships with Reading and Editing. While Graphs work has not been prioritized by Discovery, we hope to start tracking basic usage statistics [current tracking only includes the approximate number of users who saw our maps and how much usage they have done (average tiles per user)].

More detail: For more information about the Discovery team's 2016-17 work, see here.

===

Program 3: Increase our global reach by increasing readership

===

Teams: Reading. Strategic Background

The mission of the Wikimedia Foundation is to empower and engage people around the world to collect and develop educational content under or in the public domain, and to disseminate it effectively and globally. Beyond maintaining core functionality, for FY16-17 we will focus our resources on where we will have the most impact as guided by our mission: 1) increasing retention by improving reader experience with our encyclopedias, 2) engaging new readers in an under-served geography, and 3) deepening engagement across our projects.

====

Goal 1: Maintain core readership functions and services

====

Readers access Wikipedia content hundreds of millions of times a day, and we need to ensure that experiences are fast and reliable. This goal demonstrates our commitment to maintaining our core Reading experiences as a first priority.

• Objective 1 – Maintain current websites: Maintain the mobile and desktop websites, and APIs, as well as 29 community and Foundation extensions that are used across our sites. During the year, we expect readers to view more than 200 billion page views and 100 billion API requests through our sites and APIs.
• Objective 2 – Maintain apps: Millions of readers rely on the apps to engage with Wikipedia. Since first being introduced in September 2012, we have seen 30 million downloads for our iOS app and Android app. Throughout the year, maintain and update both platforms.

====

Goal 2: Improve the encyclopedia experience

====

For our established audiences, we want to increase retention by improving the presentation of and engagement with encyclopedic content in our current web and app experiences, while retaining the integrity of the fundamental encyclopedia model.

• Objective 1 – Increase retention across our reading experiences: By the end of FY16-17, release new versions of our apps and web experiences with features designed to increase user retention. This will include content notifications, which we anticipate will lead to an increase in sustained return visits. Other features under consideration include an article scoring tool (possibly based on ORES) and article profiles that make it easier to discover new content. We expect to have at least 2 releases per platform in FY16-17. Our goal is to increase our retention by 5% across all of our platforms.
• Objective 2 – Improve article rendering: By the end of FY16-17, improve mobile article rendering for the Web, which will give users a more engaging and polished presentation of articles. This will contribute to the goal of increasing retention by 5% on the web platform.
• Objective 3 – Integrate Wikidata: On both the mobile site and the Wikipedia native apps, experiment with using Wikidata to enhance the reading experience – using Wikidata short descriptors in search and article titles to help readers get more context at a glance, as well as building infoboxes from Wikidata to provide a better formatted quick fact lookup experience.

====

Goal 3: Launch the New Readers project

====

The economically less developed regions of the world have 85% of the world’s population, less than 60% of mobile subscriptions, and only 30% of our page views. There is a clear opportunity for the Foundation to further our mission by reaching new Readers in these geographies.

• Objective 1 – Launch one new experience directed at new readers: The Reading team will, in co-operation with Communications, Community, Partnerships and Design Research, launch one new experience for a specific geography during FY16-17. The specifications, target markets and features will be developed through on work around the Product Program 1 (Better understand our users) ongoing in FY15-16 and into FY16-17. We anticipate it will include performance and language switching optimizations, among other features. By the end of FY16-17, the Wikimedia Foundation wants – with the help of Product Audience teams – to increase our overall reach by a collective 5% by targeting high-potential regions around the world.

More detail: New Readers

====

Goal 4: Foster a community of readers

====

This initiative is intended to test the hypothesis is that there is a wide swathe of readers who are more than casual browsers, but not full encyclopedia article writers, who would like to better interact with knowledge on Wikimedia. The hypothesis will be evaluated by prototyping new Wikipedia experiences based on interactions with content and other users. We plan to explore curation tasks within this initiative, while being very sensitive to moderation issues at all times.

This initiative is intended to increase reader engagement by creating new Wikipedia experiences based on interactions with content and other users. The community of readers hypothesis is that there is a wide swathe of readers who are more than casual browsers, but not full encyclopedia article writers, who would like to better interact with knowledge on Wikimedia. We plan to explore curation tasks within this initiative, while being very sensitive to moderation issues at all times.

• : More detail: Reading strategy - community of readers

• Objective 1 – Increase engagement across our reading experiences: By the end of FY16-17, research and release interactive Wikipedia reader-oriented features across all our platforms (Web, Apps) in co-operation and consultation with the community. Possible features include micro-contribution/interaction and curation experimentation and notifications. We expect to have at least 2 releases per platform in FY16-17. Our target is to increase our engagement by 5% on the Android platform, leveraging learnings from the investigation of the core hypothesis.

===

Program 4: Maintain and improve content creation and editing tools

===

Team: Editing

====

Goal 1: Maintain and incrementally improve current content creation and curation interfaces

====

Besides maintaining core functionality for the movement, this goal helps WMF move forward its strategic priority: Increase and diversify contribution of quality knowledge by making the tools easier to use.

• Objective 1 – Strengthen interfaces: Throughout the year, maintain and incrementally improve content creation and curation interfaces. These interfaces, such as that of the visual editor, give contributors the ability to easily and efficiently contribute writing, photos, and other content to our websites. Our work on a unified, consistent editing interface between the mobile and desktop Web experiences, and between visual and wikitext editors, will strengthen editing for new and existing users alike. In support of these changes, we will unify around a single Wikitext parser for both reading and editing.
• Objective 2 – Modify and improve curation tools: Throughout the year, iterate modifications and improvements to core curation tools, like edit, diff and history pages, in order to allow contributors to more easily and efficiently manage contributions – both their own and those of others.
• Objective 3 – Guiding edits: We will experiment in the visual and wikitext editors with different ways to suggest to users things they can do to make better, more constructive edits as they make them. This work is aimed at reducing the burden on experienced users when they review new editors' changes. We also intend for these experiments to improve the "on-boarding" experience for new users, helping them learn what is wanted and valued by their wiki's community.

====

Goal 2: Improve editing experience by reducing technical debt

====

By reducing technical debt of improving tools and features, we position communities and the Foundation to more effectively meet our strategic priority: increase and diversify contribution of knowledge. Throughout the year, clean up and simplify the extensions and libraries that power editing features. These features are central to the work of volunteers and development teams, and the improvements will make editing work more efficient and effective for both groups.

• Objective 1 – Improve the wikitext format:We will modernize the wikitext format to be more powerful and predictable, using a robust testing system to guide our work. This will include minor syntax changes and improved templates, making them simpler by restricting the technical impact on the output of the page.
• Objective 2 – Expand the core of MediaWiki to support new kinds of content: By the end of FY16-17, add support in MediaWiki for pages and revisions capable of storing multiple types of content simultaneously. For example, each revision of a video description page will encapsulate the state of the video, its subtitles, its metadata, the text of the description page and the associated wiki metadata such as protection levels at that particular time. This will help existing contributor workflows and allow us to provide powerful new kinds of content. This objective is part of the work led by Wikimedia Deutschland in providing structured data about media files on Commons linked to Wikidata.
• Objective 3 – Streamline metadata editing: Throughout the year, simplify the editing of page metadata, such as page titles, protection levels, incoming redirects and other information, in order to allow contributors to more easily and efficiently manage contributions – both their own and those of others.

====

Goal 3: Invest in new types of content creation, curation and collaboration tools

====

This goal is critical to our vision of every single human being freely sharing in knowledge. By offering better translation tools, we can move forward two key strategic priorities: 1) Increase volunteer retention and engagement, and 2) Increase and diversify contribution of quality knowledge.

• Objective 1 – Expand the Content Translation Tool: By the end of FY16-17, roll out the Content Translation tool to all users on desktop. Also make a content Translation tool prototype for mobile devices. The tool has been in beta mode for desktop users since we first introduced it in January 2015, and has led to more than 50,000 new articles.

===

Program 5: Maintain and build contributor tools

===

Team: Community Tech

The Foundation’s third strategic priority is to increase and diversify knowledge by developing high-priority curation and creation tools for user needs. The Community Tech team’s focus is to build or improve tools for the most active wiki contributors, as prioritized by the community.

====

Goal 1: Community Wishlist: Build and maintain tools used by the most active contributors to our projects

====

In late 2015, the Community Tech team conducted WMF’s first Community Wishlist Survey, inviting active contributors from all projects and languages to submit proposals for features and fixes that they’d like to see addressed. Once the proposals were collected, the contributors voted on the projects that they’d like to see Community Tech take on. The top 10 community “wishes” became the team’s backlog of projects to investigate and address.

More detail: Community Wishlist survey process

• Objective 1 - Top 10 wishes: In 2016, the team is responsible for investigating and addressing the top 10 wishes from the 2015 survey, including:
• A multi-language bot that identifies dead external links, and directs those links to an archived version, running on English Wikipedia with internationalization planned
• A new pageview stats tool to replace stats.grok.se, live on all wikis
• Cross-wiki watchlists, planned for a beta feature
• Fixing numerical sorting in categories, rolled out to all wikis
• Improvement of plagiarism detection tools on English Wikipedia, with a more accessible and effective interface on Tool Labs
• Assisting Wikidata with building structured data on Commons, in response to a wish for translated category names

More detail on timelines and targets: Community Tech

====

Goal 2: Tool labs support

====

Working with volunteer developers is an important part of Community Tech’s work. Popular contribution tools and bots become de facto production software needed to keep the wikis healthy and happy, but when a tool has a single maintainer, there’s a high risk that it will be abandoned. To mitigate against this risk, the team will improve Wikimedia Tool Labs as a center for volunteer development support, including a framework of best practices and communication, allowing projects to grow beyond what can be accomplished by a single motivated individual. This speaks directly to our strategic priority to increase volunteer retention and engagement.

• Objective 1 - Improve documentation and support: Help organize groups to work on infrastructure, documentation, and support needed for bots and tools.
  

More details: Community Tech/Tool Labs support

====

Goal 3: Represent both large and small communities through the Community Wishlist

====

The Community Wishlist has been well received with more than 600 people participating. However, we did identify one issue with the 2015 survey, which was that the support-voting process privileged larger projects. While the Wikisource communities were a strong presence in the 2015 survey, especially considering their relative size, but they couldn’t muster enough votes for any of their proposals to break into the top 10. The process needs to allow both large and small communities to be heard.

• Objective 1 – Conduct a modified community wishlist: Modify the 2016 survey process to include some carve-out space for smaller projects, to which a portion of developer time would be allocated. Conduct the new survey by December 2016 to gather a new set of proposals from the communities.

==

Technology

==

The technology department supports global access to the Wikimedia projects that is reliable, fast, and secure. This team supports performance, availability, development infrastructure, technical operations, security, architecture, release management, analytics engineering and Research. One of the larger teams, they support most of the core operations to make sure our projects, services and development pathways are available to as many people as possible, on as many devices as possible, in a manner that safeguards users’ privacy and trust.

We support progress by providing tooling and infrastructure that make it possible for product developers to enhance and augment the capabilities of our software. We create pathways for creative and motivated individuals to translate their ideas into working software that is reliable, easy-to-use, secure, and scalable.

We work closely with the Product team to support ongoing initiatives and cover development dependencies. We provide counsel by assisting product teams and other units within the organization and the movement to make good choices on technology by assessing costs, analyzing usability, anticipating failures, evaluating privacy, reviewing security, projecting impact, and suggesting alternatives.

We also work with the Product audiences providing research before new products or features are built. We conduct, enable, and review research to validate and iterate on concepts, to ensure usability and that products are built around users’ needs. We conduct research and explore services so that we can surface the best ways to end barriers to contribution. We use formal collaborations with industry and academia to scale efforts of the organization.

Tracking performance targets is a new discipline for our team. In FY16-17, we will be establishing baselines so that we can more accurately make predictions and measure performance increases in future annual planning. We will also develop a roadmap to show which projects will be completed each quarter.

===

Program 1: Improve tools that help us understand user needs

===

Team: Analytics

The Analytics Team is focused on making Wikimedia related data available for querying and analysis to both WMF and the different Wiki communities and stakeholders. We develop infrastructure so all our users, both within the Foundation as within the different communities, can access data in a self-service fashion that is consistent with the values of the movement. This ties directly into the first strategic priority, to understand our users to better serve their needs. In the past, this has been difficult to accomplish, due to lack of proper infrastructure for computation (cluster) and serving data (APIs).

====

Goal: Build the infrastructure and capacity to better understand our users’ online interactions with our projects and more quickly respond their needs

====

Currently, the Foundation has limited capacity to understand what users as a whole are doing with the projects, where they are experiencing problems, and what would best facilitate easier reading and editing. By focusing efforts on improving our querying and analysis tools, services and systems so all our users, both within the Foundation and the different communities, can access data. This will help us better serve readers’ and editors’ needs.

More detail on all projects: Analytics projects

• Objective 1 – Improve tools for data display for the Foundation and community: By the end of FY16-17, make tools more efficiently display overview data about editing and pageviews of the Wikimedia projects, so that the Foundation and the community can monitor the sites, understand what is happening on an overall level, and develop insights without having to use a query interface. This will involve deploying a new storage for data tailored for easier access.

Note: Baseline data unavailable; it will be established, and then progress will be measured as part of this objective.

• Objective 2 – Improve data computing and release processes: By the end of FY16-17, improve computing and dataset creation processes so that more actionable data can be released to the community, and make improvements that save storage space and therefore reduce costs. This will improve the response times of Pageview APIs (median < 1 sec), bot detection on Pageview API datasets, and release of new datasets to community.
• Objective 3 – Real-time data processing: By the end of FY16-17, build a platform that will enable real-time data processing of what’s trending for pageview articles, save network storage capacity, and reduce costs of the infrastructure. This potentially will lead to new tools and services for the community and Foundation.
• Objective 4 – Build compatibility between key databases: By the end of FY16-17, improve compatibility among key databases, allowing users to query them in ways that will provide more distinct information about users’ interactions with the Wikimedia sites. Target: Tooling available to query data in hadoop that used to be on MySQL.

More details: No longer limited by resource constraints in MySQL. Frees DBA time as it removes one big piece of work our only DBA needs to attend to now. Teams benefit from being able to join distinct data sources (hadoop and mediawiki database). Such a pipeline does not exist today.

===

Program 2: Expand research capabilities to equip product development to better meet users’ needs

===

Teams: Research and Data, Technical Operations, Design Research (see objective) The scientists and UX researchers on the Foundation Research team use data to understand and empower the millions of readers and contributors who interact with the Wikimedia projects on a daily basis. We turn research questions into publicly shared knowledge, design and test new technology, produce empirical insights to support product and engineering decisions, and publish research informing the organization’s and the movement’s strategy. We are strongly committed to principles of transparency, privacy, and collaboration; we use free and open source technology and we collaborate with researchers in the industry and academia.

====

Goal 1: Build an open infrastructure to increase the volume, quality, and reproducibility of research on Wikimedia projects

====

In FY15-16 the Research team delivered a number of projects to support volunteers performing content curation and content creation. Revision scoring as a service brought to Wikimedians an easy way to automatically assess the quality of articles and individual revisions via a set of open APIs, currently available in 16 languages/projects. Article recommendations showed they have the potential to triple the content creation rate while maintaining the same level of quality as organically created articles and have since been integrated into the Content Translation tool. In FY16-17 we will expand these efforts on research infrastructure that supports Wikimedia communities.

• Objective 1 – Understand the editing culture: By the end of FY16-17, conduct research that builds on previous studies of newcomer socialization and mentorship. Focus on editors and how to increase their ability to work more effectively with projects. Analyze the effects of harassment and disrespectful behavior, to better understand how they affect the retention of new contributors and to eliminate barriers to contribution. (Research and Data team)
• Objective 2 – Evaluate AI as a service to help volunteers improve quality: Throughout FY16-17, continue efforts to design and evaluate services making artificial intelligence available as a service to volunteers and tool developers. Expand revision scoring as a service to make scores and quality assessments readily available to our communities via open APIs. Design and test recommender systems to support community initiatives such as edit-a-thons and outreach events and allow volunteers to easily identify tasks and areas in need of quality improvement or contributions. (Research and Data team)
• Objective 3 Create an open research infrastructure: Throughout FY16-17, create an open notebook infrastructure using state-of-the art technology that will consolidate research onto one platform to increase access and accelerate our ability to work collaboratively. Work in collaboration with partner organizations and academic programs to spearhead the adoption of this infrastructure among students and collaborators. (Research and Data team, Technical Operations team)

====

Goal 2: Expand the Foundation’s research capacity by partnering with researchers in industry and academia

====

In FY15-16 we developed an Open Access policy to simplify how we collaborate with researchers and to ensure that the output of these collaborations be made immediately available under open licenses, consistently with our mission. Some of our most successful projects this year are the result of formal collaborations. In FY16-17 we plan to expand the Research team’s capacity via short-term internships and formal collaborations with industry and academia, under the terms this policy, to reduce the overall cost for the organization to conduct research projects.

• Objective 1 – Expand academic research outreach: Aim to achieve a stronger academic presence by submitting the output of our work to key conferences in the field and by organizing an annual research workshop. These efforts will help us align the interests of the academic community to issues of strategic importance for the movement. Targets: 4 Papers submitted and accepted in peer reviewed conference proceedings in the fiscal year; 40 Works submitted and accepted by researchers attending annual workshops. (Research and Data team)
• Objective 2 – Initiate formal research collaborations: Set up three new collaborations with external research teams to address critical, under-resourced areas. Targets: FY 2016-17 Q2-Q4. (Research and Data team)

More details: Formal collaborations

====

Goal 3: Perform evaluative design research to iterate concepts and designs focusing on usability and solving problems and unmet needs for users

====

Our goal is to help the organization validate and iterate design concepts, to ensure usability and products being built around the needs of users. We employ usability testing, concept testing, surveys and co-design with users, and collaborate with product teams toward these ends.

• Objective 1 – Conduct evaluative design research: Continue to collaborate with the Foundation teams and Communities toward building user-facing functionality around the needs of users and contributors. Iterate features and functionality toward usability and utility. Target: 15 evaluative research projects in FY16-17. (Design Research team)
• Objective 2 – Analyze and apply generative research for new readers: Analyze and synthesize data collected in three generative, qualitative research studies for new readers in India, Nigeria, and Mexico. This work will inform how we can best support online learning in these regions, and invite more readers to Wikis. (Design Research team)
• Objective 3 – Expand capacity for standardized iterative user testing: Adopt and implement user testing tools that enable lightweight, iterative evaluation of the usefulness and usability of WMF products over time against pre-defined benchmarks. The first step towards this goal is to deploy tools that facilitates remote, unmoderated testing of mobile and desktop platforms in addition to moderated user testing of the desktop interface. New tools will allow us to efficiently test WMF software with more representative users in real-life contexts, and provide a set of baselines for future benchmarking. This work will contribute information to product teams for deciding which areas are most important to put effort toward. Targets: First two quarters of FY 16-17. (Design Research team)

====

Goal 4: Improve communications and access of all research projects, so that institutional knowledge is easily shared and applied

====

Currently, research, data analytics, and community surveys are conducted by different departments of the whole Foundation. This structure was intentionally built to ensure better integration and responsiveness of key personnel to serve specific projects. However, this structure makes it challenging to share information across teams and effectively with the community. By improving how we communicate and organize this information, institutional knowledge can be more effectively applied.

• Objective 1 – Create a Research minisite that would act as a landing page for all resources related to research at the organization: Potentially by end of Q1, build a centralized location for storage of research projects, with a primary focus on the two teams in the Research department: Research & Data and Design Research.

More details: Research’s quarterly goals; a complete list of ongoing projects, cross-linked with Phabricator and organized by quarter; and a list of our current formal collaborations and documentation on how they are set up.

• Objective 2 – Strengthen research communications across teams and to the community: Employ a variety of methods to ensure that our understanding of users is communicated across the product organization and the community and is used to qualify product decisions and prioritization. Deliverables will include problem definition, personas, research findings (presentations and reports), demographic analysis and user segmentation, and quantitative usage data. A schedule of deliverables will be determined during Q1 and then posted.

===

Program 3: Improve site reliability

===

Teams: Technical Operations, Security, Architecture, Technology Services (see objective)

====

Goal 1: Keep Wikimedia's sites and services running responsibly, reliably, and securely, including protection against and response to outages, data loss, and breaches

====

As one of the world’s most popular websites , Wikimedia must vigilantly secure our content and protect the privacy of our millions of users. We do this by ensuring operational and software production security, through governance, and by working with our communities.

• Objective 1 – Increase operational excellence: By the end of FY16-17, increase resilience, responsiveness, and security so all Wikimedia sites and services are running > 99.97% of the time. Also reduce technical debt (projects not completed in FY15-16) and provide more operational support to the rest of Product and Technology. (Technical Operations)
• Objective 2 – Improve software security: Improve security throughout the Foundation software development life cycle. This will include static, dynamic, and manual security testing for deployed software; triage for reported security bugs, and assistance to teams addressing them. Run audit of our systems and reduce the number of exploitable vulnerabilities on Foundation-run sites, better protecting private data and reducing the risk of our site being unavailable due to denial of service attacks. Targets: For security purposes, specific targets and improvement measures of bugs, attacks, and incidents are not shared publicly. (Security team)
• Objective 3 – Improve the security capabilities of the Foundation engineering teams: By the end of FY16-17, improve the security capabilities of engineering teams throughout the Foundation. Teams will understand their risk exposure, have a plan to address priority issues, and have the capability to execute the plan with help from the Security team. By improving teams' ability to prevent, detect, and respond to security issues, we will empower teams to protect the Foundation's assets. (Security team)
• Objective 4 – Improve privacy protection: By the end of FY16-17, begin implementing the planned Privacy Roadmap, as well as design privacy into the projects driven by our strategy. All staff will be given adequate training and resources to ensure the safety of their individual systems and accounts. Systems and data repositories will fully comply with applicable privacy policies and regulations. Access to any private or sensitive data will be governed by an appropriate data-access policy. Target: Ongoing throughout FY16-17 with some mapping and process deliverables in Q3. (Security team)

====

Goal 2: Overhaul legacy systems to provide an open structure that supports customization and new editor features

====

Many of our sites were built 10-15 years ago as closed systems. These legacy architectures limit our ability to build new features and tools and to make major performance improvements. By updating our systems using current technologies, we will be able to produce a better experience for both readers and editors, including the ability to experiment and adapt the look/feel, functionality, and tools available, as well as improved performance. This is essential underlying work to support our strategic priority of providing better contribution tools.

• Objective 1 – Transform Tool Labs: By the end of FY16-17, transform Tool Labs to a more modern, flexible and resilient architecture so that tools can more readily be built and adapted by both the Foundation and community. Provide a better alternative to GridEngine for Tools projects, using distributed scheduling with containers. Target: Increase number of Tools projects (currently 1300) on new alternative infrastructure by June 2017, targeting to support most or all new tools. (Technical Operations)
• Objective 2 – Provide architectural leadership: Throughout FY16-17, provide architectural leadership for Wikimedia software, maintaining the conceptual integrity of the system while ensuring that the system is developed in a consensus-oriented way. Continue approving RFCs and improving operational efficiency. (Architecture team)
• Objective 3 – Improve service platform: Support ongoing service developments with mentoring, documentation, code review, deployment, and incident response. Improve service monitoring with better automation for setting up dashboards and alerts. Improve reliability by enforcing SLAs (service level agreements) externally and internally with robust rate limiting and circuit breaker facilities. Improve security by providing shared and reviewed solutions for sanitization and access control, and minimizing privileges for each service. Evolve our container-based distribution solution to the point where we can leverage it for development, continuous integration, third-party distribution, and production deploys. (Technology Services team)
• Objective 4 – Build out Rest API: Build out a consistent, well-documented and cacheable REST API, which will improve performance, support high-volume use cases, and allow developers to more easily work with our content. Expand the REST API to cover use cases making up at least 2/3 of API traffic. Develop and document a clear plan for integrating the remaining use cases in a consistent manner. Improve documentation and evangelize our APIs to users. (Technology Services team)

===

Program 4: Improve site performance

===

Teams: Performance, Technical Operations (see objective)

====

Goal 1: Make access to Wikipedia faster and more reliable, especially for mobile and global users

====

For the Wikimedia movement to be truly global, we have to provide excellent access around the world. With more people accessing our sites and creating content via mobile phones, we have to ensure that the sites are available, even if their Internet connections are limited or devices are basic. At the moment, all logged-in user traffic is handled by a single data center in Ashburn, Virginia. By the end of the fiscal year, we plan to serve users from our Texas and Virginia locations allowing us to improve access and provide substantial user value by expanding the reach of our infrastructure in a manner that is both cost-effective and maintainable. This work will allow the Foundation to expand to other data centers as needed in the future, significantly reducing both operational costs and time delays to users.

• Objective 1 – Improve page delivery: By the end of FY16-17, focus on identifying and fixing performances and architectural issues exposed by performance measurements, analysis, and site traffic. Follow the numbers, using profiling data to pinpoint bottlenecks in our software. This will allow pages to load faster and consume less bandwidth, with essential content appearing first. Targets: 15% improvement in page “paint” time (the time to load the visual page and scroll) and 25% improvement in page save time. (Performance team)
• Objective 2 – Move all URL-routing to PHP: By the end of Q2 in FY16-17, reduce the current complexity so that when a user enters a URL, the site quickly serves up that content, reducing processing time and increasing our ability for search engine optimization. This means that instead of multiple layers (Varnish, Apache, and HHVM), we will use a common software language, PHP, and move URL-routing logic from Apache to MediaWiki. (Performance team)
• Objective 3 – Improve site availability: In the second half of FY16-17, reduce the time it takes to recover from a failure of our primary data center by half. (Performance team, Technical Operations team)

Note: Baseline data unavailable; it will be established, and then progress will be measured as part of this objective.

• Objective 4 – Deploy Asian caching POP: Starting in Q3 FY 2017 and expected to be completed by Q2 FY 2018, optimize site access for our Asian audiences by deploying a small caching data center in Asia. (Technical Operations team)

Program 5: Expand the way software is tested

Team: Release Engineering

We are constantly updating the software that sustains and supports the Wikimedia projects’ hundreds of millions of readers and tens of thousands of contributors. New software developed by Foundation engineers and community volunteers is being deployed onto the projects nearly daily. The Release Engineering team manages this process, ensuring that every new deployment does what it’s supposed to do, building critical testing software relied on by Foundation and community developers.

====

Goal: Add a new automated browser testing framework in a more popular programming language, namely Javascript

====

Currently, production testing for Wikimedia can only be created using the Ruby programming language, limiting the number of developers who create and maintain the end-to-end test suites. By adding JavaScript capability, we will greatly increase the ability of developers inside and outside the Foundation to more quickly and frequently test the software updates that our sites’ users and contributors use every day.

• Objective - Release a new test framework: By the end of Q2, release a complete version of the JavaScript-based framework for developers to use in the testing of Wikimedia’s software updates. In Q3 and Q4, measure its success by the number of changes that the community’s developers make in relation to Wikimedia’s developers.

==

Strategic Partnerships

==

The Strategic Partnerships teams is primarily focused on partnerships with technology companies, mobile providers, and hardware manufacturers. We explore new partnerships that can enhance Wikimedia projects. In the event that there is a pre-existing movement partner that has a relationship with a partner we are targeting, we collaborate together to leverage the work and relationship or to decide together who should drive the partnership forward.

The Strategic Partnerships teams coordinates the Foundation’s conversations with potential partners. When starting discussions, we explore with a partner how we might work together to provide value to the Wikimedia Foundation. Once we establish how the partner might be interested in working with us, we bring in the appropriate teams at the Foundation to lead the discussion.

===

Program 1: Increase partnerships and promotions

===

Team: Strategic Partnerships

====

Goal: Increase readership and revenue to support the Foundation

====

The team will provide value for the Foundation through partnerships that increase readership, receive informative or actionable data from partners, or result in corporate donations. Distinct from the Global Reach team, these partnerships are generally focused on expanding or maintaining readership on WMF sites in markets where Wikipedia is already an established brand.

• Objective 1 - Manage relationships with key tech partners: Pursue and establish partnerships with key tech companies and to seek opportunities to secure corporate donations by the end of FY 16-17.
• Objective 2 - Support and grow our apps and preloads: Sign 2 major preloads with leading tech companies and arrange 5 app promotion deals with key partners to increase the number of app downloads.

===

Program 2: Carefully grow Wikipedia Zero

===

Team: Global Reach

The Wikipedia Zero program was created in 2012 to expand the reach of Wikipedia and the Wikimedia projects in regions where data affordability was identified as a barrier to accessing knowledge and educational resources. To this date, we have launched the program in more than 60 countries, which has provided Wikimedia project access to a possible aggregate of 750 million people during the course of the program.

====

Goal: Remove the barrier of cost and increase readership

====

As data charges remain high in many countries in Africa, Asia, Latin America, and Middle East, Wikipedia Zero continues to be relevant to provide access to Wikimedia projects to under-served populations in these geographies.

• Objective 1 – Build new Wikipedia Zero partnerships: In 2016-2017, the Global Reach team will adopt a more focused approach, only pursuing proactive partnerships in our 6 priority countries identified through the New Readers project. Our goal will be to increase Wikipedia Zero’s footprint by adding 100 million new readers from these 6 target countries by the end of FY2016-2017, in addition to our current 470 million users.

• More details: Our team will remain open to incoming requests from motivated mobile operators in other countries, and explore them as appropriate. Both inbound and outbound efforts for Wikipedia Zero are and will continue to be guided by our operating principles. For each country, we will continue to consider whether data affordability is a significant barrier, and how local policy regulations affect the program’s implementation.
• Objective 2 – Refine the Wikipedia Zero program: During the course of next fiscal year, the Global Reach team will focus on understanding the impact Wikipedia Zero has had with different kinds of users – from general readers to active editors – to allow for better data-driven decision making.

More details: We have learned about the program’s impact through practical experience in the countries and communities where the program is active. Recently, we started conducting phone surveys through a specialized global survey provider based in Ghana, VotoMobile, to collect quantitative data related to our anecdotal experiences. We have completed these surveys in Ghana and Mexico, with Nigeria and India planned next. We chose to use phone surveys as the most cost effective means to get quantitative data on the awareness and perception of Wikipedia, along with understanding what barriers are preventing or inhibiting Wikipedia usage. Using a non-Wiki based survey in countries allows us to get both people who do not use Wikipedia, as well as those who do. We also plan to do a community consultation along with an on-wiki survey to understand the program’s impact and promote a data-driven dialogue about the program within our movement. See specific details: Global Reach Insights.

• Objective 3 – Establish at least one outreach or community support activity with a Wikipedia Zero partner: The Global Reach team will work with an existing mobile operator partner to further distribution, access, and awareness of Wikipedia in a Wikipedia Zero country by the end of fiscal year 2016-17.

More details: We want to strengthen the communication and overall connection with Wikimedia affiliates and community at large. When an unintended problem caused by zero-rating arises, our team will continue to take responsibility and work with the communities affected to find the best way to address it. When we have partnership opportunities that would affect and/or interest our communities, they will be involved early and often. Our team is committed to ensuring that the Wikipedia Zero program is always contextually aware and supportive of our mission.

===

Program 3: Increase reach through new types of partnerships

===

Team: Global Reach

We need to reach new readers in countries where Wikipedia usage is significantly lower than demographic and internet/mobile phone access data would indicate. This work needs to be done urgently, at scale, and with dedicated resources.

The Global Reach team will focus on 4 different types of partnerships:

• Local governments
• Nonprofits organizations
• Educational institutions
• Corporate Social Responsibility (CSR) oriented private sector companies.

These 4 categories are broad, as there are clearly many opportunities we could explore within each. For more information details of current projects: Global Reach.

We are aware that local affiliates and individuals from our communities lead many of these local partnerships and our intention is not to change that. Our team will only pursue or investigate partnerships focused on readership. When editorship becomes the focus of a partnership, we will involve the local community.

====

Goal: Expand Wikimedia projects’ awareness and usage through new partnerships

====

While working on Wikipedia Zero over the last four years, we have identified key barriers that go beyond affordability and require diverse types of partnerships. Lack of awareness about Wikipedia, infrastructure limitations, low digital literacy, and gender inequality are some of the issues we face when trying to expand awareness and access to Wikimedia content.

• Objective 1 – Explore and develop new types of partnerships: The Global Reach team will explore new types of partnerships with nonprofits, governments, educational organizations, and private sector companies, focused on readership and distribution. Our goal is to build two new partnerships in each region (Middle East and Africa, Asia and Latin America).

More details: We are aware that local affiliates and individuals from our communities are leaders on local partnerships and our intention is not to change that. If editorship becomes the focus of a partnership, we will involve the local community.

==

Communications

==

We develop initiatives to increase the reach of Wikimedia – the first strategic focus area, and are working to expand our capacity for support and integration for community – the second strategic focus area. The Communications team develops and sustains awareness and appreciation of the Wikimedia movement, mission, and brand among the global general public. This is accomplished through media and public relations, strategic messaging and issues management, brand management and campaigns, digital production and communications, audience development for content and product, communications capacity building for global contributors and affiliates, and support for written and visual products of the Wikimedia Foundation, its departments, executives, the Board of Trustees, and the Wikimedia movement.

In the coming year, the Communications will implement strategic initiatives that help increase the awareness and use (reach) of the Wikimedia projects, movement, and brand. People around the world experience Wikimedia in different ways: In order to engage them effectively, we need to start by identifying who we intend to reach (identifying audiences), develop an understanding of their communications (brand awareness, affinity, and sentiment) and product (user journeys, product awareness) needs. We also have opportunity to extend the reach of specific products and projects that support our mission in markets where people already know and use Wikimedia projects, such as mobile web, apps, Wikipedia Zero, and the visual editor. In the coming year we will identify specific, high-potential audiences, improve product messaging and presentation, and run integrated campaigns to increase awareness and adoption.

===

Program 1: Improve public understanding and appreciation for Wikimedia movement and projects

===

Team: Communications

Public awareness and understanding of Wikimedia's core purpose and value are critical to fulfilling our vision of reaching every human, and thriving in the future.

====

Goal 1: Understand current public perception

====

Conduct research and analysis to understand public perception of Wikimedia projects and community using sources including international press and social media.

• Objective 1 – Conduct coverage audit from past year: Review top narratives, outlets, geographies, sentiment surrounding Wikipedia, Wikimedia projects, and the Wikimedia Foundation to better understand FY15-16 coverage.
• Objective 2 – Continue media monitoring: Continually monitor international media coverage and social conversations to further inform messaging strategy.

Note: this work will begin in Q4 of FY15-16 but will continue through FY16-17.

====

Goal 2: Develop proactive public messaging strategy for Wikimedia projects

====

Using insights from Goal 1, build year-long messaging strategy through the end of FY16-17 to guide all proactive messaging and PR work.

• Objective 1 – Identify top narratives: Use narratives to address gaps or misunderstandings in public perception (based on coverage audit and media monitoring) of Wikimedia movement and projects and support organizational objectives.
• Objective 2 – Build strategy and tactics: Outline strategy for increasing awareness of priority narratives throughout the year among target audiences, with focus on media relations, editorial (blog and other digital channels), advocacy, and social media.

====

Goal 3: Implement messaging strategy

====

Inform proactive PR, editorial, and social media with messaging strategy. Remain agile and responsive to incorporate ongoing insights and new objectives.

• Objective 1 – Obtain positive international media coverage: Build and strengthen relationships with key outlets and secure coverage of top narratives, leveraging community stories and achievements, and the Foundation-led programs and technology.
• Objective 2 – Increase engagement with top narratives: Reach audiences through digital channels (blog and social) with content related to top narratives. Encourage candid, meaningful discussion and incorporate feedback back into messaging strategy.

===

Program 2: Make our brand more consistent, relatable, and more easily understood

===

Team: Communications

We want people to make the choice to visit and contribute to the projects, partner with our movement, advance our values, and engage with our mission and brand. To increase this awareness and understanding we will continue to develop initiatives to promote Wikipedia and the Wikimedia projects. Those initiatives include storytelling materials to be used throughout the movement, outreach such as the annual report, and discussion of brand strategy with affiliates and interested community members.

====

Goal 1: Expand storytelling and video production

====

We develop inclusive processes to create shareable materials for the use of the entire movement, and outside media sources. Stories and pictures explain the people, values, and efforts of Wikimedians to new audiences.

• Objective 1 – Build testimonials of volunteer efforts: Help explain the movement to donors and the general public by building at least 15 new interviews of community members that can be used in outreach materials. They will be from around the globe and explain a variety of volunteer efforts.
• Objective 2 – Develop videos of volunteer events: Produce guidelines (Q1) for, and publish, 10 short videos (dependent on event timing) based on video shot from throughout the movement representing volunteer events and explaining aspects of Wikimedia. This will reach more than a million casual social media users.

====

Goal 2: Brand standards and support

====

Design guidance builds a consistent look and feel over time, which has been proven to increase trust and raise public perception. Increased trust supports collaborative and partnership opportunities for the Foundation and across the movement. Careful stewardship of the movements' brand protects the tremendous cultural and financial value established by volunteers.

• Objective 1 – Create annual report: Q2 to Q3 of FY16-17, work with Finance and Advancement to create an annual report of FY15-16. The annual report is a significant way we share knowledge of the Wikimedia movement with the public. As an example, for FY14-15 the annual report was integrated with Wikipedia’s 15th birthday.
• Objective 2 – Expand design capacities: Assist with creative brief, plan and style guides; review of all organization materials including monthly metrics and other initiatives. Increase response time for community requests. This is an ongoing core capacity.
• Objective 3 – Continue to develop brand strategy for the Wikimedia movement: We will share our early understandings of the project’s brands, and ask for community feedback. The first step is in planning for Wikimania. Further steps will grow from those conversations.

===

Program 3: Identify and build understanding of new audiences

===

Team: Communications

To fulfill our strategic objective of reach effectively, we need to first identify potential new audiences and understand them. We want to identify and build deep understanding of the communications needs and tendencies of people unfamiliar with Wikimedia through initial outreach and evaluation. This includes conducting research in collaboration with other internal teams (Design Research, Reading, Global Reach, and others) to understand awareness, needs, and media habits.

====

Goal 1: Understand new readers to better explain and raise awareness for Wikimedia projects

====

Continue research in 2 countries (Nigeria, India) in cooperation with Design Research, Readership, Global Reach, and Community Engagement teams. This will allow Communications to develop specific messaging, social media content, and localized media that explain Wikimedia projects and adjust Wikimedia project perceptions based on documented challenges. It will also allow the Communications teams to better support local community press and publishing efforts to raise awareness of Wikipedia and Wikimedia projects.

• Objective 1 – Establish personas for use in communication strategies: Establish guiding "new reader" personas that typify user habits, needs, media preferences, and technologies. Develop strategic approaches and publishing channels to effectively reach these types of readers. Extend social media followings among new reader persona types to grow awareness and advocacy of Wikimedia projects. Timing is tied to research.

====

Goal 2: Segment existing audiences

====

Identify and connect audiences with new Wikimedia products to increase Wikimedia project adoption or deepen user engagement.

• Objective 1 – Define target audiences: Define 2-3 high potential audience segments within existing users, to match with new tools/products and communicate through future campaigns.

====

Goal 3: Build feedback loops

====

Identify and implement feedback loops for audiences, including owned channels (social media), surveys, and more. Building a feedback loop means to establish a practice of collecting feedback, making improvements on that feedback, and reviewing that cycle. It should be iterative.

• Objective 1 – Pilot feedback loops: During FY16-17, plan and pilot multi-channel audience feedback loops that connect us with 1,000+ users.

===

Program 4: Increase awareness and product adoption among specific audience segments

===

Team: Communications

Once we have identified focus audience segments and built an understanding of their needs and sentiment, we will work to raise awareness of the Wikimedia projects and help increase adoption of Wikimedia products. We will do this by iteratively developing and executing multi-channel communications campaigns tailored for specific audience segments. These campaigns will include content we distribute on our "owned" channels (social media, blog), PR, influencer engagement, and potentially live events. Our aim will be to help people connect with and use Wikimedia products and projects in the the most relevant, accessible ways.

Note: Although Wikimedia projects are for the whole world, different people around the world have different needs from Wikimedia projects. We will start by identifying specific audiences to focus our outreach.

====

Goal 1: Raise Wikimedia awareness among new readers

====

Develop strategies for selected audience segments to increase user engagement in low readership countries. This work will begin by utilizing New Readers research insights to produce audience segments with distinct technology, education, and Wikipedia perception challenges. The communications team will then work in concert with local community and media to offer targeted education and project advocacy. Refine based on performance.

• Objective 1 – Target new readers with messaging campaigns: Develop messaging campaigns in 1 country with low readership based on Program 3 (Identify and build understanding of new audiences) research.
• Objective 2 – Expand press coverage: Execute campaigns to raise new reader awareness for Wikimedia by earning local press and social media coverage.
• Objective 3 – Measure performance: Measure initial campaign impact against control baseline. Establish new, appropriate benchmarks for performance measurement, continue to iterate campaign to continuously improve performance.

====

Goal 2: Showcase Wikimedia’s relevant content and share our mission through emerging digital communications platforms and services

====

We will use new social platforms to help people interact with Wikimedia content in the newest, most relevant ways.

• Objective 1 – Grow three new social channels, with at least one in Asia: By using emerging communications platforms and services, show how Wikipedia/Wikimedia continues to be relevant in the world of shared online content and help people interact with Wikimedia content in new ways.
• Objective 2 – Work to increase diversity via specific channels and programs: With Pinterest we will engage with a following different from our usual demographics by enlisting “guest hosts” from the community who curate and introduce content from Wikimedia Commons.
• Objective 3 – Pilot distribution program: Pilot one new Wikimedia content distribution program on social media targeting new audience segment.

====

Goal 3: Introduce and advocate new products

====

Develop and launch product-specific campaigns, with campaign specific KPIs and targets for measuring impact. Refine based on performance.

• Objective 1 – Create product campaigns: Design two product-specific campaigns to have statistically significant impact on user adoption and engagement. Specific metrics are TBD based on research in Program 3 (Identify and build understanding of new audiences).

===

Program 5: Grow and improve audience and engagement on the Wikimedia digital channels

===

Team: Communications

As media and communications continue to change outside of the Wikimedia world, we will be present on new digital channels, bringing attention to the Wikimedia projects and movement. We will increase both audience and engagement on multiple platforms of global social media, and on the Wikimedia blog, with continual daily communications showcasing Wikimedia content, connecting with people, and explaining the movement to new communities.

====

Goal 1: Spread broad messaging to new and existing communities

====

We will represent Wikimedia and Wikipedia with verified accounts on the largest social media channels as a global information source.

• Objective 1 – Expand and improve social media: By the end of FY16-17, we plan to:
• Leverage the Facebook group of community members and other social media platforms to connect with Wikimedians around the world and incorporate their ideas, stories, and needs into a more crowd-sourced social media with a deeper and more meaningful authenticity.
• At the urging of the community, we will not over-emphasize corporate social media metrics at the expense of more meaningful connections. We will steadily grow Twitter followers 10%; grow Facebook followers 15%; grow Instagram follower base 20% and engagement proportionately.
• Grow the Wikimedia blog readership and increase social mentions by 5%.
• Objective 2 – Create social campaign prototype: By the end of FY16-17, create a prototype for social campaigns (including video, community management, engagement and reporting), through discussion and development with community partners. This prototype will be executable at regular annual milestones – e.g., Wikimania, major global conferences.

====

Goal 2: Advocate the movement via social media

====

We will help explain and raise awareness of the movement by profiling community members, highlighting new initiatives, and explaining the best of Wikimedia. We will measure this with press mentions, traffic to the blog and online engagement, such as social media mentions.

• Objective 1 – Feature Wikimedians: Profile or feature Wikimedians from 10+ countries in posts and the community digest, including priority strategic growth countries (Nigeria, Egypt, India, Indonesia, Brazil, Mexico). Grow engagement, relationships and awareness in key areas: specific metrics will be developed on a country-by-country basis.
• Objective 2 – Increase Wikimedia blog readership: Grow Wikimedia Foundation blog readership by 5% and increase social engagement on posts about the blog in order to engage community with our created content.
• Objective 3 – Distribute video: Distribute video to relevant audiences focusing on the Wikimedia movement and projects, achieving 25,000 views per video on social media as well as embeds on other websites. This will share a human view of the movement in new areas, to go beyond text on a website. (see Goal 1 under Program 2).

====

Goal 3: Cultivate new communities to support future growth of the projects

====

Just as we have a community of editors that is at the core of the Wikimedia projects, we can also use our social channels to cultivate communities of people who love and support Wikipedia. We can reach people in under-served regions and languages, and build relationships with potential future contributors, advocates, and donors.

• Objective 1 – Engage through social media: Strategically and continually share relevant information on social media to encourage engagement and connect with readers who want to take part more in the movement. By strategically posting on timely subjects we can demonstrate Wikipedia’s growing relevance in current events. Target of 1M engagements (reactions, comments and shares) per month.
• Objective 2 – Connect with growing communities: Gain important insights about our readers and build relationships with new or growing communities by building sustained insight relationships with 25 users across priority countries.

==

Legal

==

The Wikimedia Foundation legal team oversees the global legal portfolio for Wikipedia and its associated projects. Our goal is to support the Foundation and the communities of contributors – consistent with our legal ethics – in their mission to share free information worldwide. We aggressively and globally steward the values of our mission and our community of writers, editors, photographers, and other contributors by building and overseeing governance where appropriate; by protecting and defending those key values when challenged; and by facilitating initiatives designed to support and grow our community and their various projects, including Wikipedia and its sister Wikimedia websites.

Part of our budget and work focuses on core legal services for the Foundation. These services include, for example, contracts negotiation and review, Board governance, fundraising compliance, training, general internal legal advice, and product and tech support. We address these core services in a different section below ("Non-Programs").

A large part of our budget and work – which is addressed here – is devoted to programmatic services where we work globally to support the Wikimedia communities to achieve their mission on different fronts. For example, the legal team dedicates resources to supporting users in project-related litigation, and we engage with the Wikimedia communities through consultations and advice on core policies, such as our Terms of Use, Trademark Policy, and various privacy policies. The programmatic work that we do as a legal team is somewhat unusual for a traditional global website, but it represents the critical interest of community members in legal issues underlying our mission, such as censorship, copyright, free expression, privacy, trademarks, and access to knowledge.

===

Program 1: Protect project trademarks and practices

===

Team: Legal

In addition to its own house marks, the Wikimedia Foundation has been entrusted with stewardship of the trademarks that represent the high-quality content created by the contributors supporting the Wikimedia 12 projects. We presently have 39 marks, which we manage within our global portfolio of more than 1,500 pending or filed registrations. We work closely with Communications to ensure consistency in practice and strategy.

====

Goal: Protect project trademarks

====

We will grant licenses to project marks that support the mission of the Wikimedia communities and enforce proper use of those marks to protect the reputation and mission of the communities and projects.

• Objective 1 – Support mission-based community use: Continue to advise individual community members, user groups, chapters, and others on the application of our open Trademark Policy, with a goal of supporting the communities’ work in furtherance of their mission. This policy was created in consultation with community members in 2013, provides an easy-to-use guide to facilitate community use of the project marks. It allows for expansive use of the trademarks, but it still preserves the goodwill attached to them as a sign of high-quality Wikimedia content.
• Objective 2 – Granting mission-oriented licenses: We receive requests to use project trademarks in contexts from t-shirts to popular movies and television. Consider each request and selectively grant trademark licenses to promote the project brands in contexts that will uphold their community-built reputation and attract new users consistent with our mission.
• Objective 3 – Enforcement against misuse of marks: Defend the community-entrusted marks to help ensure their good reputation. Send cease and desist letters relating to deceptive or improper use of the marks on- and offline. To fight cybersquatters and fraudulent use, file World Intellectual Property Organization (WIPO) actions, when appropriate, to protect the reputation vested in the project marks.
• Objective 4 – Maintain and defend project marks worldwide: As part of our overall program, maintain project trademark registrations and domains worldwide, and defend them against wrongful legal and administrative challenges, including those from government offices and third parties globally.

===

Program 2: Support community members in unfair litigation while defending our mission

===

Team: Legal

We support community members and their mission through worldwide defensive litigation. We recognize that to make free knowledge available to a global audience, we must embrace not only the projects themselves, but also the individuals who contribute to them when their work leads to rare, but unfair, litigation.

====

Goal: Support community members who are facing unfair litigation

====

We will help community members when they are sued unjustly in connection with their activities on the projects to ensure that they are supported in their mission to create and disseminate Wikimedia free content. We assist community members to find legal counsel, and we often provide funding for their defense. With the support of a worldwide network of outside counsel, virtually all litigation to date has been successful under these programs.

• Objective 1 – Administer the Defense of Contributors Program: Administer the Defense of Contributors Program to provide support and funding when a contributor is sued in relation to their legitimate activities on the projects.
• Objective 2 – Administer the Legal Fees Assistance Program: Administer the Legal Fees Assistance Program to provide support and funding when a community member who serves in an administrative or governance function is sued in relation to their legitimate activities on the projects.

===

Program 3: Protect the communities’ discretion in determining proper content

===

Team: Legal

The Wikimedia communities exercise their editorial discretion in creating and reviewing content on the projects. To support this critical role, the Foundation only acts on content takedown notices when legally and factually required. We aggressively oppose unwarranted demands to remove content. We research and clarify the law in areas not well established.

====

Goal: Ensure that the communities retain their editorial discretion with respect to project content

====

We will aggressively oppose demands to remove content when inconsistent with facts and law.

• Objective 1 – Investigate inquiries swiftly and aggressively: Quickly and thoroughly respond to inquiries via the “legal@” email queue. Oppose unfounded demands in appropriate venues, including the courtroom. Explain to requesters how the projects and the communities work. Suggest community solutions to content issues when possible. Remove content only when required by facts and law.

===

Program 4: Join with the Wikimedia communities in advocating for policy positions relevant to the work of the communities

===

Team: Legal

We advocate for the Wikimedia movement, mission, and values when lawmakers and government officials are considering policies that may affect how people can access, use, or contribute to the projects. Our public policy work takes many forms, from public comments – such as those submitted to the U.S. Copyright Office on mass digitization – to proactive litigation – such as Wikimedia v. NSA. Our goal is to protect and improve the environment in which the projects have been built by our contributors and to improve the reach of the projects consistent with our mission.

====

Goal: Address issues of future importance to the projects

====

• Objective 1 – Coordination and identification: Coordinate with members of the communities via the Public Policy Portal and Public Policy Mailing List to determine which issues should be addressed to best support the worldwide communities.
• Objective 2 – Planning, drafting, and execution: Work with community members to draft and submit public comments, assist in publicity campaigns, and take other actions so that decisionmakers are aware of the positions of the communities. Use the policy portal, mailing list, and Wikimedia Blog to report our actions and their outcomes in a way that encourages community participation. We expect to focus on: promoting the freedom of panorama and free licensing, continuing to oppose government censorship in various venues, and defending intermediary protection laws on which the projects depend.

===

Program 5: Maintain transparency in our defense of content and user privacy

===

Team: Legal

A key value of the Wikimedia movement is transparency. Part of our commitment to this principle is the publication of our biannual Transparency Report, which provides the communities and the general public with information that maintains trust in the Wikimedia projects.

====

Goal: Fight censorship and report on efforts to modify content or obtain user data

====

Inform users and the public about requests to alter the projects or to obtain user information.

• Objective 1 – Publication of biannual Transparency Report: The Transparency Report details requests we receive to alter or remove content, and to obtain nonpublic user information, from governments, businesses, and others. Publish this report twice a year, approximately in February and July.
• Objective 2 – Resist demands to remove content or provide nonpublic user information: As noted above, when we receive requests to remove or alter project content, we will push back, unless otherwise compelled by facts and law. In 2015, we received 454 requests, and we denied all of them. Similarly, we will not provide nonpublic user data, unless confronted by legitimate legal process or emergency, as described in our requests for user information procedures and guidelines. In 2015, we received 48 requests for user data, 13 of which were informal requests from governments, and we denied all but one.

==

Non-programs

==

Fundraising, Fundraising Tech, Legal, Talent and Culture, Team Practices, and Finance and Administration are considered operational. While their work represents a minority percentage of our budget, it is crucial to the strength of our organization, the health of our culture, and every success of the Foundation.

===

Fundraising

===

The Fundraising team raises the funds necessary to support a vibrant Wikimedia movement. We work to fulfill the short and long-term resource needs of the organization.

We have developed a plan to raise 63 million USD. The majority, 57 million USD, is through our annual online giving campaigns, both banners and email campaigns, and 6 million USD is through foundation grants and major gifts. This plan keeps our fundraising cost ratio at less than ten percent, which earns us the top rating for fundraising efficiency from Charity Navigator. We will also be focusing our efforts on improving campaigns on mobile devices in response to the growth in mobile readership, and building the endowment to ensure the long-term health of our organization. This is critical not only to reach the revenue target in FY 2016-17, but it is also important for sustained future support for our mission. In addition to funding the annual plan, we will be raising 5 million USD for the Wikimedia Endowment and securing five planned giving commitments to support the Foundation for the long-term. Lastly, this year we will be investing in eliminating duplicates from our donor database and deepening our current donors' relationship with the organization.

===

Fundraising Tech

===

The Fundraising Tech team supports ongoing fundraising goals by maintaining and improving the existing systems used by the Online Fundraising and Major Gifts teams. We maintain and improve all existing online fundraising systems and integrated third-parties upgrades. New projects for FY16-17 include adapting to cross-border donation laws, and supporting global credit card processor mergers. Long-term scalability improvements to our customer relationship management system and work to identify and remove pain points in working with our donor data are also part of our core efforts.

===

Legal

===

In addition to the programmatic work set out above, part of our department's work and budget in FY16-17 will be focused on core legal support for the Foundation. Much of this core work will support programs in other departments. We will provide defense against inappropriate challenges targeting the Wikimedia Foundation, including through mitigation of legal threats and opposition to global litigation against the Foundation.

We will oversee our contract oversight and management, which necessitates the negotiation, review, and filing of about 275 contracts in FY16-17. These agreements are received almost daily from all departments, and vary vastly in complexity and topic area.

As in other years, in FY16-17, we will maintain the Wikimedia Foundation organizational trademark, provide HR legal support, and ensure compliance and daily advice in various areas, such as global fundraising, copyright, privacy and security, and intermediary liability requirements. We will support our engineers with ongoing technical advice on a variety of issues including open source licensing, mobile device regulations, and user interface design questions, including initiatives like "privacy by design." We will also address movement governance issues and provide Board support, including providing advice on legal and other matters, as set out in the Board Handbook.

We plan to launch more trainings to keep staff informed on a variety of topics, such as handling data breaches, dealing with legal holds, and copyright onboarding for those making videos and other media on behalf of the Foundation. We also anticipate updating the Board member onboarding process with new training materials.

===

Talent and Culture

===

The Talent and Culture team acts as a partner with the organization and organizational leadership to develop culture, increase leadership capacities, and provide personnel administration in service of the ongoing support and maturation of the Foundation.

The three pillars we offer are recruiting, human resources, and learning and development. We find and hire a diverse group of talented professionals as new staff, interns, and contractors who support our community and Wikimedia projects. We manage the full employee lifecycle – onboarding, performance management, compensation changes, life events, wellness and off-boarding processes when staff leave the Foundation. And in our learning and development capacity we facilitate the development of managers and leaders capable of handling the complexity of our operating environment, ensure that staff are able to develop in way that is consistent with the Foundation mission and goals as well as maintain an organization in which people thrive.

===

Team Practices

===

The Team Practices Group (TPG) facilitates the use of practices and processes that support the health of teams across the Foundation, with a strong emphasis on creating conditions of clarity, trust, and continuous improvement. The team accomplishes this work through dedicated resourcing, lightweight coaching, and workshops at the Wikimedia Foundation.

===

Finance and Administration

===

The Finance and Administration department is responsible for both the timely and professional fiduciary overview of all finance activities, and over-seeing the physical space and technological/infrastructure needs of Foundation staff.

The core responsibilities and objectives of the Finance team include managing and controlling daily, weekly, monthly and annual finance operating workflows such as accounting, processing of the Foundation’s financial transactions, external reporting, treasury, and compliance filings. We also lead the financial management workflows for the Annual Plan, budgeting, investment management, and other financial decision making activities in support of the Foundation’s mission.

The finance team partners with other Foundation teams such as Legal to undertake risk management activities including developing the Foundation’s insurance portfolio, to protect the Foundation, its Board members, its employees, its assets, and its websites. We also support and partner with the Funds Dissemination Committee and the Community Resources team to enable their objectives by providing or securing ongoing finance expertise and improved financial reporting. Finally, we enhance financial systems functionality to increase transparency and improve effective and efficient financial operating workflows.

The critical FY16-17 Finance team outcomes include the successful completion of the annual audit (where the team supports the Board's Audit Committee), the publication of the Foundation's 990 form, the finalization of a SMART and transparent Annual Plan, and improved quarterly and mid-year 16-17 Annual Plan reporting.

Office IT and Administration provide the physical and information technology infrastructure that our staff needs to serve our community and the Wikimedia sites. The Office IT team handles the IT infrastructure in the San Francisco office (such as desktop PCs, internal servers, networking infrastructure, video-conferencing equipment). The Administration team provides support staff for each team, as well as the physical infrastructure that the rest of the organization needs for their work, such as planning and managing the office space. The Travel team, as part of our Administration team, provides travel support to employees, Board members, and others working for the Foundation.

==

Staffing

==

Note: The data presented below may change depending on the feedback received from the Audit Committee and Board of Trustees. If the changes are deemed significant, we will revise and publish the new data in the final version of the Annual Plan.

===1.

Please describe your organization's staffing plan or strategy here, or provide a link to your organization's staffing plan or organogram

===

Table 4 - # of Staff - Program versus Non-Program

Description	FY15-16 Plan	FY15-16 Projection	FY16-17 Plan
Program	207	203	209
Non-program	73	69	68
Total # of Staff	280	272	277

2. Number of staff by departments or functions

Table 5 - # of Staff - By Departments

Description	FY15-16 Plan	FY15-16 Projection	FY16-17 Plan
Community Engagement	38	40	40
Product & Technology	149	146	152
Communications	11	10	10
Legal	12	12	11
Advancement (Fundraising/Partnerships)	23	20	20
Talent & Culture and Team Practices	19	19	19
Finance/Administration/IT	26	23	23
Governance	2	2	2
Total # of Staff	280	272	277

3. Staffing expenses

Table 6 - Staffing Expenses Summary - Program versus Non-Program (all amounts in USD)

Description	FY15-16 Plan	FY15-16 Projection	FY16-17 Plan
Program	24.944.635	23.207.612	26.016.801
Non-program	10.290.038	9.040.070	10.222.130
Total Staffing Expenses	35.234.673	32.247.682	36.238.931

Table 7 - Staffing Expenses - By Departments (all amounts in USD)

Description	FY15-16 Plan	FY15-16 Projection	FY16-17 Plan
Community Engagement	4.177.630	3.993.134	4.387.380
Product & Technology	18.668.854	17.482.986	20.144.960
Communications	1.367.274	1.033.979	1.389.242
Legal	1.635.234	1.496.645	1.746.617
Advancement (Fundraising/Partnerships)	3.082.754	2.458.768	2.530.493
Talent & Culture and Team Practices	2.592.901	2.274.591	2.877.817
Finance/Administration/IT	3.128.785	2.675.229	2.726.981
Governance	581.241	832.350	435.441
Total Staffing Expenses	35.234.673	32.247.682	36.238.931

==

Financials: FY 2016-17

==

Note: The data presented below may change depending on the feedback received from the Audit Committee and Board of Trustees. If the changes are deemed significant, we will revise and publish the new data in the final version of the Annual Plan.

===

Detailed Budget: FY 2016-17 annual plan

===

Table 8 - Program and Non-Program Expenses Summary (all amounts in USD)

Description			FY16-17 Plan
Program Expenses
	Staffing		26.016.801
	Non-Staffing
		Data Center CapEx	2.185.177
		Data Center OpEx	2.504.000
		Grants	5.460.000
		Outside Contract Services	2.398.854
		Legal Fees	1.017.800
		Travel & Conferences	1.561.305
		Other expenses	1.881.811
	Sub Total Program Expenses		43.025.748
Non Program Expenses
	Staffing		10.222.130
	Non-Staffing:
		Donation Processing Fees	2.240.000
		Outside Contract Services	2.213.800
		Legal Fees	621.900
		Travel & Conferences	289.673
		Other expenses (Facilities, Insurance, FF&E, All Hands, Recruiting, Staff Development, Personal Property Taxes, and Etc.)	4.386.749
	'Sub Total Non-Program Expenses'		19.974.252
Total Annual Operating Expenses			63.000.000

Note 1: The financial data presented here is not broken out by the specific programs described in the narrative above. One of the Finance department’s FY16-17 objectives is to assess and adapt our existing financial workflow(s) and associated systems to budget and monitor program costs.

Note 2: The Finance department is revising its goals for FY16-17 to include enhancing its leadership and guidance to other movement entities - specific objectives and resource planning is under development and will be developed in consultation with others.

===

Revenues: FY 2016-17 annual plan

===

1. Does your organization plan to draw on its operating reserves during the upcoming funding period to support its expenses? If so, please provide the amount you intend to draw from your reserves here. This should not be included as revenue in the table below.

No.

2. Please use this table to list your organization's anticipated revenues (income, or the amount your organization is bringing in) by revenue source (where the revenue is coming from) in the FY. Use the status column to show if this funding is already guaranteed, if you are in the process of requesting funding, or if you are planning to request funding at a later time. Please feel free to include in-kind donations and resources in this table, as applicable, but use the status column to show that they are in-kind resources.

• $57 million from the annual online global campaigns (combined effort by WMF and potentially payment-processing chapters)
• $6 million from Foundations and Major Gifts

===

Expenses: upcoming year's annual plan

===

Table 9: FY16-17 Annual Plan Expenses - By Departments (all amounts in USD)

Description	FY16-17 Plan
Community Engagement	5.728.270
Grants	5.460.000
Product & Technology	27.927.324
Communications	2.344.132
Legal	3.723.517
Advancement (Fundraising/Partnerships)	6.721.948
Talent & Culture and Team Practices	3.626.568
Finance/Administration/IT	6.593.000
Governance	875.241
Total Annual Operating Expenses	63.000.000

==

Appendix 1: Wikimedia Foundation Risks

==

As part of our annual plan cycle, we identify some of the top potential risks that could threaten the Wikimedia Foundation’s mission to empower people to contribute to the sum of free knowledge. These potential risks cover a broad spectrum, including product and technology, fundraising, community health, legal, operations, communications, and other domains. Below we set out a number of examples.

Mitigation strategies are set out below as well, but such strategies can never eliminate all risks. Among other things, this is due to the nature of our culture, movement, and mission as well as resource constraints. That said, we must ensure reasonable assessment of risks to support smart strategic and comprehensive planning.

===

Technology

=== ====

☛ Risk: Failure of technology infrastructure disrupts Foundation operations.

====

In the past, the Foundation has suffered short website outages, which have been the result of technology operations depending on a single data center. Recent efforts adding an additional data center have reduced this risk.

Mitigation strategies:

• Conduct analysis of technology infrastructure to determine bandwidth usage and prevent overloads.
• Analyze technology infrastructure and location of data centers to identify vulnerable points of failure and extend redundancy where appropriate.

===

Competitive Landscape

=== ====

☛ Risk: A competitor provides a better reader experience for Wikimedia content, diminishing our ability to attract readers, editors, and donors.

====

This is an ongoing risk based on for-profit and individual efforts to use our content as well as many third-party apps available in iOS and Android.

Mitigation strategies:

• Understand impact of Internet traffic patterns on readership, edits, and revenue.
• Streamline reader engagement features and upgrade editing experiences to meet user needs.
• Improve presentation and searchability of content.
• Develop a strong partnership program to seek cooperative, working relationships.

===

Fundraising

=== ====

☛ Risk: We experience a greater readership decrease than anticipated in key so-called Global North countries, where we raise the bulk of our funds.

====

While readership remains fairly steady overall, we are seeing a decrease in readership in many of the so-called Global North countries where the Foundation raises the bulk of its funds.

Mitigation strategies:

• Deepen our relationships with our existing donors and expand their engagement with the organization.
• Achieve a higher banner donation rate than the previous year.
• Explore alternative revenue streams that are in line with the Foundation’s mission and values.

===

Community Health

=== ====

☛ Risk: The Wikimedia global movement does not improve in cultural, geographic, or demographic diversity, leading to less relevant and lower-quality content for a global audience.

====

Mitigation strategies:

• Invest in and implement diverse technologies and delivery strategies that (a) raise awareness of Wikimedia projects, (b) help us in identifying and building new audiences, and (c) improve the ability of users worldwide to access the projects.
• Promote community initiatives related to diversity and emerging regions through monetary, communications, programmatic, and evaluation resources.
• Support programs to increase participation from diverse volunteers such as recognition and mentorship.

====

☛ Risk: Foundation-community relations worsen and lead to decreased Foundation effectiveness, reduced on-project civility, editor and contributor attrition, and lower-quality content.

====

Mitigation strategies:

• Focus strategically on community needs in part through the Community Engagement department.
• Improve transparency and increase communications between the Foundation, the communities, and Wikimedia affiliates.
• Work with the Support and Safety team to improve “safe space” policies and other techniques to make the Wikimedia projects safe places for a diverse user community.
• Allocate dedicated financial and technical resources through the new Community Tech team for community requests and tools that positively impact civility and interactions with new users.
• Provide public support and strong stances on contentious issues like gender gap.

====

☛ Risk: Changes to attract new users trigger a strong negative reaction among established editors and contributors that causes them to stop or reduce participation on the Wikimedia projects.

====

Mitigation strategies:

• Ensure constructive user input and respectful socialization of changes early.
• Improve tools to facilitate the introduction of new products.
• Use incremental approaches when introducing new products, including small group beta tests or default settings only for new users.

====

☛ Risk: Community leadership does not develop effectively, damaging community participation, governance, and responsiveness.

====

Mitigation strategies:

• With a greater focus through our Community Engagement department, create spaces and support for innovation, training, and mentorship for existing and new community leadership.
• Support diversification in candidates for the Board of Directors and community governance bodies.
• Improve tools for community administration and management on the projects.

===

Legal

=== ====

☛ Risk: Changes to safe harbor immunity laws abroad expose the Foundation to new, extensive liability, costs, and technology burdens.

====

Immunity laws - known as safe harbor statutes - now protect the Foundation from being sued for content uploaded by users. Changes in those statutes could open us to lawsuits or require costly technical measures to monitor and remove content.

Mitigation strategies:

• As part of ongoing public policy strategy in partnership with our communities, engage in education to inform the public and lawmakers about the importance of safe harbor laws while opposing any threatening proposals.
• Ally with like-minded organizations to persuade lawmakers to pass strong safe harbor protections for hosting companies like the Foundation.

===

Operations

=== ====

☛ Risk: The transition of executive directors causes operational slowdown or the failure to accomplish a critical task.

====

Mitigation strategies:

• Engage in an open and transparent process to select a new ED who will support Foundation and movement values.
• Commit Foundation resources to shoring up core operations and executing key strategic initiatives, while building in flexibility for a new ED.
• Maintain operational accountability to Annual Plan commitments, while building in flexibility for a new ED.

====

☛ Risk: The Foundation fails to accomplish a critical task because only one unavailable or departing staff member has the necessary expertise.

====

Mitigation strategies:

• Identify critical roles and develop succession planning and talent management to ensure that substitutes are available.

===

Communications

=== ====

☛Risk: Part of our communities take a position that is problematic or out-of-step with public sentiment, resulting in damage to brand and reputation.

====

This risk is most acute in areas where the Wikimedia community is not reflective of the diversity of the broader society. Past examples have included controversy around the Gamergate article and discussions on the Wikipedia gender gap.

Mitigation strategies:

• Increase proactive monitoring capacities to better anticipate major community policy or bureaucratic decisions.
• Increase transparency and communications between the Foundation, the communities, and the public.
• Develop strategic messaging with unified narrative, reframing as needed, and with an emphasis on facts and the way forward.

==

Appendix 2: Program - Non Staffing Expenses

==

Table 10 - Detailed information regarding Program - Non Staffing Expenses: Travel & Conferences (all amounts in USD)

Department	Movement	WMF	Total	Reference/Notes
Community Engagement	336,085	253,995	590,080	Movement travel associated with Developer Summit, Hackathon, FDC deliberations, Community Capacity Development Convenings, AffCom, Peer Mentoring Events and Wikimedia Conference
Governance	80,000	45,000	125,000	Movement travel for Board meetings and attendance at community events and ED's attendance at community wide events such as Wikimedia Conference
Product & Technology	N/A	706,848	706,848	Travel associated with Developer Summit, Hackathon, Development and Research Conferences, Peer Mentoring Events and Wikimedia Conference.
Communications	10,000	23,650	33,650	Movement travel associated with attendance at community-wide events such as Wikimedia Conference
Strategic Partnerships	N/A	105,727	105,727	Travel required to meet program objectives described under Strategic Partnerships, primarily to secure partnership or Wikipedia integration in Latin America/Middle East and Africa/Asia region
Total	426,085	1,135,220	1,561,305

Table 11 - Detailed information regarding Program - Non Staffing Expenses: Outside Contract Services (all amounts in USD)

Department	Total	Reference/Notes
Community Engagement	381,922	3rd party resources such as research work, design/build IdeaLab and Grants portal, and contractors for Wikipedia Library support required for the program activities described under Community Engagement
Governance	250,000	3rd party resources for programmatic specialized projects such as strategic consulting and board support
Product	447,121	3rd party resources required for the program activities described under Product. Including Bi-weekly regression testings, daily QA, bots/APIs for both copyright/plagiarism detection, and miscellaneous contracting cost to support the program objectives.
Technology	382,720	3rd party resources required for the program activities described under Technology. Including benchmarking, mobile research, research to improve detection and response capabilities of operations
Communications	897,000	3rd party resources to support increased global awareness of, positive sentiment regarding, and engagement with Wikimedia movement, Wikipedia and sister projects. This includes external research on new readers, proactive public messaging for Wikimedia Projects, campaigns & promotion for volunteer efforts and events, positive media coverage, media and social media monitoring, photography, videography, and other production, the creation of brand materials such as the Wikimedia Foundation Annual Report, and support for design and brand standards. See Program section of Communications.
Strategic Partnerships	40,000	3rd party resources to support research and survey efforts around content usage and Wikipedia’s awareness and access.
Total	2,398,763

Table 12 - Detailed information regarding Program - Non Staffing Expenses: Legal Fees (all amounts in USD)

Department	Total	Reference/Notes
Legal	1,017,800	The legal team dedicates resources to supporting users in project-related litigation, and we engage with the Wikimedia communities through consultations and advice on core policies, such as our Terms of Use, Trademark Policy, and various privacy policies. The programmatic work that we do as a legal team is somewhat unusual for a traditional global website, but it represents the critical interest of community members in legal issues underlying our mission, such as censorship, copyright, free expression, privacy, trademarks, and access to knowledge.
Total	1,017,800

Table 13 - Detailed information regarding Program - Non Staffing Expenses: Other Costs (all amounts in USD)

Type	Total	Reference/Notes
Payroll fees	568,591	Contractual obligation with payroll processor for international staff as a dependency of geo-diversity in staffing resources.
Other Project Expenses	600,000	Project fundings - In support of the Annual Plan
Data Center Hardware Warranty	160,000	Costs associated with Program 3 – Improve Site Reliability and Program 4 – Improve Site Performance under Technology.
Volunteer Support/Interns	90,000	Program 6 and 7 for Technical Collaboration under Community Engagement
Security Testing	90,000	Program 3 – Improve Site Reliability under Technology.
Computer Software	45,200	Grants, research and other required software.
Other operating expenses	328,020	Staff development, memberships, subscriptions, phone services, merchandise giveaways and other minor miscellaneous expenses.
Total	1,881,811

==

Appendix 3: Log of changes made to initial draft based on FDC recommendations

==

For more detailed information, see the FDC's comments to the WMF and the WMF's responses.

Table 14 - Changelog

FDC Recommended Change(s) (summarized)	Response (on FDC Talk Page) or Changes to Annual Plan (AP)
Governance Conduct an external assessment to evaluate board composition, Board onboarding process, relationship between Board and ED, communication channels to all, Board member selection process/criteria, Advisory Board, Board resource allocations Recommend this assessment is completed BEFORE the permanent Executive Director is hired.	Response on FDC Talk page (summary): This has been taken under advisement. The decision is the Board's to make. Staff has been compiling a list of vendors. Board will continue discussion on this at the June 2016 Board meeting. AP changes: None.
WMF Strategy / Long-term Movement Strategy Good the WMF has a new strategy in place, concern it did not have extensive community involvement Concern that Foundation should engage in a process with community to develop a long-term movement strategy to better drive WMF work efforts (similar to the 2011-15 strategy, that is now expired)	Response on FDC Talk page (summary): The current strategy went through a series of community consultations over a 9-month period and will drive the Foundation's work for 18-24 months (starting April 2016). "The Foundation views FY2016-2017 as an opportunity to scope the development of such a movement strategy. We will conduct discovery into the needs, resources, stakeholders, timelines, and other variables necessary to develop a successful strategy, with the intention that strategy development process would occur under the tenure of a permanent Executive Director." AP changes: None.
Financials and staffing Recommends detailed financial budgets Recommends that WMF not "rush" to backfill open staff positions Rationale for new staff is missing	Response on FDC Talk page (summary): Given the systems and process in place, detailed financials by program were unable to be provided this year. Systems and processes are being evaluated to improve the financials for the next round. Talent and Culture is hiring based on standard protocols, and hiring is not being "rushed." AP changes: None at this time. Note that no changes will be made to the overall budget, but very minor changes may be made within the department budgets in the June 6 revision.
Overall comments on programs "Desire for the WMF to view its actions as leveraging a network effect utilising the resources of the global movement" Lack of detailed budget made the individual programs difficult to review out of financial context Recommends more layering; "due to the structure of the plan, the inputs (e.g., resources) are often unclear and the outputs of many programs do not have targets" Reduce repetition of work that is being done across departments (such as New Readers) Clarify terms: New Readers program, Global South, "emerging communities" Appreciates learning and analysis is happening throughout; hopes information is being shared appropriately and acted upon effectively Would like more separation of operational work from programmatic work	Response on FDC Talk page (summary): "Leveraging effect" was discussed internally. This is a useful lens; while some processes in place now (Community Engagement, Product, Legal, Comms), we could have better systems in place to leverage even more and will consider this feedback. Structure was built in layers, to go from general information (department and program descriptions) to more specific (SMART objectives). Where possible, we have clarified the goals and objectives. We will continue to refine interim targets through our Quarterly Goals process. Repetition occasionally occurred since we structured by department, not by overall initiative, since this made sense for the vast majority of programs. We acknowledge there was some overlap for key cross-department initiatives. Internal collaboration is extensive, and we added more framing to the annual plan to help describe how departments work together. Terms clarified. A separate section on Research has been added, so that readers can better understand how this works and is acted upon across the Foundation. Separation of operational and programmatic work needs further definition of terms. AP changes: Any joint work that may have seemed repetitious has been further clarified, so that the specific team's focus is clear for their unique program. New section on "Research across the Foundation" has been added, to show how teams collaborate and share insights.
Community Engagement (general comments) Pleased community health is focus. Appreciates clear description of each team's roles; hopes they are adequately funded because work is important. Concerned with the decrease reported in KPI’s results for the second quarter, encourages this is investigated.	Response on FDC Talk page Regarding KPIs
Community Engagement – Program 1: Develop community leadership and mentorship PC&L "Focus the definition of a 'community leader' in consultation with the community in order to ensure that the process of identifying these is accepted movement wide." Formalize the Peer Leadership Academy with clear access points.	Response on FDC Talk page AP changes: Minor clarifications made.
Community Engagement – Program 2: Introduce training modules for functionaries and event organizers regarding issues management SuSa Synchronize training with others who are doing similar training (e.g., Wikimedia Nederlands). Ensure hosting on a new platform does not get fragmented or narrow community involvement.	Response on FDC Talk page AP changes: Minor clarifications made.
Community Engagement – Program 3: Develop capacity-building tools and resources for core Wikimedia programs PC&L While need is there, it will be important to resource the center appropriately, otherwise it won't work. Is scope resourced effectively?	Response on FDC Talk page AP changes: Clarifications made.
Community Engagement – Program 4: Allocate resources to effective community-led projects Community Resources Work with community to clarify the scope and requirements for each grant, so it's clearly distinguished from chapter grants. Clarify available grant budget by month or quarter. Give applicants the requirements on a timely basis.	Response on FDC Talk page
Community Engagement – Program 5: Give more support to GLAM partnerships PC&L Clarify GLAM program; add targets. Communicate what it is more clearly and broadly. Consider how to support community work with GLAM institutions for countries without chapters.	Response on FDC Talk page AP changes: None at this time; considering adding more detail to GLAM project plan
Community Engagement – Program 6: Support Affiliations Committee and affiliate partnerships PC&L Consider how to support AffCom with tough issues in a way that is constructive and not demoralizing. Same with Langcom.	Response on FDC Talk page
Community Engagement – Program 7: Improve collaboration with communities in product development Technical Collaboration Give clear guidance on state of Affiliate tools development. Be clear when/if WMF will take over support of tools developed by Affiliates.	Response on FDC Talk page
Community Engagement – Program 8: Connect volunteer developer work with community technical needs Community Tech Positive - no action recommended	None
Community Engagement – Program 9: Identify support gaps and provide targeted resources SuSa Inspire campaigns may be too frequent. Consider one per year. "However, it seems like a thematically designed grant program; the process and support is the same; and this seems to put a limitation on other grant applicants who are not interested in the inspire campaign; these applications could be processed in parallel with the inspire campaign."	Response on FDC Talk page
Community Engagement – Program 10: Maintain quick public response time and expand community surveys SuSa. PC&L Need to clarify – too vague, especially around survey support and followup	Response on FDC Talk page AP changes: Clarifications made.
Community Engagement – Program 11: Protect our users, staff, and public SuSa Program needs to be more visible. Example emergency@ address is unknown. Consider merging this program with functionaries' training (program 2)	Response on FDC Talk page AP changes: Clarifications made (new objective added). Team declined to merge programs to better distinguish between the two.
Product (in general) Need more editing tools. Need to improve tools for administrative actions. Link the storyline between research/analysis across the depts. - Why, what benefit, potential of what is being investigated. Avoid redundancy and express how to keep institutional knowledge.	AP changes: Overall goals/objectives clarified. Editing tools clarified. New research section added at the beginning. Product overview shows how teams collaborate.
Product – Program 1: Better understand our users Reading, Editing, Discovery Add clear and tangible goals. The purpose of the research is not clear enough, too academic and not practical enough. Need clear definition of the research being done. Need to consider using outside institutions to conduct research (local - New Readers noted here).	AP changes: Program introduction added to clarify how the research impacts product development specifically, rather than generally. Links added to give more information on research in progress.
Product – Program 2: Maintain and improve content discovery Discovery Search functionality - agrees it is appropriately reflected here. Add better metrics for Maps, Graphs. Question regarding definition of Program vs. Operations – FDC thinks Search APIs should be considered operational	Αλλαγές ΑΡ: More information on Maps and Graphs with clearer targets. No changes to how programs are described (comment about separating operations from programmatic work) - this requires a bigger conversation with FDC for next planning cycle.
Product – Program 3: Increase our global reach by increasing readership Ανάγνωση G2 - good but need to engage more with community, since work being done locally. Need to go beyond Encyclopedia to consider sister projects and demand for other UX. G3 - New Readers - concerns how the countries are selected (some already engaged and not working - Mexico, India), how will these be built better?, how will others be addressed? Need research on how this will grow. G4 - Suggests there is not enough data to support hypothesis given.	Αλλαγές ΑΡ: Program introduction added to clarify. G1 - minor adjustments. G2 - no changes to plan, taking comment regarding engagement under advisement. No capacity to go beyond Encyclopedia in FY16-17. G3 - προστέθηκαν σύνδεσμοι με περισσότερες λεπτομέρειες. G4 - Goal introduction added to give more information about the hypothesis.
Product – Program 4: Maintain and improve content creation and editing tools Επεξεργασία G1 - good, but need tie to WikiData. VisualEditor needs to be fixed on desktop first before mobile. Start working on admin and curation tools for mobile.	Αλλαγές ΑΡ: Some goals/objectives rearranged for better clarity of intent of work. Original G3 was removed. Work with Visual Editor on both platforms described more fully. New objective added "Guiding edits" for visual and wikitext editors. Due to capacity, no additional work added beyond what is now listed.
Product – Program 5: Maintain and build contributor tools Community Tech Good, but need to add in clear targets and detailed objectives to meet these goals.	Αλλαγές ΑΡ: Προστέθηκε εισαγωγή. G1 links for more specific targets and details and timelines on how these goals will be executed.
Τεχνολογία (γενικά) Link more with Product, clearly spelling out connections and differences. Add in more specific metrics, besides end of year. Need to better represent, since 60 people - large percentage.	Αλλαγές ΑΡ: Information added to introduction to describe how Product and Technology collaborate. More detail added throughout.
Technology – Program 1: Improve tools that help us understand user needs Analytics Good, but add in research to understand past failure to accomplish this goal.	AP changes: Program introduction added. Link to Analytics' projects added for more detail.
Technology – Program 2: Expand research capabilities Research and Data, Technical Operations, Design Research G1, 2 – seems too high level. Link to other research and show how they all integrate. G3 – Obj 1, 2 – clearly link to the New Readers program.	Αλλαγές ΑΡ: G2 & G3 – revised targets added. Link to New Readers program added. As a service to mainly Product, work is dependent on needs of the Product org, so specific research is built based on the needs of the research questions. Team is equipped with many methodologies to complete research to test hypotheses or glean the appropriate insights. New G4 added (improve cross-communications), moved from Product Program 2. Links added. Note Research section added to introduction of all Programs, to better describe how the research teams all work together.
Technology – Program 3: Improve site reliability Technical Operations, Security, Architecture, Technology Services G1 good, but need to add in metrics, milestones, targets. G2, Obj 1 – define targets. G2, Obj 2 – good but communicate it more broadly.	Αλλαγές ΑΡ: G1 and G2 objective targets were added where possible.
Τεχνολογία- Πρόγραμμα 4: Βελτίωση της επίδοσης του site Επίδοση, Τεχνικές Εργασίες Best written in Technology. Exemplary program.	Κανένα
Technology – Program 5: Expand the way software is tested Release Engineering Well presented, defined. Suggests adding more than 1 goal for this team of 7.	Αλλαγές ΑΡ: New goals are being developed and will be added to the June 6 revision.
Strategic Partnerships (in general) Describe the scope of Strategic Partnership and how it interacts with other departments (what is and isn't done). Clarify what happens when there is a pre-existing movement partnership in place. Finds it problematic to have both "corporate donations" (receiving money) and content-deals under one team.	Απάντηση στη σελίδα συζήτησης FDC: This explains why the team is the primary point of contact discussing both corporate donations and content-deals (mainly because initial meetings are exploratory in nature and this is unknown at the onset). Αλλαγές ΑΡ: Introduction of Strategic Partnerships group added to describe scope and how it functions with other departments, this includes how they work when there is a pre-existing movement partnerships in place.
Strategic Partnerships – Program 1: Increase partnerships and promotions Strategic Partnerships Positive. Success here could be huge for movement.	Αλλαγές ΑΡ: Clarification added, so this work is not confused with Global Reach team.
Strategic Partnerships – Program 2: Carefully grow Wikipedia Zero Global Reach FDC supports the program, need balance between free access and equity of access. Doesn't know if phone surveys are an effective use of time/effort. Consider other survey methodologies or outsource. Pleased to see community involvement, since needs to be on-the-ground. Need to develop longer-term plan, since Zero is never intended as a solution to the problem.	Απάντηση στη σελίδα συζήτησης FDC: This includes specifics on how the team works as a bridge until the local efforts are firmly established and Zero is no longer needed. Αλλαγές ΑΡ: More details added around the local telephone service provider, why telephone surveys work particularly well for this research.
Strategic Partnerships – Program 3: Increase reach through new types of partnerships Global Reach New partnerships need to be clarified so it can be better understood and measured.	Απάντηση στη σελίδα συζήτησης FDC Αλλαγές ΑΡ: Οι λεπτομέρειες που αφορούν τους τέσσερις τύπους συνεργασίας έχουν προστεθεί.
Επικοινωνίες (γενικά) Need to clarify plans and goals, especially around WMF brand vs. movement brands. Goals/programs are repeated, sometimes inconsistent (blog referenced). Add in critically missing collaboration with community media contacts and chapters. Potentially add in program to empower, train, and support them.	Απάντηση στη σελίδα συζήτησης FDC Αλλαγές ΑΡ: Clarification added on how this integrates with the strategic plan and concrete separation of WMF brands vs. movement brands. Overall clarification to goals and any repetition. Because ongoing collaboration with chapters and media contacts is part of the daily work, it is not spelled out as a separate, specific goal. However, when applicable, this is integrated into the existing goals and objectives.
Communications – Program 1: Improve public understanding and appreciation for Wikimedia movement and projects Communications Κανένα	Κανένα
Communications - Program 2: Make our brand more consistent, relatable, and more easily understood Επικοινωνίες G2 is outward focused, but its objectives are too inward focused.	Απάντηση στη σελίδα συζήτησης FDC Αλλαγές ΑΡ: Program has been clarified with new overall program detail, changes to G2, objective 1. Also, a new G2, objective 3 has been added (Continue to develop brand strategy for the Wikimedia movement).
Communications – Program 3: Identify and build understanding of new audiences Επικοινωνίες Κανένα	Κανένα
Communications – Program 4: Increase awareness and product adoption among specific audience segments Επικοινωνίες Clarify target audiences, how content distribution can be effective, if social media is the right platform.	Response on FDC Talk page AP changes: More detail added to G1 to clarify the target audiences. This was also adjusted to help clarify Communications' role in the New Readers work. More detail on the social media given.
Communications – Program 5: Grow and improve audience and engagement on the Wikimedia Foundation’s digital channels Επικοινωνίες G1 – Add more qualitative info on reach and engagement – not just numbers. Q on why instagram account is important vs general brand. Clarify how / when WMF-operated social media is promoting the organization or the movement brand. G1, Obj 2: Collaborate with other chapters and community members who have already done that in the past. G2, Obj 3: Clarify to what extent the WMF is distributing their materials via commons as well as social media channels.	Απάντηση στη σελίδα συζήτησης FDC Αλλαγές ΑΡ: More detail given throughout. G1 – more information added on reach to community members through Facebook and other platforms. G1 and G2 objectives were clarified.
Legal (in general) Publish more information about the support that it does / does not provide to the Board of Trustees, particularly in terms of trustee candidate vetting, trustee selection, and trustee orientation.	Taking this under advisement.
Legal – Program 1: Protect project trademarks and practices Legal Clarify support given to smaller recognized Affiliates	Απάντηση στη σελίδα συζήτησης FDC AP changes: small clarifications made
Legal – Program 2: Support community members in unfair litigation while defending our mission Legal Κανένα	Κανένα
Legal – Program 3: Protect the communities’ discretion in determining proper content Legal Κανένα	Κανένα
Legal – Program 4: Join with the Wikimedia communities in advocating for policy positions relevant to the work of the communities Legal Public Policy Portal is important, but it needs to be more visible, will stimulate more discussion to formulate opinions.	Απάντηση στη σελίδα συζήτησης FDC AP changes: small clarifications made
Legal – Program 5: Maintain transparency in our defense of content and user privacy Legal Consider if any of the private information shared with FDC could be made public, in that it greatly illustrates the value of the services Legal gives	Απάντηση στη σελίδα συζήτησης FDC
Non-programs – Fundraising Advancement Excellent work. May benefit from a better coordination with chapters and local community to reduce conflicts. This could be good to do this year...	Κανένα
Non-programs – Fundraising Tech Εξαιρετική δουλειά.	Κανένα
Non-programs – Talent and Culture T&C Add what their goals around global diversity are, since this needs work. Add more info on its work with recruiting trustees, especially around global diversity.	Σημειώσεις: Ensuring diversity of trustees is not a T&C responsibility. The board is tasked with recruiting trustees, although T&C is available to advise and assist in the process. T&C's year-long diversity program was designed to be more agile for the year, adapting as they dive into the issue, starting with: FQ1 - set alliance committee, set baseline metrics, set foundation of staff understanding & awareness, and set plan for manager training.
Non-programs – Team Practices Ομαδικές Πρακτικές Expand role to include more non-technical groups and departments	Σημείωση: Action already taken; a new role was created and filled in team, focused on possible new work in these areas.
Non-programs – Finance and Administration Provide leadership and guidance to other movement entities, as well as learning from those entities, to become a model of excellence in its area of expertise.	Απάντηση στη σελίδα συζήτησης FDC See general note regarding Finance & Staffing
Non-programs – Financials: FY 2016-17 Finance Overall request for more detailed, specific budgets tied to programs.	Απάντηση στη σελίδα συζήτησης FDC See general note regarding Finance & Staffing