Welcome to the Growth team pages.
Discover Growth Features
Use Growth features
Growth features at your community
Increasing new editor retention in mid-size wikis.
- Наблюдение на първия ден (Пътешествие на редактора)
- Персонализиран първи ден
- Фокусиране върху бюрото за помощ
- Позитивна подкрепа
- Community configuration
Таблицата по-долу е бърз начин да видите кои инициативи на екипа за Растеж са внедрени в кои уикита. Вижте конкретните страници на проекта за подробности.
In the table below, wikis in bold (Уикипедия на арабски, Уикипедия на бенгалски, Уикипедия на чешки, Уикипедия на испански) are our pilot wikis, with dedicated resources. Wikis in italics are kept in the control group so that get some data about our features' impact.
Wikis in A/B testing mode are with the following configuration: 80% of new accounts get Growth features, 20% have the default experience. These numbers are sometimes different, if so they are detailed in the table below. Wikis with less than 500 new accounts per week aren't concerned by this A/B testing.
All versions of Wikipedia now have the Growth features. The list below details the ones where the configuration is not the default one.
|Wiki||EditorJourney||Welcome survey||Help panel||Newcomer homepage||Newcomer tasks||Link recommendation||Image recommendation||Mentor dashboard|
|All Wikipedia not listed below||Not needed||Готово||Готово||Готово||Готово||Available at all wikis, activated where a list of mentors has been created|
|Уикипедия на арабски||Готово||Готово||A/B testing||A/B testing||A/B testing||Готово||A/B testing (50%)|
|Уикипедия на бенгалски||Not needed||Готово||A/B testing||A/B testing||A/B testing||Готово||A/B testing (50%)|
|Уикипедия на чешки||Готово||Готово||A/B testing||A/B testing||A/B testing||Готово||A/B testing (50%)|
|Уикипедия на немски||Not needed||A/B testing||A/B testing||A/B testing||Готово|
|Уикипедия на английски||Not needed||A/B testing (10%)||A/B testing (10%)||A/B testing (10%)||A/B testing (10%)|
|Уикипедия на испански||Not needed||Готово||A/B testing||A/B testing||A/B testing||Готово||A/B testing (50%)|
|Уикипедия на персийски||Not needed||Готово||A/B testing||A/B testing||A/B testing||Готово||A/B testing (50%)|
|Уикипедия на френски||Not needed||Готово||A/B testing||A/B testing||A/B testing||Готово||A/B testing (50%)|
|Уикиречник на френски||Готово||Готово||A/B testing||A/B testing||Неизвършено|
|Уикипедия на унгарски||Готово||Готово||A/B testing||A/B testing||A/B testing||Готово|
|Уикипедия на арменски||Готово||Готово||Готово||Готово||Готово|
|Уикипедия на корейски||Готово||Готово||A/B testing||A/B testing||A/B testing|
|Уикипедия на нидерландски||Not needed||A/B testing||A/B testing||A/B testing||A/B testing||Готово|
|Уикипедия на полски||Not needed||Готово||A/B testing||A/B testing||A/B testing||Готово|
|Уикипедия на португалски||Not needed||Готово||A/B testing||A/B testing||A/B testing||A/B testing (50%)|
|Уикипедия на румънски||Not needed||Готово||A/B testing||A/B testing||A/B testing||Готово|
|Уикипедия на руски||Not needed||Готово||A/B testing||A/B testing||A/B testing||Готово|
|Уикипедия на сръбски||Готово||Готово||Готово||Готово||Готово|
|Пробна Уикипедия||Not needed||Готово||Готово||Готово||Готово||Готово||Готово|
|Уикипедия на турски||Not needed||Готово||A/B testing||A/B testing||A/B testing||A/B testing (50%)|
|Уикипедия на виетнамски||Готово||Turned off (see task T218920)||A/B testing||A/B testing||A/B testing||Готово||A/B testing (50%)|
Екипът за Растеж е сформиран през юли 2018 г. Екипът подкрепя програмата „Ново съдържание“ на отдела за аудитория и, от друга страна, дългосрочната цел на фондация „Уикимедия“ „Равенство на знанието“. Тези инициативи са свързани с изграждането на здрави общности, които носят широко и задълбочено съдържание на хората по целия свят. Един от начините за постигане на това е чрез ангажиране на нови сътрудници в проектите на Уикимедия. За съжаление, много малко хора, които започват да допринасят, продължават да допринасят в дните и седмиците след началото. Това е така, защото допринасянето изисква много културни и технически умения, които са трудни за научаване. Целта на екипа на Растеж е да се справи с този проблем чрез софтуерни промени, които помагат да се задържат новите сътрудници в средните по размер проекти на Уикимедия, като се започне с Уикипедиите.
Започваме работата си със средните по размер Уикипедии по няколко причини. Тези проекти имат голям потенциал за растеж, но също така пред тях има предизвикателства, на които може да се помогне чрез софтуер. Голяма част от мотивацията за работата на този екип идва от изследователския проект Опит на новия редактор, който бе предприет през 2017 г. В проучването, Фондация Уикимедия работи с чешката и корейската общности на Уикипедия, за да разбере предизвикателствата, които са пречка пред новите сътрудници. Продължавайки тази връзка, ние ще тестваме софтуерни промени в [$cswiki чешката] и [$kowiki корейската] Уикипедии, преди да ги внедрим в други средни по размер Уикипедии. Нашите промени в софтуера обикновено попадат в една от следните категории:
- In-context help: changes to the Wikipedia editing experience to surface helpful guidance around technical and conceptual challenges.
- Human-to-human help: forums and programs that connect editors to each other so that experienced contributors can help newer contributors succeed.
- Task recommendations: suggesting edits that will help newcomers learn wiki skills.
Community Relations Specialist
Senior Software Engineer
Staff Data Scientist
Senior User Experience Designer
Senior Software Engineer
Senior Software Engineer
Senior Technical Program Manager
Senior Product Manager
- For information about the Growth team that existed from 2013–2015, see Growth/Growth 2014.
- For information about the predecessor to this team, see Collaboration.
Past projects by various iterations of the team and volunteer developers:
- AfC improvements
- Map Improvements 2018
- Edit Review Improvements
- Structured Discussions, formerly Flow, discussion and collaboration software. Now in production as opt-in for talk pages, help pages and village pump-style discussion forums, on select wikis, but new requests are currently not applied.
- Notifications (Echo), a redesign of the notifications system in Wikipedia. It was deployed to all Wikimedia wikis in November 2013.
- New Page Triage, redesigning the New Page Patrol experience.
- WikiLove, a tool designed to encourage community health and reduce "bite".
- MoodBar, a tool designed to encourage feedback from new users, with Feedback Dashboard supporting review by experienced members.
- Article Feedback Tool, a tool designed to encourage readers to provide feedback on articles.
Goals and metrics
As stated in the Audiences department’s 2018-2019 annual plan, the Growth team’s goal is:
Increase retention of new contributors in the target wikis, Czech and Korean Wikipedias.
To determine whether we’re meeting our goal, we have specified metrics and set targets for them:
|New contributor retention in target wikis||10% increase|
|Mentor retention in target wikis||Sustainable rate|
The first metric, “new contributor retention”, is the main metric we use to measure our impact. The second metric, “mentor retention”, will be relevant for interventions that involve mentorship. As we focus our work, we will consider whether that second metric is the right fit for the team at this time.
We need to create a more specific definition of “new contributor retention” in order for it to be useful. See the section below on “What does it mean to ‘retain new contributors’?” for our team’s thinking.
- In the future, this section will contain links to the Growth team's reports that track our metrics.
What does it mean to "retain new contributors"?
For the purposes of this team, “new contributors” are people who have registered accounts on a wiki project, even if they have not made an edit. To “retain” them means that they make edits and continue to make edits over time. Though we hope that contributors are retained for months and years, we know that they will first have to make it through their first days and weeks. Those first days and weeks are more likely to be the Growth team’s focus.
There are different periods of time over which we can measure retention. One definition might be “second month retention”, meaning a contributor is "retained" if they edit during their first month and also edit during their second month. But another definition might be “second week retention”, meaning a contributor is "retained" if they edit during their first week and also edit during their second week.
As we work, the Growth team will determine which types of retention are most important to track and to increase. See this page for a formal definition of retention.
Wikimedia projects need to have a constant stream of new contributors in order to become hubs for broad and deep content. New contributors replace experienced contributors who stop editing. They also increase the diversity of the editing community. This stream of new editors allows projects to grow their content while increasing the diversity of their content. But in many Wikimedia projects, the number of active contributors is decreasing or staying the same, and the retention rate of new contributors is also decreasing or staying the same. This issue was studied in the 2013 paper The Rise and Decline of an Open Collaboration System: How Wikipedia's reaction to popularity is causing its decline. The authors showed that active contributors in English Wikipedia began to shrink in 2007, with the major cause being increasing technical and cultural barriers for contributors. Since then, similar patterns have been seen in other Wikimedia projects.
- Data showing the state of active contributors and contributor retention in Wikimedia projects is forthcoming.
Beyond the high-level numbers themselves, additional research suggests that many new contributors do not reach their full potential because contributing is both technically and culturally complicated. For instance, it is common for excited new contributors to have their first edits reverted or their first pages deleted without an informative explanation. This causes them to be confused and disappointed, and ultimately not to continue editing.
Together, the numbers, research, and stories, mean that we can do better to engage and retain new contributors. In particular, the Wikimedia Foundation decided to focus on mid-size Wikipedias because those projects need to grow their content, have challenges with contributor retention, and there is potential for software to help.
To better understand what causes new contributors to stay and to leave, the Wikimedia Foundation completed the New Editor Experiences research project in 2017. The project identified the main challenges experienced by new contributors to Wikipedia, and a set of potential solutions. See the “Challenges” and “Solutions” sections below for the details.
The Growth team formed to take action on the challenges and solutions identified by the research project. We will continue our relationship with the Czech and Korean communities by testing changes in those wikis first. When we discover changes that increase contributor retention, we will engage other communities to consider deploying those changes in more wikis.
Although much valuable research has already been done to help our team understand new editors, important open questions remain. The team records and prioritizes our open questions on this page. We will be deliberate about using research, data, surveys, and feature instrumentation to answer them.
The following is a list of healthy characteristics that we think wikis should exhibit with respect to new contributors. They are guiding principles for our team, and we hope to help make them a reality in the wikis we work with.
- Diverse contributors lead to wikis with broad and deep content.
- Contributors who want to make useful improvements to a wiki should all be able to find a place in the community where they fit in.
- Contributors should be able to learn to edit on their own.
- Contributors of any skill level should be able to ask for and receive help from other community members.
- Contributors should be able to learn and edit in a supportive and non-confrontational environment.
There are challenges that stand in the way of the principles above. The main challenges were identified by the New Editor Experiences research project that was completed in 2017. With the help of Czech and Korean community members, researchers interviewed 64 contributors to Czech and Korean Wikipedias to learn about why they started editing, what they found easy or difficult, and if they've stopped editing, why they stopped. The project surfaced a set of technical, conceptual, and cultural challenges, summarized below. Our team’s work will help wikis overcome these challenges so that the principles can become reality.
- Technical: new contributors struggle with specific skills needed to contribute.
- Editing: though Visual Editor is helpful for new contributors, it is hard for them to learn the process of building, citing, and publishing.
- Communication: new contributors have trouble finding and using Talk pages. This is because Talk pages do not use Visual Editor, and because they work differently than other internet discussion systems.
- Finding help: many wikis have scattered and inconsistent help materials that are difficult for new contributors to find and use.
- Conceptual: new contributors have trouble learning core wiki policies and best practices. The following are the concepts that are most challenging.
- Community: many new contributors do not realize there is an active community behind each wiki project.
- Verifiability and citations: all content must be attributed to reliable sources.
- Notability: all content must have garnered enough broad attention to deserve an article.
- Encyclopedic style and neutral point of view: articles should present content without bias toward one side of an argument.
- Copyright: content should not violate the licensing of its sources.
- Cultural: the wiki environment can be discouraging to new contributors who are trying to find where they fit in.
- Personas: new contributors have different objectives for why they are editing, but it is hard to figure out how to accomplish them.
- Framing: the way that contributors communicate impacts whether new contributors stay. Negative feedback can discourage further contribution.
The Growth team will attempt multiple solutions to the above challenges, and we will learn and expand as we go along. These are the findings from the New Editor Experiences project that will guide the solutions we attempt:
- Intermediaries: many new contributors have succeeded because a partner or mentor helped them learn to edit. These partners are frequently found in off-wiki places like schools, libraries, or meetups.
- Iterative learning: new contributors have more success when they learn editing skills over time in safe environments.
- Outside help: new contributors frequently search for help outside of Wikipedia, either in off-wiki communications, or through other internet resources.
Those trends lead to two main categories of solutions to the challenges described above. The work of our team will usually fit into one of these categories:
- Human-to-human help: forums and programs that connect contributors to each other so that experienced contributors can help newer contributors succeed. This can include help desk forums, mentorship opportunities, or even off-wiki connections.
- In-context help: changes to the Wikipedia editing experience to surface helpful guidance around technical and conceptual challenges. This is guidance surfaced at the time it is needed, in the place where it is needed -- as opposed to on a separate page that may be difficult to find.
How we work
The Growth Team follows several principles as we work toward our objective.
- We keep in close communication with the communities our team affects, so that our work remains grounded in reality.
- We start with small interventions, learn quickly, and adjust our approach.
- We make decisions based on evidence from experiments, data, and user research.
- We take the time to equip ourselves with the tools we need to be flexible and work quickly.
- The software we build gives flexibility to the communities who use it, so they can modify and improve it on their own.
- When we know something doesn’t work, we remove it cleanly and learn for the future.
- We follow the Wikimedia Product Guidance for working with communities.
How to work with us
Please review this guide describing how to engage with the Growth team.
These are links and research that underpin the background, principles, challenges, and solutions above, and that continue to shape our team’s thinking.
- The Rise and Decline of an Open Collaboration System: How Wikipedia's reaction to popularity is causing its decline
- New Editor Experiences
- Post-registration editor survey
- Formal definitions of editor retention
- Mentoring in Wikipedia: A Clash of Cultures
- Tea & Sympathy: Crafting Positive New User Experiences on Wikipedia
- The original Growth team from 2013 - 2014.
- Research on the impact of the Wikipedia Adventure
- Evaluating the impact of the Wikipedia Teahouse on newcomer socialization and retention
- Accept, decline, postpone: How newcomer productivity is reduced in English Wikipedia by pre-publication review
- The Pipeline of Online Participation Inequalities: The Case of Wikipedia Editing
- Research on New editors' first session and retention
- Fostering Public Good Contributions with Symbolic Awards: A Large-Scale Natural Field Experiment at Wikipedia
- Bengali Wikipedia replaced Korean Wikipedia on February 2021. Vietnamese Wikipedia was a pilot until October 2021, replaced by Spanish Wikipedia in December 2021.