Page MenuHomePhabricator

[EPIC] Growth: Newcomer tasks 1.0
Closed, ResolvedPublic

Description

This is epic is about work on the "newcomer tasks" project: task recommendations for newcomers. It will be hosted at first via the newcomer homepage (T213990).

We think that newcomers should have every opportunity to succeed when they first arrive at the wiki. But frequently, newcomers attempt a task that is too difficult for them, can't find a task they want to do, or can't find ideas for how to remain involved after their first edit. This leads to many of them leaving and not coming back. There have been successful attempts in the past at recommending tasks to editors, and so we believe that the newcomer homepage is a potential place to recommend relevant tasks for newcomers.

We'll need to keep in mind a few things:

  • Many newcomers arrive with something specific in mind they're trying to accomplish, like add a specific photo to a certain article. * We don't want to get in the way of them accomplishing their goal.
  • Newcomers build up their skills over time by progressing from easier edits to hard ones.
  • When newcomers are successful early on, they are more motivated to continue editing.
  • Taking those things into account, we want to recommend tasks to newcomers that arrive at the right place and time for them, teach them skills they need to be successful, and relate to their interests.

A valuable tool we have for helping tasks be relevant to newcomers is the welcome survey, which was originally built specifically for this purpose: personalizing the newcomer's experience. We'll plan to use the optional information newcomers give about their goals and interests to recommend appropriate tasks for them.

One of the largest challenges is going to be figuring out how to gather tasks that are appropriate for newcomers to do. There are many existing sources, such as templates that call for work on articles, recommendations in the Content Translation tool, or suggestions from tools like Citation Hunt. The question will be which of those options help newcomers accomplish their goals.

At first, we'll focus on using the newcomer homepage as the place to recommend tasks, but in the longer term, we can imagine building features that extend into the editing experience to recommend and help newcomers accomplish recommended tasks.

Also in the longer term, we'll be thinking about ways to tie task recommendations into other parts of the newcomer experience, such as the impact module on the homepage, or into the help panel.

Related Objects

StatusSubtypeAssignedTask
ResolvedMMiller_WMF
ResolvedRHo
DeclinedNone
ResolvedDesignRHo
ResolvedTrizek-WMF
ResolvedAug 9 2019revi
ResolvedAug 9 2019 Urbanecm_WMF
ResolvedAug 9 2019Dyolf77_WMF
ResolvedPPham
ResolvedMMiller_WMF
Resolvednettrom_WMF
Resolvednettrom_WMF
Declinednettrom_WMF
Resolvednettrom_WMF
Resolvednettrom_WMF
Resolvednettrom_WMF
ResolvedEtonkovidova
ResolvedTgr
ResolvedCatrope
Resolvedkostajh
Resolvedkostajh
Resolvednettrom_WMF
Resolvedkostajh
Resolvednettrom_WMF
Resolvednettrom_WMF
Declinednettrom_WMF
Resolvednettrom_WMF
Resolvednettrom_WMF
Resolvedkostajh
Resolved Urbanecm_WMF
OpenNone
ResolvedCatrope
Resolvedkostajh
OpenNone
OpenNone
ResolvedCatrope
ResolvedCatrope
ResolvedMMiller_WMF
ResolvedMMiller_WMF
ResolvedMMiller_WMF
ResolvedTgr
Resolvedkostajh
ResolvedTgr
Resolvedkostajh
Resolved mepps
ResolvedCatrope
Resolvedkostajh
Resolvedkostajh
Resolvedkostajh
DeclinedNone
Resolvedkostajh
ResolvedTgr
Invalidkostajh
Resolvedkostajh
ResolvedCatrope
Resolvedkostajh
Resolvedkostajh
ResolvedTgr
Resolvedkostajh
ResolvedCatrope
Resolvedkostajh
ResolvedEtonkovidova
OpenNone
Resolvedkostajh
ResolvedBUG REPORTTgr
Resolvedkostajh
Resolvedkostajh
ResolvedMMiller_WMF
ResolvedRHo
ResolvedRHo
ResolvedTrizek-WMF
ResolvedTgr
ResolvedBUG REPORTkostajh
OpenNone
InvalidNone
ResolvedEtonkovidova
ResolvedTrizek-WMF
ResolvedCatrope
OpenNone
Resolvedkostajh
ResolvedBUG REPORTEtonkovidova
ResolvedMMiller_WMF
ResolvedTrizek-WMF
ResolvedMMiller_WMF
Invalid Urbanecm_WMF
InvalidNone
Resolvedkostajh
Resolvedkostajh
Resolvedkostajh
Resolvedkostajh
ResolvedTgr
ResolvedTgr
ResolvedMMiller_WMF
DuplicateNone
ResolvedTgr
OpenNone
OpenNone
ResolvedRHo
Resolvedkostajh
OpenNone
ResolvedTrizek-WMF
ResolvedTgr
ResolvedEtonkovidova
InvalidNone
ResolvedTrizek-WMF
ResolvedTrizek-WMF
OpenNone
Resolvedkostajh
DeclinedNone

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes

Change 552156 had a related patch set uploaded (by Catrope; owner: Catrope):
[operations/mediawiki-config@master] GrowthExperiments: Enable suggested edits without opt-in

https://gerrit.wikimedia.org/r/552156

Change 552156 merged by jenkins-bot:
[operations/mediawiki-config@master] GrowthExperiments: Enable suggested edits without opt-in

https://gerrit.wikimedia.org/r/552156

Mentioned in SAL (#wikimedia-operations) [2019-11-21T00:24:32Z] <catrope@deploy1001> Synchronized wmf-config/InitialiseSettings.php: GrowthExperiments: Enable suggested edits without opt-in (T227728) (duration: 00m 52s)

Not sure if this is the place where I can leave feedback, but personally I think that the current Beta features for mobile should probably be visible to all editors, including not signed in mobile editors. As mobile devices have already overtaken desktops and laptops globally it is quite likely that people entering Wikimedia websites do so on a mobile device. It is quite egregious that the "standard mobile website" actively hides both editing and discussion features. There is no way to find a talk page on mobile unless you're signed in, furthermore, the mobile browser also doesn't allow entire pages to be edited unless you specifically know that you can manually turn "editor/1" into "editor/all" in the URL while editing.

The entire "mobile experience" seems to revolve around content consumption and not content creation or improvement. Even as a consumer's choice it fails as it omits both categories and navigational templates (though they are visible on Dutch-language Wikimedia websites for some reason). The growth team should probably focus more on mobile as a lot of users are coming in through mobile devices.

Hi @DonTrung -- thank you for getting in touch about this. The Growth team definitely prioritizes mobile experiences, because as you say, many newcomers are arriving at Wikipedia through their mobile devices. In some Wikipedias where we work, like Arabic, mobile is the clear favorite for newcomers creating accounts. These days, we tend to design first for mobile to make sure our ideas work on that platform, and then afterward develop a desktop experience. All the Growth features are available on mobile.

That said, the Growth features are not yet available to logged-out users. We made the decision on our team to focus on logged-in users because there are very many of them, and because having an account facilitates some of the features we've built. An example is mentorship -- we assign all newcomers a mentor, who they can ask questions to. In order for us to make sure a given newcomer continues to have the same mentor everytime they come to the wiki, it helps for them to have an account.

But in the future, we do want to make versions of the Growth features for all users -- we'll have to think about how to adapt some of them.

Which wiki do you work on? Have you been able to try out the Growth features?

Rileych subscribed.

Kosta and I are closing this. Reopen if you need to!