Рост/Обновления от Команды Роста

This page is a translated version of the page Growth/Growth team updates and the translation is 78% complete.

Эта страница содержит обновления о работе Команды Роста по увеличению активности и удержания новых редакторов. Планирование этой работы началось в июне 2018 года. Команда работает над несколькими проектами одновременно, но все они будут обсуждаться на этой странице.

Как принять участие

It is important that our work is grounded in the reality of the communities we hope to help. If you have thoughts or ideas around this project or our team's work, please comment on this project's talk page.

Обновления проекта

Обновления за 2022 год приведены ниже, из этой страницы. Посмотрите на обновления 2022 года.

Обновления за 2024 перечислены ниже, с этой страницы. Смотреть 2024 обновления. ● Growth team updates: 2024, 2023, 2022, 2021, 2020, 2019, 2018.



Update 2024-02-23: New project ideas for the Newcomer Homepage

  • The Growth team will assist with the WikiExperiences 1.3 Key Result from the WMF Product & Technology department's Objectives and Key Results after we complete initial work on Community Configuration.
    • WikiExperiences 1.3 Key Result: A 1 percentage point increase (YoY) in the portion of newly created or improved articles on high-impact topics with acceptable quality, per the “global quality score”, that are created or edited on Wikipedia, starting with underrepresented geographic regions and gender.
  • The initial project ideas Growth is discussing related to the WikiExperiences 1.3 Key Result:

Update 2024-02-16: New project ideas for the Newcomer Homepage

  • Community Configuration 2.0
    • The Growth team is drafting initial Community Configuration Guidelines (T350728) and Developer documentation (T349039). We will share an initial draft for community discussion soon.
    • We shared a second iteration of Community Configuration designs.
    • Engineers have completed writing specifications for the Configuration store (T342752) and the editing form (T343072).
    • Engineers have reviewed Community Configuration use for Growth features, Automoderator, Web, and Campaigns in order to better understand use cases and which datatype and components would work for each use case. (T351545).
    • The initial code for the Community Configuration dashboard is written (T354390).

