Wikimedia Product/2018-19 Q2 Goals

Wikimedia Audiences Goals, FY2018–19, Q2 (October-December)

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.

Contributors

Goal setting process owner: Danny Horn

Annual Plan Outcome	Annual Plan Output	Team	Quarterly Goal	Dependency
New Content Outcome 1: Progressive Onboarding	Output 1.1: Human-to-human help	Growth	Collect "Understanding first day" data from instrumentation, and post early numbers on wiki. Collect "Personalized first day" data from user input, and post early numbers on wiki. "Focus on help desk" intervention experiment in production. A third community beyond Czech and Korean is participating in conversations with the Growth team in their own language.	Czech and Korean ambassadors. All teams involved in instrumentation processes (Legal, Analytics Engineering, etc.)
New Content Outcome 2: Communication	Output 2.1: Talk page consultation	TPC working group	Organize Talk Page Consultation working group, beginning with staff and then including volunteers. Phase 0 of the consultation: Agree on the principles and process of the upcoming work.
New Content Outcome 3: Mobile contribution	Output 3.4: Simpler editing on mobile web	Editing	Prioritize pain points of visual editing on mobile, and design interventions. Create low-fidelity prototypes and run tests for first set of interventions. In order to decrease regression errors and improve future development speed, increase unit test coverage of the content editable code in the visual editor to 80%. Improve the visual editor load time for desktop and mobile by 100ms.
New Content Outcome 4: Local Language Content	Output 4.1: Content translation	Language	Provide guidance for newcomers to overcome common issues in Content Translation 2. Content Translation 2 becomes the default experience (still in beta).	Editing (technical support on VE editing surface) Research (user research to learn how the tool works for newcomers) Community Relations Specialists (announcements of new version availability and tracking feedback)
New Content Outcome 4: Local Language Content	Output 4.2: Improve Translate extension & Translatewiki process	Language	Improve the quality of translations for Translate extension by completing key maintenance tasks captured for this area.
Community Wishlist Outcome 1: Productivity and satisfaction	Output 1.1: Community Wishlist	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 Relations Specialists support for rollouts. Event Metrics: Design, Design Research
Community Wishlist Outcome 1: Productivity and satisfaction	Output 1.2: Special projects	Community Tech	Data portability: Begin research and design exploration.
Community Health Initiative Outcome 1: Timely, informed decisions when harassment occurs.	Output 1.1: Reporting system	Anti-Harassment Tools	Agree to a process for generating consensus about an improved harassment reporting system with the Wikimedia community and Trust & Safety. Allow admins to more efficiently investigate user misconduct by designing filters for the Interaction Timeline based on findings from usability tests.	Trust & Safety Prateek Wiki communities
	Output 1.2: Blocking tools		Release partial blocks to at least one willing, mature production wiki.	Trust & Safety Prateek
			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

Design

Goal setting process owner: Nirzar Pangarkar and Margeigh Novotny

Annual Plan Outcome	Annual Plan Output	Team	Quarterly Goal	Dependency
New Content, Outcome 3: Mobile Contribution	OOUI adoption for Special Pages for advance editors on Mobile Web platform	Audiences Design	Adopt OOUI on top three special pages on Minerva Skin Special:Contributions Special:Recent Changes Special:Watchlist	Minor: Reading Web
---	---	Audiences Design	Research and design recommendation on Wikimedia Foundation Website on following aspects Usability and navigation Aesthetics and brand Accessibility and performance
New Readers	2. Awareness: More people in target countries/languages know what Wikipedia is.	Audiences Design	Design and develop a landing page in time for video marketing campaign in Mexico	Release Engineering, Security, Communications dept.
Platform Evolution	OOUI maintenance and extension	Audiences Design	Maintain and extend Quarterly OOUI releases	n/a
Mobile Editing	Mobile Contribution Research	Audiences Design Strategy	Deliverables complete	n/a

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
New Readers	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. Supporting: Aud PM 2 &3, P&GR 3 &4	Communications	Complete production and launch video marketing campaign in Mexico. task T193412	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.	Partnerships & Global Reach	Complete baseline and endline phone surveys in Mexico to support awareness campaign (Comms 2, see above). task T193590	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]	Audiences Design, Product, Engineering	Deliver custom landing pages with tracking. Landing pages will be linked from awareness campaign video in Mexico. task T200289	Partnerships & Global Reach, Communications, WMMX,
Structured Data on Commons	1: Commons contributors can edit metadata more easily, in any MediaWiki-supported language	Output 1MM: Release of features that enable structured data editing and addition on the file page and as part of the media upload process.	Multimedia	Deploy multilingual file captions on Commons in October	Security, Core Platform, Wikidata, Community Relations
				Refine API to manage adding/editing depicts values for 3rd party tools	Security, Core Platform, Wikidata, Community Relations
		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
		Output 1 CommRel: Facilitate community conversations and feedback requests around editing features, uploading features, and multilingual support.	Community Relations	Communicate release of multilingual file captions to communities	Multimedia
				Monitor community feedback on multilingual file captions and surface issues and wins to Multimedia team
		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	Commons and Wikidata communities
				Present SDC update at WikiConNA and talk to key program organizers about their Commons programming and SDC.
			GLAM	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.	Search Platform	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	GLAM	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.	Community Relations	Facilitate conversations between volunteer tool and bot developers and Multimedia team	Multimedia
	None	None	Program Management	Submit mid-term financial and narrative program reports	Advancement, Finance

