Draft scope
UX Recommendations for the design and development of a centralized location for moderators, and the workflows or processes that could be most impactful to centralize there.
- Wikipedia only
- Editors who are not new to editing, but are new to some moderation workflows and tasks. The product may expand to include editors who are completely new to doing moderation work as well.
- We expect to focus on a limited number of WPs to start. While we don't have a set list, here is some criteria to consider when choosing the languages for this study:
- While it is not decided what the central location exactly is or how it will exactly look like (hence this research), recommendations from this research should keep the path open for a potential joining of the central location and the newcomer dashboard.
Research questions we have might include:
- How do moderators decide what to work on when contributing to Wikimedia projects?
- Do they find specific areas to work in, or contribute wherever they’re needed?
- What processes and workflows do they engage in, and how do they know when contributions are required for them?
- How do they identify and track backlogs where they have skills to contribute?
- What kinds of edits do patrollers want to identify and revert, that they are currently unable to effectively locate?
- Would moderators find it helpful to have a central location which can route them to moderation needs on their wiki?
- If so, what sorts of signals or modules would they find helpful to have access to?
- What do newer patrollers find confusing or intimidating about getting further involved in content moderation processes?
- e.g. tooling, policy knowledge, finding edits to moderate, complex processes?
- What are moderators discovery or retrieval needs? Are they currently doing repetitive or cumbersome tasks related to retrieval of content? (context: this information can help us, Research, for scoping experiments related to discovery needs of editors which we would like to start experimenting with (at the service of eventually this KR or similar KRs. and to implement the AI strategy for editors.)
Priority
High. The centralized location for existing editors has a high priority for FY26, under WE.1.3. Doing the related UX research prior to the start of the FY gives the Design Research team the opportunity to raise awareness about the user needs before the work for design and development of the dashboard begins. This will assure that the PM and other decision makers have the information they need about the users and can confidently proceed.
Past work
This work will build on the learnings from Who are Moderators research (FY25-SDS.1.23) T371865 and ‘Task Prioritization’ focus area research (T381045).
Context and the text of the original request
One of the central elements of the Contributor Strategy is the notion of a centralised location for editors to discover opportunities to contribute. As part of WE1.3, the Moderator Tools team plans to test this idea with a focus on moderators: can we build a compelling central location through which editors can discover moderation workflows, or tasks requiring their attention?
To decide if this is a hypothesis we should pursue, and if so what we should build, we need to do some user research to learn more about editors’ perceptions, opinions, and challenges. This research will directly impact the work the Moderator Tools and other Contributors teams do in the coming Fiscal Year.
We want to better understand how moderators decide what to work on when contributing to Wikimedia projects. Do they find specific areas to work in, or contribute wherever they’re needed? What processes and workflows do they engage in, and how do they know when contributions are required for them? How do they identify and track backlogs where they have skills to contribute?
Stakeholder and sign-off on the Product end:
@SonjaPerry (while Sam is away)