Update 2024-02-09: Personalized praise experiment results

 
Personalized praise increased number of non-reverted edits made within 30 days of registration on Spanish Wikipedia.
  • Positive Reinforcement
    • We have shared experiment results for the Personalized praise feature. This feature was developed for Mentors as part of the Growth team's Positive Reinforcement project. For this experiment, we focused on the effect of praise on newcomer retention and productivity. The Personalized praise feature was deployed to the Arabic, Bangla, Czech, and Spanish Wikipedias in late May 2023. We analyzed the Spanish Wikipedia separately from the other three because on the Spanish Wikipedia 50% of newcomers are randomly assigned a mentor, which means the feature is part of a controlled experiment.
    • On Spanish Wikipedia, although we found no significant impact on retention, we found a significant positive impact on newcomer productivity. This finding is encouraging since our preliminary analysis of mentorship found conflicting results.
    • As these results were not positive enough to clearly justify the time investment from Mentors, we have decided to start conversations with our Product Ambassadors and communities and consider further improvements before releasing the feature more widely. We will consider improvements related to reducing the amount of work needed by Mentors, potential design improvements, and improvements to how newcomers are selected to be displayed in the Personalized praise module.
  • Support conditional defaults for user properties to help address user_properties table bloat
    • This week, the Growth team has finished up the work of supporting conditional defaults for user properties (T354459). Growth completed 11 tasks and documented the work (https://www.mediawiki.org/wiki/Manual:$wgConditionalUserOptions). DBAs will handle dropping the old rows (T357072). This effort to support conditional defaults was requested by Wikimedia system administrators and was considered a high priority because if ignored it may have resulted in database malfunctioning in the wikis with the most registered users.

Update 2024-02-02: Community Configuration

Update 2024-01-26: Growth + Campaigns Offsite

  • The Growth team has members on four continents and many time zones, but once a year we have the opportunity to spend a work week together. This year our offsite was scheduled with the Campaigns Product team.
  • We spent the majority of our first day together discussing our current project: Community Configuration 2.0.
  • Our second day was future-focused and we discussed ideas for supporting the Wiki Experiences 1.3 Key Result. The Growth team Annual Plan always included time for a secondary annual-plan related project, but we hadn't finalized plans. After reviewing the state of all WMF Product & Technology Objectives & Key Results, WMF Product leadership suggested Growth could help support the Wiki Experiences 1.3 Key Result since it is considered an understaffed and "at risk" key result. The Growth team is currently considering various ways we can extend Growth features to best support this Key Result, and we will share some initial ideas and mockups with the community soon.
  • Our final offsite days together were spent working directly with the Campaigns team.

Update 2024-01-12: Donor Thank You page results on English Wikipedia

  • English donors encouraged to try editing
    • One theme that emerged from volunteer feedback was around the need to recruit more editors, rather than just fundraise. After receiving support from English Wikipedia editors, we scaled the Thank you page experiment to English Wikipedia for the 2023 English fundraising campaign. Detailed analysis and interpretation of results for the first day and first week of the campaign can be found in this task: T352116, and final campaign analysis is found in this task: T352900.
    • The following are results for the entirety of the 2023 campaign: 2023-11-28 @ 09:00 UTC to 2024-01-01 @ 12:00 UTC.
Platform Page views Unique visitors Registrations Registration % Activations Activation %
Desktop 6,045 5,203 1,912 36.7% 219 11.5%
Mobile web 7,665 6,802 2,486 36.5% 222 8.9%
Totals 13,710 12,005 4,398 36.6% 441 10.0%
    • Although it was a small fraction of donors that clicked through to Try editing Wikipedia, this Donor Thank you page campaign led to 4,398 new accounts, and 441 of those accounts went on to constructively edit within 24 hours (a constructive edit means the edit wasn’t subsequently reverted within 48 hours).
    • We also calculated the revert rate of the edits made by these users, as well as what proportion of their edits came through the Suggested Edits module on the Newcomer Homepage. When it comes to the revert rate across all edits, with the knowledge that contribution amounts vary greatly between users, the revert rate is 8.9% out of <900 edits (we're not reporting specific edit counts per our Data publication guidelines). The low revert rate might be a result of the high proportion of Suggested Edits these newcomers make. Overall the proportion is 61.8% out of <900 edits. The rate is lower on desktop (53.6% out of <450 edits) than on mobile web (70.0% out of <450 edits).
    • As we concluded in previous experiments in other languages (Newcomer Experience Pilot Project- Thank You Pages and Thank You Banners) the donor Thank you page "Try editing Wikipedia" call to action seems like a sustainable and low-impact way to grow the number of new editors on Wikipedia.
  • Community Configuration 2.0
    • Design: After receiving initial user research results from Community Configuration, the Growth team’s UX designer has worked on further refinements to the Community Configuration designs (T350201).
    • Engineering: We have started the more front-end focused work on Community Configuration. We have started to investigate form generation options for Community Configuration (T332849 ) and write specifications for the editing form (T343072).
  • Support conditional defaults for user properties
    • Growth engineering has been partially focused on tasks related to adding support for conditional defaults for user properties to help address user_properties table bloat (T354459). This work wasn’t part of the Growth team’s annual roadmap, but was escalated by Wikimedia system administrators as ignoring the issue indefinitely could result in database malfunctioning in the wikis with the most registered users.
  • IP Editing: Privacy Enhancement and Abuse Mitigation
    • We have finished work on setting a 1-year expiry for temporary accounts (T344695 & T300271).

Update 2024-01-05: Community Configuration user research & supporting conditional defaults for user properties

  • Community Configuration 2.0
    • The Growth team’s UX designer shared some further refinements to the Community Configuration designs (T350201).
    • We have switched to justinrainbow/json-schema for schema validation (T353230). Initially, we went with opis/json-schema for validating schemas. This proved to be problematic, because certain features we use are only available in 2.3 (T351878) and Wikilambda currently uses 1.x (T319054).
    • We have completed initial user interviews with admins about Community Configuration: Community Configuration: interviews with admins. The main learnings are:
      • Participants from smaller wikis are enthusiastic about how “democratizing” Community Configuration is.
      • Participants from larger wikis trust that the restrictions/permissions that currently govern configuration will continue to do so under Community Configuration.
      • Participants found the Community Configuration designs to be an improvement over the existing configuration processes/systems they are familiar with.
      • Participant concerns about empowering too many people to make configuration changes were alleviated once participants interacted with the Community Configuration prototypes.
      • The explanatory messages, logo image, and page title used in the prototype can be reconsidered in light of the fact that Community Configuration will be used by many non-technical, non-native speakers of English
  • Support conditional defaults for user properties
    • Engineers have been mainly focused on tasks related to adding support for conditional defaults for user properties to help address user_properties table bloat (T354459). This work wasn’t part of the Growth team’s annual roadmap, but was escalated by Wikimedia system administrators as ignoring the issue indefinitely could result in database malfunctioning in the wikis with the most registered users.
  • Other improvements:
    • Dark mode improvement (T351097).
    • No back icon on mobile growth home page overlay (T351097).
    • Section level “add an image” placeholder bug fix (T352208).
    • In order to support future effort to deprecate Flow, users can no longer enable the Flow beta feature on their user talk page (T248309). We also updated copy to help provide clarity (T352565).
    • Mentorship bug fix for Mentor whose mentees were not reassigned after quitting mentorship (T354220).
    • IP Masking improvements (T344694 & T350923).