Readers

Goal setting process owner: Jon Katz

Annual Plan Outcome	Annual Plan Output	Team	Quarterly Goal	Dependency
New Content	3.3 Research-driven mobile contribution for new contributors	Android	Build prototype edit action feed and begin user testing.	Commons (multimedia) Reading Infrastructure Research (possibly) Legal/Finance (for user research approvals)
New Content	3.3 Research-driven mobile contribution for new contributors	Infrastructure	Build API design specification for services needed for releasing edit action feed in Q3	Android
New Content, Outcome 3: Mobile Contribution	Output 3.2: Mobile for existing contributors	iOS	Deliver beta version of new syntax highlighting and improved Wikitext editing flows.	None
Structured Data on Commons	Output 1MM: Release of features that enable structured data editing and addition on the file page and as part of the media upload process	Multimedia	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, Outcome 3: Mobile Contribution	Output 3.1: Contribution tools on mobile web via an existing mediawiki skin	Web	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, Outcome 2: Improvement and Analysis	Output 2.1: Interventions Implemented	Web	Add Schema.org properties to pages and determine whether this increases their ranking in search results.	Parsing Wikidata Performance Community Relations
Platform Evolution CDP, Outcome 2: Engineers are able to access more functionality of the stack using well encapsulated components and well defined APIs	Output 2.7: Refactor presentation layer away from business logic code in MediaWiki	Web	Automate asset bundling in MobileFrontend/Minerva Speed up unit test execution and increase code coverage
(cont from 2017-2018 annual plan), Outcome 1: Users have better experiences when interacting with articles across mobile and desktop Web platforms, measured through a combination of metrics focused on user retention, pageviews, and time spent on page	Objective 1: Enable readers to gauge the quality and reliability of an article prior to reading	Web	Complete testing and iterating on page issues feature Deploy page issues feature to target wikis	Community Relations
Platform Evolution CDP, Outcome 2: Engineers are able to access more functionality of the stack using well encapsulated components and well defined APIs	Output 2.5: Parser Unification Work	Parsing	Port additional token and DOM transformations to PHP and evaluate performance
Platform Evolution CDP, Outcome 2: Engineers are able to access more functionality of the stack using well encapsulated components and well defined APIs	Output 2.5: Parser Unification Work	Parsing	Identify a PEG.js replacement in Parsing land
Platform Evolution CDP, Outcome 2: Engineers are able to access more functionality of the stack using well encapsulated components and well defined APIs	Output 2.5: Parser Unification Work	Parsing	Production use of Parsoid Language Converter for read views of phase 2A and 2B languages
Better Use of Data - Outcome 3: Data collection	Output 3.1: Instrumentation Output 3.2: Controlled experiment (A/B test) capabilities	Infrastructure	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 Reading web Data analysts
Platform Evolution CDP, Outcome 2: Engineers are able to access more functionality of the stack using well encapsulated components and well defined APIs	Output 2.7 Refactor presentation layer away from business logic code in MediaWiki	Infrastructure	Deploy beta of the mobile-html and data/{js,css} services Write down production deployment plan with apps and platform team	Android iOS Platform