Page MenuHomePhabricator

Research Spike: surfacing Structured tasks
Closed, ResolvedPublic1 Estimated Story Points

Description

Main User Story:

As the Growth team's Product Manager, I want to evaluate the effort required for the various approaches we have brainstormed, so that our decision-making process includes considerations of both short-term effort and long-term maintenance costs.

Underlying User Stories:

As a new Wikipedia account holder using a mobile device, I want the editing workflow to be broken into a series of simple steps, so that I can easily and successfully contribute.
As a new Wikipedia account holder using a mobile device, I want real-time editing support to be available exactly when I need it, so that I can effectively contribute.



This task is essentially an initial research spike to explore the technical complexity of the various approaches we outline in T368187: [EPIC] Constructive activation experimentation (Growth work related to Wiki Experiences 1.2).


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
  • Review designs (from T371731) with Growth PM and Designer
  • Consult with other stakeholders & Growth engineers as needed
  • Write a short summary of the technical considerations & complexities, open questions, and provide a relative effort estimate for each idea. (I'm not expecting an estimate of points or time, just a basic comparative estimate of which ideas would require the most / least work).

Details

Other Assignee
JFernandez-WMF

Event Timeline

KStoller-WMF moved this task from Inbox to Estimated tasks backlog on the Growth-Team board.
KStoller-WMF updated Other Assignee, added: JFernandez-WMF.
KStoller-WMF set the point value for this task to 1.
Sgs raised the priority of this task from Medium to High.Aug 7 2024, 11:35 AM

For link-recommendations, this seems very related: T307902: Assess database requirements for link recommendations reading entry point. Apparently, something like that was already considered 2.5 years ago, and the take-away was "We can just cache link recommendations for all pages on all wikis, as long as we clean up space somewhere else"?

Nice Phabricator archeology! I didn't know about that task, but indeed it seems quite related!

@DMburugu - based on the discussion on T307902: Assess database requirements for link recommendations reading entry point, I wonder if we should consider T308084: Reduce DB space used by Echo notifications as a maintenance priority?

@KStoller-WMF It would be a good idea to do a spike and see how much free space we could potentially free up by implementing the approach suggested which is around removing bot generated notifications. If it turns out to be significant(> 2Gb), we can make T308084 a priority. If not, we can explore caching options to reduce DB hits as suggested in T307902

The numbers for T307902 seem fair but I'm not sure we could scale this to several types of recommendations. Would we then need to free more space in exchange? Will there always be space to free in exchange? I'd like to understand if requesting directly to the service was already discarded for a specific reason, it's unclear from the conversation in T307902 if it was due to high-traffic issues or other.

Details about the technical challenges mentioned here can be found in the document Surfacing Structured Tasks > Technical considerations section. Below is a comparative summary of the work required for each of the design prototypes evaluated, see Figma.

Read-mode, inline-tag

  • Retrieving link recommendations for a random article
  • Marking text in read mode
  • Displaying popup in read-mode

Read-mode, scroll

  • Retrieving link recommendations for a random article
  • Displaying popup in read-mode

Exiting-editor, scroll

  • Retrieving link recommendations for a random article

The Read-mode, inline-tag version seems the one that requires more work indeed. The retrieval of recommendations is a common problem that we can not avoid, at least for a production ready version of the feature. This is a problem we can start working since it doesn't depend on the design chosen. @KStoller-WMF let me know if this enough to make a decision and move forward.

Thank you, let's consider this done!
Once I add further details about next steps we can start to break out the necessary tasks: T375829: Planning: finalize and create tasks for Surfacing Structured Tasks