Page MenuHomePhabricator

Communications: Constructive activation experimentation (Growth work related to Wiki Experiences 1.2)
Closed, ResolvedPublic

Description

User Story:

Specific communications user story:

  • As the Growth team Product Manager, I want to gather community feedback early in the project to ensure we develop a solution that effectively meets community needs.

Underlying user stories:

  • As a new Wikipedia account holder on mobile, I want editing workflows that are broken into a series of easy steps, so that I can successfully contribute.
  • As a new Wikipedia account holder on mobile, I want editing support that is surfaced in the moment that I need it, so that I can successfully contribute.
Task Scope:

Already completed:
✅ Shared early Growth team annual plans with the community: https://www.mediawiki.org/wiki/Growth/Annual_Plan_2024-2025
✅ Shared initial WE1.2.3 ideas with Growth team pilot wikis and more generally on MediaWiki: https://www.mediawiki.org/wiki/Growth/Constructive_activation_experimentation
✅ Shared initial ideas with Wikimania attendees: T371334: Wikimania 2024: Design review for surfacing structured tasks

Next:

  • This task: Share current status and designs with communities. (To gather the patroller and experienced Wikimedia users point of view)
    • Pilot wikis: Egyptian Arabic, Spanish and French
  • NOT this task: user testing of prototypes

Design ideas we plan to move into design prototype testing. These are the ideas that best serve our Structured Task strategy, and align with community and stakeholder feedback, and allow us to explore three very different moments in which a suggestion could be surfaced.

MomentHow might we...User targettingUILogic
Pre-edit momentHow might we encourage and support new account holders to make successful first edits?logged-in account holders with zero editsFollows the "Check Sheet" Edit Check UI, and the suggestion should load async after the article has loaded.The suggestion is dismissible, and after dismissing a suggestion (x) times we should refrain from further suggestions.
Mid-edit momentHow might we encourage and support new account holders to make successful first edits?logged-in account holders with zero editsUI follows the "Check Sheet" Edit Check UI, and the suggestion should load async after the article has loaded.If the editor starts typing before the suggestion loads, then suggestion should not display. The suggestion is dismissible, and after dismissing a suggestion (x) times we should refrain from further suggestions.
Post-edit momentHow might we motivate newcomers to make another edit?logged-in account holders with less than 10 editsPost-edit dialog that offers a suggestion for Structured Task on a related article.The suggestion is dismissible, and after dismissing a suggestion (x) times we should refrain from further suggestions.

Background

Current full-page editing experiences require too much context, patience, and trial and error for many newcomers to contribute constructively. To support a new generation of volunteers, we will increase the number and availability of smaller, structured, and more task-specific editing workflows (E.g. Edit Check and Structured Tasks). The Growth team will primarily focus on Structured Tasks, while working closely with the Editing team to ensure our work integrates well with Edit Check.

This project aims to address the following user problem: Getting started editing on Wikipedia is difficult and especially frustrating on mobile devices. I want the editing interface to provide the in-the-moment policy and technical guidance I need, so my initial efforts aren't reverted.

This project aims to achieve the following user outcome: As a new Wikipedia volunteer, I feel confident and enthusiastic about contributing to the Wikimedia movement by editing Wikipedia articles. The tools provided guide me step-by-step, limit distractions, and allow me to learn progressively so I can successfully contribute on my mobile device.

Growth team hypothesis

As part of the Growth team 2024/2025 Annual Plan, the Growth team will explore various ways to increase constructive activation on mobile. This is part of the Wikimedia Foundation 2024-2025 Annual Plan, specifically the Wiki Experiences 1.2 Key Result

Wiki Experiences 1.2 Key Result
Constructive activation: Increase in the percentage of newcomers who publish ≥1 constructive edit in the main namespace on a mobile device.

Wiki Experiences 1.2.3 Hypothesis:
If we conduct user tests on two or more design prototypes introducing Structured Tasks to newcomers within/proximate to the Visual Editor, then we can quickly learn which designs will work best for new editors, while also enabling engineers to assess technical feasibility and estimate effort for each approach.


Acceptance Criteria
  • Share communication plan with Growth PM + Ambassadors
  • Coordinate with Growth Designer if further designs are needed to help facilitate discussions
  • Coordinate with Growth Ambassadors regarding community outreaching
  • Summarize the discussions

Event Timeline

When the designs will be available at Commons, I'll start the work.

When the designs will be available at Commons, I'll start the work.

Designs have been added:
https://www.mediawiki.org/wiki/Growth/Constructive_activation_experimentation#Design

@JFernandez-WMF will you add designs in Spanish to this task? Thanks!

I just uploaded Spanish designs to Commons:

These are the designs in English, in case we want to create a category to categorize (sorry for the redundancy) them all together @Trizek-WMF

KStoller-WMF lowered the priority of this task from High to Medium.Oct 23 2024, 9:22 PM
KStoller-WMF moved this task from Current Sprint to Estimated tasks backlog on the Growth-Team board.
KStoller-WMF edited projects, added Growth-Team; removed Growth-Team (Current Sprint).

I'm moving this out of this sprint to acknowledge that we are first focusing on: T366328: Community update module: community outreach for pilot testing

This task came up when I was reviewing "Stalled tasks" in our current sprint. The Acceptance Criteria is met, although community discussions are now ongoing. Given that Growth team Ambassadors are handling the actual community discussions, should I resolve this task?

Resolving this task, as the main communication is complete.

We should reach out to pilot wikis one last time to let them know before we start the next experiment.