Growth/Growth team updates/2024

Growth team updates: 2024, 2023, 2022, 2021, 2020, 2019, 2018.


Update 2024-04-19: Community Configuration testable on Beta edit

  • Community Configuration 2.0
    • There are still missing pieces, but you can test the first parts of the CommunityConfiguration extension on Spanish Beta.
    • Growth engineers are still working to migrate the rest of the Special:EditGrowthConfig settings to Special:CommunityConfiguration.
    • We are adding in better error handling (T360368), monitoring (T361072), and other features needed prior to a pilot wiki release.
    • Two Growth engineers will attend Wikimedia Hackathon and are preparing a Community Configuration session (T360432).  

Update 2024-04-12: "Add an Image" experiment analysis published edit

  •  
    Add an Image increased constructive activation (making a non-reverted article edit) for newcomers on the mobile web platform
    Add an Image
    • We have published “Add an Image” experiment analysis. Major take-aways from the experiment:
      • The “Add an Image” structured task leads to an increase in newcomer participation on the mobile web platform, particularly by making constructive (non-reverted) article edits:
      • The likelihood that mobile web newcomers make their first article edit (+17.0% over baseline)
      • The likelihood that they are retained as newcomers (+24.3% over baseline)
      • The number of edits they make during their first two weeks on the wiki (+21.8% over baseline)
      • A lower probability of the newcomers’ edits to be reverted (-3.3% over baseline).
  • New Growth team engineer
    • This week we welcomed Michael Große to the team! Michael is a Leipzig-based software developer who previously worked for WMDE on Wikidata, and before that on DokuWiki.

Update 2024-03-22: Community Configuration edit

  • Community Configuration 2.0
    • The Community Configuration security review is complete, and the extension is classified as low risk. (T349568). In general, the code reviewed appears to be robust in terms of security. There are no vulnerable dependencies, and no apparent vulnerabilities are present.
    • We will release the first part of Community Configuration to es.wikipedia.beta next week (T357766).
    • Our next major milestone is to migrate the remaining logic of SpecialEditGrowthConfig to the new CommunityConfiguration extension (T355317).
    • We are drafting initial design guidelines for Community Configuration (T350728).

Update 2024-03-15: Early planning for additional Newcomer homepage modules edit

  • Community Updates module
    • Growth Product Ambassadors have translated project documentation into Arabic and Spanish and are starting community discussions about this small experimental project.
  • Newcomer Homepage Translation task
    • We are still in the early discovery period for this project, and considering community needs and exploring the feasibility of filtering tasks to help address knowledge gaps.

Update 2024-03-08: Non-editing Participation Research edit

  • Non-editing Participation
     
    Non-editing Participation final report
    • We have published a summary of the Non-editing Participation Research conducted this fiscal year. Including a link out to the final report. The Non-editing Participation final report, in addition to painting a clearer picture of the people who make accounts “to read Wikipedia,” finds that
      • (a) many readers create accounts because they expect that their accounts will provide them with reading tools and features;
      • (b) new account holders as a group are interested in deepening their relationship with Wikipedia, and have taken a step to do so; and
      • (c) interviewed readers are more interested in tools and features that improve their own experience (like creating reading lists) than they are in features that rely on interaction with others (like sharing reading lists).
    • On the whole, many readers want more from the Wikipedia reading experience than they currently get, and these interested readers might be enticed to deepen their relationship with and participation in Wikipedia if provided some of the tools they appear to expect.
    • The Growth team may focus on a project that relates to Non-editing Participation next fiscal year, but our team's focus will depend upon the WMF Contributor experience and Consumer experience priorities set in the 2024-2025 Wikimedia Foundation annual plan.

Update 2024-03-01: Community Configuration progress edit

  • Community Configuration 2.0
    • Growth engineers are focused on Community Configuration, and they have completed several important steps that block an initial beta release:
      • Made it possible to register community configuration providers via a MediaWiki configuration variable (T358263).
      • Investigate generating JSONSchema approach (T351232) and JsonSchemaValidator improvements (T358769).
      • Write specifications for the Configuration store (T342752) and the Editing form ​​(T343072).
      • Community configuration 2.0 editing form MVP (T356622).
      • Coordinate with Growth’s QA Engineer to start testing Community Configuration.

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

  • 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 edit

  • 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 edit

 
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 edit

Update 2024-01-26: Growth + Campaigns Offsite edit

  • 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 edit

  • 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 edit

  • 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).