Wikimedia Product/2018-19 Q2 Goals

Purpose of this document: Goals for the Wikimedia Audiences department for the first quarter of fiscal year 2018–19 (October–December 2018). The goal setting process owner in each section is the person responsible for coordinating completion of the section, in partnership with the team and relevant stakeholders.

Goals for the Technology department are available on their own page.

{| class="wikitable"
 * colspan="6" |

Contributors
Goal setting process owner: Danny Horn !Annual Plan !Annual Plan Outcome !Annual Plan Output !Team !Quarterly Goal !Dependency ! rowspan="7" |New Content ! rowspan="3" |Growth
 * rowspan="3" |1: Progressive Onboarding
 * rowspan="3" |1.1: Human-to-human help
 * Objective: Open up channels for continuous learning about new editors.

Key results:

Key result: Some part of either the “Focus on help desk” intervention or “Engagement emails” intervention is in production with an experiment. ''[Decision on specific intervention is pending. Description of those interventions is here.]'' Key result: A third community beyond Czech and Korean is participating in conversations with the Growth team in their own language. !TPC working group !Editing
 * Data flowing in for “Understanding first day” with preliminary numbers posted on wiki.
 * Data flowing in for “Personalized first day” with preliminary numbers posted on wiki.
 * Czech and Korean ambassadors.
 * All teams involved in instrumentation processes (Legal, Analytics Engineering, etc.)
 * Objective: New editors interacting with an intervention geared toward increasing retention.
 * Objective: New editors interacting with an intervention geared toward increasing retention.
 * Objective: New editors interacting with an intervention geared toward increasing retention.
 * Czech and Korean ambassadors.
 * Objective: Expand the set of our engaged wikis so that we can work and learn faster.
 * Objective: Expand the set of our engaged wikis so that we can work and learn faster.
 * Objective: Expand the set of our engaged wikis so that we can work and learn faster.
 * Community Relations Specialist
 * Community members of a third community
 * 2: Communication
 * 2.1: Talk page consultation
 * 2: Communication
 * 2.1: Talk page consultation
 * Organize Talk Page Consultation working group, beginning with staff and then including volunteers.
 * Make a plan for the consultation, which will begin in Q3.
 * 3: Mobile contribution
 * 3.4: Simpler editing on mobile web
 * 3: Mobile contribution
 * 3.4: Simpler editing on mobile web
 * 3.4: Simpler editing on mobile web
 * We need to move from the discovery phase into the delivery phase by making prototypes to address the opportunities that we identified in Q1.


 * Prioritize pain points
 * Brainstorm solutions for these problems

! rowspan="2" |Language
 * Make low fidelity prototypes, run a/b tests, implement solutions
 * Engage in research focused on target audiences
 * Strategically reduce technical debt to allow for easier visual mobile editing development
 * Improve and maintain the current visual editing experience
 * rowspan="2" |4: Local Language Content
 * 4.1: Content translation
 * rowspan="2" |4: Local Language Content
 * 4.1: Content translation
 * Objective:


 * Content Translation 2 better supporting newcomer needs.

Key Result:


 * Version 2 will be the default version to use.
 * Guidance is provided for newcomers to overcome common issues.
 * Editing (technical support on VE editing surface)
 * Research (user research to learn how the tool works for newcomers)
 * Community Liaisons (announcements of new version availability and tracking feedback)
 * 4.2: Improve Translate extension & Translatewiki process
 * Objective:
 * 4.2: Improve Translate extension & Translatewiki process
 * Objective:


 * Improve the quality of translations for Translate extension

Key result:

! rowspan="2" |Community Wishlist
 * Complete key maintenance tasks captured for this area.
 * rowspan="2" |1: Productivity and satisfaction


 * 1.1: Community Wishlist

! rowspan="2" |Community Tech
 * TemplateWizard: Complete rollout to all wikis and collect metrics about impact.
 * SVG Translate project: Complete technical development  and begin rollout process.
 * Run the 2019 Community Wishlist Survey
 * All projects: Community Liaison support for rollouts.
 * All projects: Community Liaison support for rollouts.

Event Metrics: add Design, Design Research

Who Wrote That: add Design, Design Research, WikiWho (GESIS - Leibniz Institute)/Volunteer developers ! rowspan="4" |Community Health Initiative ! rowspan="4" |Anti-Harassment Tools
 * 1.2: Special projects
 * Data portability: Begin research and design exploration.
 * Data portability: Begin research and design exploration.
 * Data portability: Begin research and design exploration.
 * rowspan="4" |1: Timely, informed decisions when harassment occurs.
 * 1.2: Blocking tools
 * Objective:


 * Allow admins to apply appropriate remedies in cases of user conduct disputes

Key Result:


 * Release partial blocks to at least one willing, mature production wiki by the end of November.
 * Alex Hollander (or handoff to Prateek)
 * Wiki communities
 * 1.1: Reporting system
 * Objective:
 * 1.1: Reporting system
 * Objective:


 * Reports of harassment are higher quality while less burdensome on the reporter

Key Result:


 * With the Wikimedia community and Trust & Safety, agree to a process for generating consensus about an improved harassment reporting system.
 * Allow admins to more efficiently investigate user misconduct by designing filters for the Interaction Timeline based on findings from usability tests.
 * Trust & Safety
 * Prateek
 * N/A
 * Objective:
 * N/A
 * Objective:


 * The impact of the Anti-Harassment Tools team is measurable

Key Result:


 * Rewrite and run the 2018 Admin Confidence Survey with preliminary data ready by November 15.
 * Implement a minimum of two data measurements to evaluate the impact of our team’s work, including but not limited to blocks, Interaction Timeline, and the reporting system.
 * Edward
 * Legal
 * Analytics Engineering
 * Morten
 * N/A
 * Objective:
 * N/A
 * Objective:


 * The Anti-Harassment Tools team is more appropriately staffed

Key Result:


 * Onboard our new design researcher and our third developer.
 * Design Research
 * colspan="6" |
 * colspan="6" |
 * colspan="6" |

Design
Goal setting process owner: Nirzar Pangarkar and Margeigh Novotny !Annual Plan !Annual Plan Outcome !Annual Plan Output !Team !Quarterly Goal !Dependency !New Content ! rowspan="4" |Audiences Design
 * 3: Mobile Contribution
 * OOUI adoption for Special Pages for advance editors on Mobile Web platform
 * Adopt OOUI on top three special pages on Minerva Skin

!Communications
 * Special:Contributions
 * Special:Recent Changes
 * Special:Watchlist
 * Minor: Reading Web
 * N/A
 * N/A
 * Research and design recommendation on Wikimedia Foundation Website on following aspects

!New Readers !Platform Evolution !New Content !Audiences Design Strategy
 * Usability and navigation
 * Aesthetics and brand
 * Accessibility and performance
 * 2. Awareness: More people in target countries/languages know what Wikipedia is.
 * 2. Awareness: More people in target countries/languages know what Wikipedia is.
 * Design and develop a landing page in time for video marketing campaign in Mexico
 * Release Engineering, Security, Communications dept.
 * 2: Well encapsulated components and well defined APIs
 * 2.8: OOUI maintenance and extension
 * Maintain and extend Quarterly OOUI releases
 * N/A
 * 3: Mobile contribution
 * 3.3: Mobile Contribution Research
 * Deliverables complete
 * N/A
 * colspan="6" |
 * colspan="6" |

Programs
Goal setting process owner: Anne Gomez (New Readers and Structured Data on Commons) !Program !Annual Plan Outcome !Annual Plan Output !Team !Quarterly Goal !Dependency ! rowspan="3" |New Readers Supporting: Aud PM 2 &3, P&GR 3 &4 !Communications !Partnerships & Global Reach !Audiences Design Product
 * 2. Awareness: More people in target countries/languages know what Wikipedia is.
 * Comms 2: Marketing campaigns to support general awareness, conducted in partnership with community volunteer committee. In previous fiscal year, these have been online video campaigns.
 * Complete production and launch video marketing campaign in Mexico.
 * Partnerships & Global Reach, Program Management, external agency, WMMX
 * 2. Awareness: More people in target countries/languages know what Wikipedia is.
 * P&GR 2: Survey general population in target markets before and after awareness activities.
 * P&GR 2: Survey general population in target markets before and after awareness activities.
 * Complete baseline and endline phone surveys in Mexico to support awareness campaign (Comms 2, see above).
 * Program Management, Communications
 * 4. Retention: More people in target countries/languages find Wikipedia useful and return to it.
 * Aud 3: A series of data-driven product experiments to support better experiences of Wikipedia. [ more]
 * Aud 3: A series of data-driven product experiments to support better experiences of Wikipedia. [ more]

Engineering ! rowspan="15" |Structured Data on Commons ! rowspan="3" |Multimedia ! rowspan="5" |Community Relations ! rowspan="3" |GLAM !Search Platform !GLAM !Community Relations !Program Management
 * Deliver custom landing pages with tracking. Landing pages will be linked from awareness campaign video in Mexico.
 * Partnerships & Global Reach, Communications, WMMX,
 * rowspan="11" |1: Commons contributors can edit metadata more easily, in any MediaWiki-supported language
 * rowspan="2" |Output 1MM: Release of features that enable structured data editing and addition on the file page and as part of the media upload process.
 * Deploy multilingual file captions on Commons in October
 * rowspan="2" |Security, Core Platform, Wikidata, Community Relations
 * Refine API to manage adding/editing depicts values for 3rd party tools
 * Output 3 MM: Implementation of “Depicts” statements that make file categorization, identification, and search simpler and more granular.
 * Deploy depicts and other statements to Beta Commons
 * Wikidata, Community Relations
 * rowspan="2" |Output 1 CommRel: Facilitate community conversations and feedback requests around editing features, uploading features, and multilingual support.
 * Wikidata, Community Relations
 * rowspan="2" |Output 1 CommRel: Facilitate community conversations and feedback requests around editing features, uploading features, and multilingual support.
 * rowspan="2" |Output 1 CommRel: Facilitate community conversations and feedback requests around editing features, uploading features, and multilingual support.
 * Communicate release of multilingual file captions to communities
 * Multimedia
 * Monitor community feedback on multilingual file captions and surface issues and wins to Multimedia team
 * rowspan="6" |Output 2 CommRel: Ensure community involvement and satisfaction with development process.
 * Communicate other statements designs, computer vision assisted Depicts tagging, ImageAnnotations and Depicts to communities
 * Multimedia
 * Facilitate community conversation about property creation process for Commons properties on Wikidata, arrive at defined property creation process for Commons property requests
 * Present SDC update at WikiConNA and talk to key program organizers about their Commons programming and SDC.
 * Multimedia
 * Facilitate community conversation about property creation process for Commons properties on Wikidata, arrive at defined property creation process for Commons property requests
 * Present SDC update at WikiConNA and talk to key program organizers about their Commons programming and SDC.
 * Present SDC update at WikiConNA and talk to key program organizers about their Commons programming and SDC.
 * Present SDC update at WikiConNA and talk to key program organizers about their Commons programming and SDC.
 * Present SDC update at WikiConNA and talk to key program organizers about their Commons programming and SDC.
 * Announce and communicate relevant ongoing releases, design proposals and community conversations to the GLAM focus group and GLAM-Wiki community and solicit targeted feedback from this stakeholder group
 * Community Relations
 * Present SD update at the GLAM-Wiki conference and talk to key program organizers about their GLAM programming and SDC.
 * Community Relations
 * GLAM sector outreach on SDC at CIDOC conference (Heraklion), Shaping Access conference (Berlin) and Baltic Audiovisual Archival Council conference (Tallinn)
 * Community Relations
 * 2: People searching for media on Commons can find more relevant results faster
 * Output 1 SP: Commons search will be extended via additions to CirrusSearch and Elasticsearch and Wikidata Query Service, to support searching based on structured data elements describing media.
 * 2: People searching for media on Commons can find more relevant results faster
 * Output 1 SP: Commons search will be extended via additions to CirrusSearch and Elasticsearch and Wikidata Query Service, to support searching based on structured data elements describing media.
 * Output 1 SP: Commons search will be extended via additions to CirrusSearch and Elasticsearch and Wikidata Query Service, to support searching based on structured data elements describing media.
 * Allow search by type of license
 * Multimedia
 * 3: GLAM institutions have more reliable and less challenging workflows for sharing media files and metadata on Wikimedia Commons as part of content partnerships, allowing for increased GLAM participation.
 * Output 3 GLAM: Structured Data on Commons and its value for GLAMs is tested and demonstrated with at least 8 experimental GLAM pilot projects
 * Output 3 GLAM: Structured Data on Commons and its value for GLAMs is tested and demonstrated with at least 8 experimental GLAM pilot projects
 * GLAM pilots project plans finalized and projects announced
 * Program Management
 * 4: Developers who create and maintain key Commons tools, including volunteer developers, can transition those tools to work with structured data on Commons.
 * Output 5 CommRel: Facilitate tool transition and support volunteer tool developers.
 * Output 5 CommRel: Facilitate tool transition and support volunteer tool developers.
 * Facilitate conversations between volunteer tool and bot developers and Multimedia team
 * Multimedia
 * N/A
 * N/A
 * N/A
 * Submit mid-term financial and narrative program reports
 * Advancement, Finance
 * colspan="6" |
 * colspan="6" |

Readers
Goal setting process owner: Jon Katz !Annual Plan !Annual Plan Outcome !Annual Plan Output !Team !Quarterly Goal !Dependency ! rowspan="3" |New Content !Android Reading Infrastructure
 * rowspan="3" |3: Mobile Contribution
 * 3.3 Research-driven mobile contribution for new contributors
 * Build prototype edit action feed and begin user testing.
 * Commons (multimedia)

Research (possibly)

Legal/Finance (for user research approvals) !Infrastructure !iOS !Structured Data on Commons !Multimedia
 * 3.3 Research-driven mobile contribution for new contributors
 * 3.3 Research-driven mobile contribution for new contributors
 * Build API design specification for services needed for releasing edit action feed in Q3
 * Android
 * 3.2: Mobile for existing contributors
 * 3.2: Mobile for existing contributors
 * Deliver beta version of new syntax highlighting and improved Wikitext editing flows.
 * None
 * 1: Commons contributors can edit metadata
 * 1MM: Release of features that enable structured data editing and addition on the file page and as part of the media upload process
 * Deploy multilingual file captions on Commons in October
 * Deploy multilingual file captions on Commons in October


 * Deploy depicts and other statements to Beta Commons
 * Refine API to manage adding/editing depicts values for 3rd party tools
 * Core Platform

Release Engineering

Reading Infrastructure !New Content ! rowspan="4" |Web
 * 3: Mobile Contribution
 * 3.1: Contribution tools on mobile web via an existing mediawiki skin
 * Build navigation for advanced contributions mode and begin gathering feedback from users on target wikis
 * Build navigation for advanced contributions mode and begin gathering feedback from users on target wikis


 * Assess and design changes necessary to special pages based on user feedback and scope risk prior to development
 * Community Relations

Audiences Design ( for OOUI compatibility)

Editing !Search Engine Optimization Add Schema.org properties to pages and determine whether this increases their ranking in search results.
 * 2: Improvement and Analysis
 * 2.1: Interventions Implemented
 * Parsing

Wikidata

Performance

Community Relations !Platform Evolution !Better Encyclopedia
 * 2: Well encapsulated components and well defined APIs
 * 2.7: Refactor presentation layer away from business logic code in MediaWiki
 * Automate asset bundling in MobileFrontend/Minerva
 * Speed up unit test execution and increase code coverage
 * Speed up unit test execution and increase code coverage

(cont from 2017-2018 annual plan) !Platform Evolution !Parsing !Better Use of Data 3.2: Controlled experiment (A/B test) capabilities !Infrastructure Reading web
 * 1: Users have better experiences when interacting with articles
 * 1: Enable readers to gauge the quality and reliability of an article prior to reading
 * Complete testing and iterating on page issues feature
 * Deploy page issues feature to target wikis
 * Community Relations
 * Community Relations
 * 2: Well encapsulated components and well defined APIs
 * 2.5: Parser Unification Work
 * Port additional token and DOM transformations to PHP and evaluate performance
 * Identify a PEG.js replacement in Parsing land
 * Production use of Parsoid Language Converter for read views of phase 2A and 2B languages
 * Production use of Parsoid Language Converter for read views of phase 2A and 2B languages
 * 3: Data collection
 * 3.1: Instrumentation
 * Determine changes necessary to current tooling and libraries based on feedback from internal users
 * Bring Audiences requirements to Analytics engineering for incorporating into their TEC2: Modern Event Platform, Outcome 1
 * Analytics engineering
 * Analytics engineering

Data analysts !Platform Evolution !Infrastructure iOS
 * 2: Well encapsulated components and well defined APIs
 * 2.7: Refactor presentation layer away from business logic code in MediaWiki
 * Deploy beta of the mobile-html and data/{js,css} services
 * Write down production deployment plan with apps and platform team
 * Android
 * Android

Platform
 * }
 * }