Lista de experimentos en Producto y Tecnología
Esta lista de experimentos busca ser una vista centralizada de los experimentos del departamento de Producto y Tecnología.
Cada experimento incluye una breve descripción del problema que buscamos resolver, el tipo de experimento, la población seleccionada y otros aspectos clave de cada trabajo. Esta página es un trabajo en curos y será actualizada regularmente.
Acerca de esta lista
Los experimentos se enlistan de acuerdo con su estatus:
- Próximos: El experimento está siendo diseñado y configurado para la recolección de datos. Estamos preparando todo y estableciendo qué queremos probar, y cómo lo mediremos. No está activo.
- En Curso: El experimento ha sido desplegado y está recolectando datos de interacción con tráfico especificado en wikis definidas. El experimento está activo por un lapso de tiempo predeterminado.
- Análisis: El dueño o la dueña del experimento están revisando los resultados y perspectivas de la comunidad.
- Decisión: El dueño o la dueña del experimento han llegado a una decisión, que será documentada en el campo de Resultados (Outcome) y típicamente estará definido en una de tres categorías:
- «Impleméntalo» — Se recomienda el lanzamiento de la versión ganadora
- «No lo implementes» — Los resultados muestran que la función no se comportó como se esperaba, no se implementará.
- «Necesitamos aprender más» — Los resultados no son concluyentes, son necesarias otra prueba, retroalimentación cualitativa, o una siguiente iteración
Experimentos
Próximos
| Experimento | Equipo | Tiempo previsto | Tipo de experimento | Público objetivo | Problema a resolver / por qué hacemos esto | Comparta su opinión |
|---|---|---|---|---|---|---|
| Test methods for email confirmation enforcement for new accounts, when the user chooses to provide an email address during account creation | PSI | Late August 2026 | A/B Test | New users registering for web accounts, who choose to provide an email address. | Today, users can create an account with an attached email address, without confirming that they control that address. This means that many email addresses attached to new accounts remain unconfirmed, and so we cannot treat them as reliable for account recovery, security notifications, reminders, or other important communications. The current model also leaves room for preventable misuse involving invalid, third-party, or repeatedly reused email addresses. On English Wikipedia, 52.63% of new accounts that provided an email address confirmed it.
The experiment would test methods for email confirmation enforcement for new accounts, when the user chooses to provide an email address during account creation. It would not require users to provide an email address, but would require confirmation if they do provide an email address. The purpose of the experiment is to determine which approach (upfront enforcement, or delayed enforcement) is the most effective at driving email confirmation, and is the least likely to create less negative impact on retaining active readers and editors. The results will provide directional evidence on which enforcement approach is more appropriate and where to focus further engineering investment. |
|
| Surface the availability of edit suggestions on articles to logged-in readers via controlled experiment | Editing | October 2026 | A/B test | TBD; registered users with ≤100 cumulative edits | As a logged-in Wikipedia reader who has edited before, does not do so regularly, and is arriving on-wiki seeking to learn about something/someone (broadly defined), I would value knowing when there are clear, actionable, and personally relevant improvements available within the article I am reading so that I can easily decide which (if any) I'd like to act on in this moment without needing to seek them out myself.
Hypothesis: If we surface the availability of edit suggestions on articles to logged-in readers through a controlled experiment, there will be a ≥# increase in the proportion of distinct registered users with ≤100 cumulative edits who publish at least one constructive edit (mobile). |
|
| Streamline the toolbelt on Minerva (Minimal Minerva) | Reader Growth | Experiment runs from end August | A/B Test | Logged out Readers | If we streamline the toolbelt on Minerva, we will see practically significant improvement to logged-out reader retention. | |
En Curso
| Experiment | Team | Anticipated Timing | Experiment Type | Audience | Problem to solve / why we are doing this | Share your feedback |
|---|---|---|---|---|---|---|
| Introduce a new content type in Apps home | Reader Experiences Apps | 20 August- experiment is live | A/B test | Logged in Readers (Apps) | This test is part of Phase 2 of the revamp of the App's Explore feed, where we're testing out new additions to Home, with the goal of increasing daily returns to the app. This was also mentioned in a recent community wish | |
Análisis
| Experiment | Team | Experiment Timeline | Experiment Type | Audience | Problem to solve / why we are doing this | Share your feedback |
|---|---|---|---|---|---|---|
| Reader → Contributor Attribution Extended Experiment #1
Build on the successful baseline experiment of reader-to-contributor registration rates across traffic sources (e.g. search, social media, AI assistants, and other referral channels). |
Various teams involved in Key Results IR1 and IR2 | Early June – Mid July 2026 | Invisible (no discernable UI change) | Sampled anonymous readers across Wikipedia projects, sampling the top 50 largest Wikipedias | Wikimedia would like to understand how different types of readers become contributors. This experiment instruments a privacy-preserving pipeline to estimate reader-to-contributor conversion rates across traffic segments such as referrer source and device class. Building on the successful Reader → Contributor Attribution Baseline Experiment, this extended experiment expands data collection to improve estimate precision, evaluate additional traffic segments, and provide deeper insight into how readers become contributors. Findings will inform future reader-to-contributor research and product decisions related to contributor growth. |
``` |
Decisión
| Experiment | Team | Experiment Timeline | Experiment Type | Audience | Problem to solve / why we are doing this | Share your feedback | Outcome |
|---|---|---|---|---|---|---|---|
| Guide Temporary Account users toward full account creation | Contributor Growth | Start Date: 2026-06-30
End Date: 2026-07-31 |
A/B test | 50% of temp account holders on French, Arabic, Spanish, and English Wikipedias | Temporary Accounts lower the barrier to starting an edit, but they also limit our ability to support and retain contributors over time. Temporary Account users cannot receive email, and experienced editors have fewer ways to teach, mentor, or follow up with them. In addition, we do not consistently communicate the benefits of creating a full account, nor do we guide Temporary Account users toward registration at moments when motivation is likely to be highest.
Early data from the Temporary Accounts banner suggests there are opportunities to better align messaging, timing, and presentation with user intent and readiness. The current experience does not clearly explain why creating a full account is valuable, nor does it prompt users to register at moments that feel relevant and motivating. As a result, many Temporary Account users continue editing without converting, limiting long term engagement, community connection, and retention. |
Ship it!
Experiment results show that the treatment group is 87% more likely to create an account than the control. | |
| Guided article creation
Help new editors easily understand and apply the existing practices and policies, and navigate the task of starting a new article with ease. |
Language and Product Localization | May-June 2026 | A/B test | 50% of users on Simple English, French, Turkish, Wikipedias | Currently, editors need to make a significant effort to create new content from scratch. As a result, reviewers have to process many low quality contributions and revert/fix them. Finally, readers see content creation as a mystery, which makes it harder for them to decide to become contributors in the future. | Ship it!
We observed a statistically significant +17.2% relative improvement in 30-day article survival rate (p=0.033, CI +1.1% to +25.0%), covering mobile and desktop combined across all editor experience levels. This confirms the feature has real positive impact and justifies continued investment. Reaching statistical significance specifically for junior editors on mobile requires either a longer window or a larger wiki set. | |
| Suggestion Mode MVP | Editing | May-June 2026 | A/B test | 50% of users on English, French, German, Japanese, Spanish, Russian, Polish, Dutch, Hebrew, Arabic, Czech, Swedish, Korean, Chinese, Vietnamese Wikipedias | Hypothesis: If we present junior contributors who enter the mobile VisualEditor with immediately actionable edit suggestions, then the proportion of edit sessions that result in someone publishing a constructive edit will increase by >=10%. | Ship it!
| |
| Redesign account creation form on mobile web
Redesign the mobile web account creation form to follow Codex guidelines and reduce visual and cognitive complexity. The updated design shortens explanatory text, improves layout, and allows users to view all required fields on a typical mobile screen without scrolling. |
Contributor Growth | Start Date: 2026-04-13
End Date: 2026-06-27 |
A/B test | 10% of traffic to auth.wikimedia.org | As a mobile web user, I want a cleaner and less verbose account creation form so that I can view all required fields at a glance without scrolling, and complete registration with reduced information overload. | Ship it!
The results were clear and positive. Users who saw the redesigned form created permanent accounts at a rate of 20.4%, compared to 16.4% in the control group. That works out to a 24.4% relative increase in the account creation rate, far exceeding our hypothesis goal of a 2% increase, and the experiment reached a 100% chance of winning. The 95% confidence interval for the increase is entirely positive, ranging from 13.7% to 35.1%. In other words, while our best estimate of the lift is 24.4%, even the most conservative end of the plausible range is a 13.7% increase, still well above our 2% goal. This gives us strong confidence that the improvement is real rather than a product of chance. | |
| Incident Reporting System enwiki trial | Product Safety and Integrity | May-June 2026 | Progressive rollout | Logged-in users on English Wikipedia | The Incident Reporting System (IRS) is being introduced to help contributors more easily find the right place to seek help when facing harassment or other issues. We are doing this because deploying IRS to the English Wikipedia requires special care, given its size and existing processes. The purpose of this trial is to generate real-world data on how the system performs in this environment. Through a controlled, limited rollout, we aim to evaluate how the system is used and whether it operates without introducing significant additional burden on functionaries. This data will inform whether IRS is effective and suitable for broader use on English Wikipedia. |
Remain on English Wikipedia.
We completed the trial, and ended up showing the Report button to 100% of eligible users for the last two weeks of the trial. During the trial, the tool did not generate a high volume of reports overall, but we also did not seen signs or hear concerns of volunteer disruption. After public feedback from English Wikipedia functionaries and other volunteers, we have left the incident reporting system enabled on English Wikipedia going forward. | |
| Reference Previews Improvement
An experiment to test whether we can serve readers better when a footnote click in read mode shows the full bibliographic information rather than flying them to the reference list. |
Technical Wishes (WMDE) | June 17 to July 1, 2026 | A/B test | 10% of desktop for logged-in and logged-out readers/contributors on German, Swedish, Farsi, Hindi, Somali, and Western Frisian Wikipedia. | The assumption that we are testing is: Most readers who click on a footnote marker do NOT intend to navigate to the reference list. They are satisfied with viewing all the bibliographic information and details in the pop-up/in-line. | To be confirmed | |
| Add user account button to header on mobile web
Improve the discoverability of account creation on mobile web. |
Contributor Growth | Start Date: 2026-03-31
End Date: 2026-06-28 |
A/B test | 10% of users on Hindi, Indonesian, Bengali, Thai, and Hebrew Wikipedias | Account creation is not easily discoverable on mobile web. Users must open the hamburger menu to find "Log in," then close the auto-focused keyboard on the login page, and scroll to the bottom to discover the "Create account" option.
A analysis of the top 20 most visited websites shows that nearly all platforms display a way to create a account directly from the homepage ( |
Ship it!
We observed that adding a user account button to the mobile web header increased permanent account creation by approximately 20.2% relative to the control group, substantially exceeding the hypothesis target of a 2% increase. As a result of this work, we will roll out the feature to all wikis on mobile web through T428220: Scale Mobile Account Menu to All WMF Wikis | |
| Revise Tone structured task
Support newcomers by introducing a Suggested Edit that focuses on identifying and improving non-neutral language in articles. [includes a machine learning model] |
Contributor Growth | Start Date: 2026-03-31
End Date: 2026-04-16 |
A/B Test | 50% of users on English, French, Arabic, and Portuguese Wikipedias | Writing in a neutral tone is a pillar of Wikipedia, but is a practice many new volunteers find to be unintuitive. An October 2024 analysis of English Wikipedia found that 56% of new content edits from newer volunteers contained peacock words, with 22% of these edits being reverted. Revise tone structured task is a way that we can help identify and improve non-neutral language in articles, alongside other implementations of the tone check model. | Ship it!
We observed that task completion rates for Revise Tone were more than 30% higher than for Copyedit, demonstrating that a more guided and structured workflow can improve newcomer participation and task completion. We will scale the Revise Tone task to additional wikis where the Tone Check model is already supported (T426364 ) and explore expanding the Tone Check model to additional languages. | |
| Improve the logged-out warning message on mobile web
Reduce the sense of friction or alarm when users encounter the logged-out warning upon editing, and highlight the benefits of creating an account (e.g., edit attribution, watchlist, communication tools, and reputation building). |
Contributor Growth | March – June 2026 | A/B test | 10% of users on Arabic, French, Spanish, German, Russian, Chinese, Italian, Portuguese, Persian, and Polish Wikipedias
0.1 % of users on English Wikipedia |
When users attempt to edit while logged out, they encounter a jarring warning message that emphasizes editing as an IP or temporary account. This interface can feel abrupt and discouraging, and it frames logged-out editing as the primary path rather than encouraging users to create an account. There is an opportunity to soften the logged-out warning message and guide users toward account creation in a more supportive, motivating way. By improving the tone and visual hierarchy, we can better communicate the benefits of creating an account and make the overall experience less intimidating. |
Ship it!
We observed a 30.6% relative increase in account creation among exposed users. This intervention significantly exceeded the original goal of increasing account creation by a relative 2% among exposed users. We will scale the improved logged-out edit warning message to all Wikimedia wikis (T424595) | |
| Share Card
An experiment to test the usefulness of a share feature that gives readers options to create a visually compelling card about an article (or portion of an article) they are reading. They can share this card to a friend or post it on their social media. |
Reader Growth | Mid May – June 2026 | A/B test | 10% of mobile logged-out readers on Arabic, Chinese, French, and Vietnamese Wikipedias and 0.1% of mobile logged readers readers on English Wikipedia | Readers increasingly prefer to get their information from people they trust, which has fueled a rise in finding information through social media and social contexts. We want to see if people enjoy sharing information from Wikipedia. | Align on whether/how to scale the article-level Share button | |
| Mobile Table of Contents
Offer a table of contents on mobile web. |
Reader Growth | March - April 2026 | A/B/C test | Mobile web users on Arabic, French, English, Indonesian, and Vietnamese Wikipedias | Readers struggle to navigate our mobile interface without wayfinding help. We want to explore whether a table of contents supports readability. | Dont Ship: Readers get overwhelmed and have difficulty navigating long text blocks. The ToC buttons in our treatments did not improve wayfinding enough to mitigate the overwhelm observed in our prior Mobile Expanded Sections experiment, so we saw the same outcome of longer sessions due to more friction, resulting in lower retention | |
| Reader → Contributor Attribution Baseline Experiment
Measure how many readers create contributor accounts and see whether the rate differs depending on how people came to the site (by referrer) |
Various teams involved in Key Result WE5.3 | March 22nd – April 2nd | Invisible
(no discernable UI change) |
Sampled anonymous readers across Wikipedia projects, sampling the top 50 largest Wikipedias | WMF would like to understand how different types of readers become contributors. This experiment puts additional code on existing interfaces that tracks how many readers become contributors across a variety of characteristics (like which device a person uses, how they found the site, etc.)The goal is to test the code to see if such experiments can be carried out going forward and gain insight into how readers become contributors. The data gathered from this experiment will be aggregated or discarded once the experiment is complete, in accordance with the data collection policies. |
We need to learn more
| |
| Activity Tab
Transforming the History tab into a richer Activity experience that highlights reading, editing, and contribution insights. |
Apps | 2025 – early 2026 | A/B test and scaling | Wikipedia app users (iOS, logged-in and logged-out) | The team aimed to increase engagement, retention, and account creation by helping users better understand and interact with their activity across reading, editing, and contributions. | Ship it! — The Activity Tab showed strong impact:
The feature has been scaled and continues to be improved, with focus on onboarding clarity and navigation. | |
| Hybrid search
Show richer results to readers when they search for something in natural language |
Apps | February – April 2026 | A/B test | Android app users on Greek, English, French, and Portuguese Wikipedias | Readers struggle to find specific information on Wikipedia using internal search, and hybrid search (keyword search plus semantic search) shows potential for improving navigation and wayfinding. | Proceed to Phase 2: Based on Phase 1 results, the experiment showed strong potential for improving search and navigation. The team is moving forward to Phase 2 (build for release). | |
| Encouraging users with unconfirmed emails to confirm them | Product Safety and Integrity | Mid May for 2 weeks | A/B/C test | Logged-in users with unconfirmed emails on English, French, German, Polish, Japanese, Hebrew, Wikidata, Commons, Mediawiki, Meta | Wikimedia projects do not currently require email confirmation in order to edit and take other actions as a registered account. As a result, many user accounts have associated emails that have never been confirmed. This is contributing right now to users being locked out of their account, with no safe way for them to regain access. This experiment will measure the effectiveness of persistent communication that encourages user accounts that have an unconfirmed email address to confirm it, or set up a new confirmed email address. | Ship it! – The results from this experiment are encouraging. We saw an 80% increase on average in email confirmation rates across the projects in the experiment. We saw negligible impact in email removal rates. Next, we will be rolling this banner out to all communities in June. You can read more about the experiment results here. | |
| Mobile page previews | Reader Growth | April 20 - May 18 | A/B test | 10% of logged-out readers on Arabic, French, Italian, Polish, and Vietnamese Wikipedias and 0.1% of logged-out readers on English Wikipedia | We want to test Mobile Page Previews — a pop-up bottom sheet that appears when a reader taps a blue link, showing the thumbnail, lead paragraph, and an option to open the article — on mobile web article pages. Page Previews already exist on the Wikipedia desktop experience and both mobile apps. | Stopped: Based on flat retention and negative indicator metrics, our hypothesis was not supported, and readers on mobile web did not prefer Page Previews over navigating directly to blue-linked articles. | |
| Donor Appreciation Badge
Testing two variations of a "thank you" badge shown to donors after a recent donation. The badge is visible only to the donor on their own browser. One variation includes a simple thank-you message, while the other includes a lightweight animation when tapped. |
Reader Experience & Fundraising | June – July 2026 | A/B/C test | Logged-out donors who recently donated on mobile web browsers (1% on English Wikipedia, 10% on German Wikipedia) | We hope to deepen the relationship between donors and the Wikimedia movement through different approaches to appreciating and engaging supporters. Findings may inform future opportunities to invite donors to create accounts for deeper engagement with Wikipedia, including reading and editing. | Inconclusive, not scaling: We need to iterate on this further under different donor sentiment experiments in DE5.4 KR (We may run a future iteration that invites anonymous donors to created WP accounts in order to save their donor status and get access to more reader features).
| |
| Surface Reading Lists to logged-out readers on mobile web to increase account registration rate | Reader Experience | May-June 2026 | A/B test | 10% of logged-out readers on German, Spanish, Italian, Portuguese, Polish, Dutch, Turkish, Urdu Wikipedias | Account creation is the gateway to meaningful participation on Wikimedia projects. This experiment aims to encourage account registration at the moments where motivation is naturally highest, such as creating reading lists. | Further Optimisation is required before scaling. 93% users responded that the feature is useful to them, exceeding our goal of 50%. | |
| A/A test on retention rate for logged-in readers baseline
Establish a baseline retention rate for logged-in readers. |
Reader Experience | March 24 to May 30, 2026 | A/A test | Randomized users across top 50 trafficked wikis | We do not currently have an existing measurement of user retention rate for logged-in Wikipedia readers. This test is intended to etablish a baseline that will be useful in helping us set key result goals for improving logged-in and active user retention on web next fiscal year. | Logged in Reader Retention baseline established. See
Logged-in Reader Retention Baseline (Users with 0 edits on top 50 Wikipedias):
We will Use the newly established definition and baseline to evaluate future logged-in reader experiments and product interventions | |
| Explore Feed Refresh
Testing a refreshed Explore Feed with a more modern design, clearer structure, and lightweight personalization, with a goal of making it easier for readers to discover interesting content and come back to the app more often. |
Apps | Mid May | A/B test | New and casual Wikipedia app readers (especially logged-out users) | The Explore Feed is not engaging enough; most users don’t come back to it, don’t customize it, and don’t clearly understand its purpose. | We exceeded our 10% goal, and saw an 10.5% statistically significant increase in engagement with the feed.
| |
| 25th Birthday Reading Challenge
Encourage readers to build a daily habit by reading one article per day and completing a 25-day streak. |
Apps | May 11 – June 18, 2026 | Experiment | Wikipedia app users (logged-in and logged-out) | Many readers open Wikipedia when they need information, but fewer return regularly. This experiment explores whether a simple, goal-based reading challenge with progress tracking and rewards can encourage more frequent engagement and habit formation. | we exceeded our goal of 5% increase compared to that cohort’s past behavior before joining the challenge.
|