Page MenuHomePhabricator

Movement Communications: Improve Tone Structured Task
Closed, ResolvedPublic

Description

User story & summary:

Task-specific user story:
As the Growth team’s Product Manager, I aim to ensure we engage with communities early and consistently throughout the product development cycle. Gathering feedback at each stage helps us expose risks and create better outcomes by building with the community.

High-level project-specific user story:
As a newcomer to Wikipedia, I want to receive suggestions that help me identify and improve non-neutral language in articles so that I can make constructive contributions that align with Wikipedia’s MOS, encyclopedic tone, and neutrality standards.

Guiding Key Result: WE1.1: Increase constructive edits (edits that are not reverted within 48 hours of being published) for editors with less than 100 cumulative edits.

Dependency: T392283: Q1 FY2025-26 Goal: Apply the Tone Check model to published articles, to learn whether we can build a pool of high-quality structured tasks for new editors

Project description:

This project aims to support newcomers by introducing a new Structured Tasks that focuses on identifying and improving non-neutral language in articles. Specifically, it will highlight sentences that contain peacock terms, puffery, promotional language, or other wording that conflicts with Wikipedia’s policies on neutrality and encyclopedic tone.
Powered by the Machine Learning “Tone” model (formerly called the “Peacock” model), with UX that builds upon the Edit Check UI, this Structured Task will highlight instances of biased language and offer in-context guidance to help users rewrite a sentence in a more encyclopedic tone. The goal is to encourage constructive, policy-aligned contributions while helping newcomers build confidence and awareness of core content standards.
This work builds on the Growth team’s broader strategy to lower barriers to editing through Structured Tasks. In Q1, we aim to release a beta version to lay the groundwork for future experiments evaluating the task’s impact on newcomer contributions and the scalability of Edit Check as a foundation for Suggested Edits.

Project-level Hypothesis:

If we provide newer editors with a Suggested Edit that highlight instances of non-neutral language or improper tone, and offer built-in guidance to rewrite with a more encyclopedic tone, then newer editors will be more likely to make constructive contributions that align with Wikipedia’s policies, while building confidence and awareness of core content standards.​​

Background & research:

Writing in a neutral tone is a pillar of Wikipedia. Writing in a neutral tone is also a practice many new volunteers find to be unintuitive. An October 2024 analysis of the new content edits newer volunteers published to English Wikipedia found:

  • 56% of the new content edits newer volunteers published contained peacock words.
  • 22% of the new content edits newer volunteers published that contained peacock words were reverted

New content edits containing peacock words were 46.7% more likely to be reverted than new content edits without peacock words
Edit_check/Tone_Check#Background

Suggested Edits help new account holders get started editing:

Acceptance Criteria:
  • Create a succinct communications plan to share this work with communities.
  • Support Product Ambassadors in their work sharing ideas and collecting feedback.

Event Timeline

KStoller-WMF triaged this task as Medium priority.
KStoller-WMF moved this task from Inbox to Estimated tasks backlog on the Growth-Team board.

Idea raised by @ppelberg:
Could this discussion be aided by including an invitation for experienced volunteers to try the PoC Suggestion Mode (w/ Tone Check enabled) the Editing Team is building in T399612: Create VE Suggestion Mode MVP.

KStoller-WMF renamed this task from Movement Communications: Improve Tone Suggested Edit to Movement Communications: Improve Tone Structured Task.Aug 22 2025, 9:56 PM
KStoller-WMF updated the task description. (Show Details)
Edtadros subscribed.

This task’s QA is covered under the combined “Revise Tone / Improve Tone Structured Task” QA in T401195, which will validate both T401195 and T399982 flows.

KStoller-WMF updated the task description. (Show Details)

I think we can consider this task resolved, enwiki communications will be handled at a later date.