Growth/Personalized first day/Newcomer tasks/hu

Ez az oldal a Növekedési csapat „új szerkesztők feladatai” projekten végzett munkáját írja le, amely egy konkrét projekt a nagyobb „személyre szabott első nap” nevű kezdeményezésen belül. Ez az oldal a jelentősebb eszközöket, terveket és döntéseket tartalmazza. A legtöbb fokozatosan érkező újdonságot az általános a Növekedési csapat újdonságai oldalon, néhány nagyobb vagy részletesebb újdonságot pedig itt tesszük közzé.

Az alábbi termékminták bemutatója segítségével könnyen megnézheted, hogy a csapat milyen eszközön dolgozik (használd a nyilakat a navigációhoz):


 * asztali eszközökre
 * mobil eszközökre

Ennek a projektnek a tervezése 2019. július 24-én kezdődött.

Jelenlegi állapot

 * 2019-07-24: az első csapatmegbeszélés az új szerkesztők feladatainak a megbeszélésére
 * 2019-08-27: csapatmegbeszélés az ötlet koncepciójának áttekintésére
 * 2019-09-09: a műszaki munkához Phabricator-feladat létrehozása
 * 2019-09-23: asztali felhasználókkal való tesztek befejezése
 * 2019-09-30: mobilfelhasználókkal való tesztek befejezése
 * Továbbiakban: a műszaki fejlesztés folytatása az első verzió novemberi kiadása érdekében

Összefoglalás
Azt gondoljuk, hogy az új szerkesztőknek meg kell kapniuk minden lehetőséget arra, hogy sikeresen legyenek, amikor először találkoznak a Wikipédiával. De gyakori, hogy elsőre olyan feladattal próbálkoznak, ami túl bonyolult számukra, nem találnak olyan feladatot, amit tetszene nekik, vagy nincsen ötletük, hogyan váljanak a szerkesztőség részévé az első szerkesztésüket követően. Ez ahhoz vezet, hogy többségük elhagyja a projektet, és nem tér vissza. Már a múltban is voltak sikeres próbálkozások arra, hogy feladatokat javasoljanak a szerkesztőknek, és azt gondoljuk, hogy az új szerkesztők honlapja egy lehetséges hely arra, hogy javaslatokat tegyünk az új szerkesztők számára az őket érdeklő feladatokra.

Néhány dolgot szem előtt kell tartanunk:
 * Sok új szerkesztő valamilyen konkrét szándékkal érkezik, amit szeretnének elérni, pl. egy adott fénykép hozzáadása egy kiválasztott szócikkhez. Nem akarjuk eltéríteni őket attól, hogy megvalósítsák ezt a céljukat.
 * Az új szerkesztők idővel, fokozatos jutnak hozzá a szükséges ismeretekhez és kézségekhez, az egyszerűbbektől a nehezebbek felé haladva.
 * Amennyiben az új szerkesztők kezdetben sikeresek, motiváltabbakká válnak a szerkesztés folytatására.

Mindezeket figyelembe véve, szeretnénk feladatokat ajánlani az érkező új szerkesztőknek a megfelelő helyen és időben, megtanítani őket a szükséges és érdeklődési körüknek megfelelő szaktudásra ahhoz, hogy sikeresek legyenek.

Az üdvözlési felmérés egy értékes eszköz, ami segít számunkra abban, hogy milyen feladatok érdeklik az újonnan érkezőket. Ezt eredetileg éppen erre a feladatra hoztuk létre: személyre szabott élményt kínálni az új szerkesztőknek. Úgy tervezzük, hogy az új szerkesztőktől opcionálisan, céljaikról és érdeklődésükről kapott információt alapján ajánlunk nekik személyre szabott feladatokat.

Az egyik legnagyobb kihívás, hogy hogyan fogjuk kitalálni és összegyűjteni azokat a feladatokat, melyek megfelelőek az új szerkesztők számára. Számos létező forrás van, mint pl. sablonok, amelyek felkérik a szerkesztőket arra, hogy dolgozzanak a szócikkeken, javaslatok a tartalomfordító eszközben, vagy ajánlások eszközökből, mint pl. a forrásvadász. A kérdés az, hogy ezen lehetőségek közül melyek segítik leginkább az új szerkesztőket a céljaik elérésében.

Elsőre az új szerkesztők honlapjának használatára fogunk összpontosítani, mint arra a helyre, ahol javaslatokat adhatunk a feladatokra. Hosszabb távon azonban el tudjuk képzelni, hogy olyan eszközöket építünk, ami kiterjeszti a szolgáltatást a szerkesztési környezetbe, mely javaslatokat ad, és segíti az új szerkesztőket abban, hogy megvalósíthassák ezeket a javasolt feladatokat.

Hosszabb távon szintén megfontoljuk a feladatok ajánlásának bekapcsolását az új szerkesztők számára kínált szolgáltatások más részeibe, mint az új szerkesztők honlapján található hatásmodul vagy a segítségpanel.

Why this idea is prioritized
We know from research and experience that many newcomers fail early in their editing journey for one of these reasons:
 * They arrive with a very challenging edit in mind, such as writing a new article or adding an image. Those tasks are difficult enough that they likely fail and don't return.
 * They arrive without knowing what to edit, and can't find any edits to make.

We also know that on the newcomer homepage, the most frequently clicked-on module is the "user page" module -- the only thing on the page that encourages users to start editing. This makes us think that many users are looking for a clear way to get started with editing.

And from past Wikimedia endeavors, we've seen that task recommendations can be valuable. SuggestBot is a project that sends personalized recommendations to experienced users, and is a well-received service. The Content Translation tool also serves personalized recommendations based on past translations, and has been shown to increase the volume of editing.

For all these reasons, we think that recommending specific editing tasks for newcomers will give them a clear way to get started. For those newcomers that have an edit in mind that we want to do, we'll encourage them to try some easy edits first to build up their skills. For those newcomers who do not have a specific preference on what to edit, they'll hopefully find some good edits from this feature.

Glossary
''There are many terms that sound similar and can be confusing. This section defines each of them.''


 * "Task recommendations" or "Task suggestions"
 * Lists of articles that need editing work, suggested automatically to users.


 * "Personalized"
 * Software that adapts automatically to each user to fit their needs.


 * "Customized"
 * Software that the user adapts to fit their needs.


 * "Topic"
 * A content subject, such as "Art", "Music", or "Economics".


 * "Maintenance template"
 * Templates that are put on articles indicating that work needs to be done on them.

Recommending tasks
The core challenge to this project is: Where will the tasks come from and how will we give the right ones to the right newcomers?

The graphic below shows our priorities when recommending tasks to newcomers.

As shown in the graphic above, we would give newcomers tasks that...


 * ...arrive at the right time and place for a newcomer's journey.
 * ...teach relevant conceptual and technical skills.
 * ...gradually guide users to build up their editing abilities.
 * ...be personalized to their interests.
 * ...show them the value and impact of editing.
 * ...motivate them to participate continually.

For instance, we do not want to give newcomers tasks that are irrelevant to what they hope to accomplish. If a newcomer wants to write a new article, then asking them to add a title description will not teach them skills they need to be successful.

We're splitting this challenge into two parts: the sourcing the tasks and topic matching.

Sourcing the tasks
There are many different places we could find tasks for newcomers to do. Our team listed as many as we could think of and evaluated them for whether they seem to be achievable for the first version of the feature. Written below is our determination on the task type we'll be starting with, followed by a a table listing many of the task sources that we evaluated.

Maintenance templates
We're going to be starting by using maintenance templates and categories to identify articles that need work. All of our target wikis use some set of maintenance templates or categories on thousands of articles, tagging them as needing copyediting, references, images, links, or expanded sections. And previous task recommendations software, such as SuggestBot, have used them successfully. These are some examples of maintenance categories:


 * Articles needing links in Arabic Wikipedia
 * Articles needing copyediting in Korean Wikipedia
 * Articles needing references in Czech Wikipedia



In this Phabricator task, we investigated exactly which templates are present and in what quantities, to get a sense of whether there will be enough tasks for newcomers. There seem to be sufficient numbers for the initial version of this project. We are likely to incorporate other task sources from the table below in future versions.

It's also worth noting that it could be possible to supplement many of these maintenance templates with automation. For instance, it is possible to automatically identify articles that have no internal links, or articles that have no references. This is an area for future exploration.

During the week of October 21, 2019, the members of the Growth team did a hands-on exercise in which we attempted to edit articles with maintenance templates. This helped us understand what challenges we can expect newcomers to face, and gave us ideas for addressing them. Our notes and ideas are published here.

Full evaluation of task types
Below is a table showing the many sources of tasks that we evaluated in coming to the decision to start by using maintenance templates.

Topic matching
Past research and development shows that users are more likely to do recommended tasks if the tasks match their topical interests. SuggestBot uses an editor's past editing history to find similar articles, and those intelligent results are shown in this paper to be executed on more often than random results. The Content Translation tool also recommends articles based on a user's previous translation history, and those recommendations have increased the translation volume.

Our challenge with newcomers is a "cold start problem", in that newcomers do not have any edit history to use when trying to find relevant articles for them to edit. We have several ideas for how to allow users to indicate topics of interest in a list, or to type topics of interest into a search. Those ideas are being investigated in this Phabricator task.

Comparative review
Our team's designer reviewed the way that other platforms (e.g. TripAdvisor, Foursquare, Amazon Mechanical Turk, Google Crowdsource, Reddit) offer task recommendations to newcomers. We also reviewed Wikimedia projects that incorporate task recommendations, such as the Wikipedia Android app and SuggestBot. We think there are best practices we can learn from other software, especially when we see the same patterns across many different types of software. Even as we incorporate ideas from other software, we will still make sure to preserve Wikipedia's unique values of openness, clarity, and transparency. The main takeaways are below, and the full set of takeaways is on this page:


 * Task types – bucket into 4 types: Rating content, Creating content, Moderating/Verifying content, Translating content
 * Incentives – Most products offered intangible incentives mainly bucketed into the form of: Awards and ranking (badges), Personal pride and gratification (stats), or Unlocking features (access rights)
 * Reward incentives – promote badges or attainments of specific milestones (e.g., a badge for adding 50 citations)
 * Personalization/Customization – Most have at least one facet of personalization/customization. Most common customization is user input on surveys upon account creation or before a task, most common system-based personalization type is geolocalization
 * Visual design & layout – incentivizing features (stats, leaderboards, etc) and onboarding is visually rich compared to pared back, simple forms to complete short edits.
 * Guidance – Almost all products reviewed had at least basic guidance prior to task completion, most commonly introductory ‘tours’. In-context help was also provided in the form of instructional copy, tooltips, step-by-step flows,  as well as offering feedback mechanisms (ask questions, submit feedback)

Initial version
Our evolving designs can always be found in two sets of interactive mockups (use arrow keys to navigate): Those mockups contain explorations of all the difference parts of the user journey, which we have broken down into several parts:
 * Desktop
 * Mobile


 * 1) Gathering information from the newcomer: learning what we need in order to recommend relevant tasks.
 * 2) Feature discovery: the way the newcomer first encounters task recommendations.
 * 3) Task recommendations: the interface for filtering and choosing tasks.
 * 4) Guidance during editing: once the newcomer is doing a task, the guidance that helps them understand what to do.
 * 5) User feedback: ways in which the newcomer can indicate that they are not satisfied with the recommended task.
 * 6) Next edit: how we continue the user's momentum after the save an edit.

For the initial version of the project, we've decided on a subset of the user flow to deploy. This first version is itself broken down into a few parts that will roll out to users in sequence.


 * Version 1.0: users can initiate the suggested edits module, choose task types from maintenance templates based on difficulty, and click to go to the articles needing help. This version will help us see how many users are interested in receiving suggested edits, but we are not confident many will actually follow the suggestions until Version 1.1.
 * Version 1.1: users can also filter articles by topic area, such as "Art", "History", or "Technology". We expect that this will cause many more users to select edits to do, but we don't expect many will actually complete their edits until Version 1.2.
 * Version 1.2: after users click through on suggested tasks, they receive guidance on completing the task through the help panel. With this in place, we think it will be possible for users to find tasks they are interested in, and have enough informaiton to complete them.

Below are some of the current draft design concepts as the team continues to refine our approach.

Variant testing
After deploying the first version of newcomer tasks, we want to start testing different variants of the feature, so that we can improve it iteratively. Rather than just having one design of newcomer tasks, and seeing if newcomers are more productive with it than without it, we plan to test more than variant of newcomer tasks at a time, and compare them. We have compiled an exhaustive list of all the ideas of variants to test -- but we will only end up testing perhaps 10 per year, because of the effort and time it takes to build, test, and analyze. Below are some of the most important ones variants to test.

Desktop
During the week of September 16, 2019, we used usertesting.com to conduct six tests of the desktop newcomer tasks prototype with internet users unaffiliated with the Wikimedia movement. In these tests, respondents are compensated for trying out the mockups, speaking aloud on what they observe, and answering questions about the experience. The full results can be found in this Phabricator task. The goals of this testing were:


 * 1) Gauge the discoverability  of the newcomer tasks module
 * 2) Identify improvements to the usability of the tasks module:
 * 3) Do users understand how to select and review article suggestions?
 * 4) Do users understand how to filter by interests and task difficulty?
 * 5) Do they know how to start editing a suggested article?
 * 6) Gauge user reactions to the suggestions and expectations about guidance through the task.


 * Summary of findings


 * All users thought it made sense and intuitive to get suggestions based on their topics of interest.
 * Similarly, the different task difficulties was positively received by all participants.
 * Overall usability of the suggested edits module was extremely high. People knew how to click to view more articles, use the filter to change topics and task levels, and knew to click on the card to open a suggestion for editing.
 * 4/6 Participants did not initially realize that they should click on “See suggested edits” as a way to help them achieve their goal of writing a new article. This seemed to be a common mental model where users separated "Editing" as different from "Creating a new page".
 * Start module is clearly the starting point for all participants. Moreover many were drawn to “See suggested edits” button as a way to follow the progression of activities in the start module.
 * Users had a clear understanding and expectation they would be shown suggested articles for editing based on the intro dialogs to add topics and introducing task levels.
 * Everyone was able to select the popular topics and add their own topic easily.
 * Everyone understood the purpose of the suggested edits module.
 * Two people were confused/assumed that they could not create a new article until completing easy and medium tasks.
 * 5 of 6 participants knew to click on the help panel button for guidance once they entered the editor mode.
 * Four people expected to be able to contact their mentor in the help panel.
 * Task tips lacked sufficient level of guidance for a couple of participants.


 * Recommendations


 * Improve copy and more over user education that creating new content is a form of editing.
 * Make updates to the Impact module as tested here to aid user understanding of suggested edits.
 * Provide good in-edit context help. It’s very important for users trying an edit.
 * Include a “checklist” for users to revise in the help panel’s task tips.
 * Provide short examples of what to do.
 * Indicate to users they do not have to copy edit for an entire article.
 * Including real-time filtering results helps users connect suggestions as article edits and encourage use of the filtering to find matching articles.

Mobile
During the week of September 30, 2019, we used usertesting.com to conduct six tests of the mobile newcomer tasks prototype. The full results can be found in this Phabricator task. The goals of this testing were the same as with desktop, but with the added goal of understanding how the mobile experience should differ from the desktop experience. Mobile user testers were prompted with the scenario of intending to add an image to Wikipedia (whereas desktop respondents were prompted with the scenario of intending to create a new article).

Summary of findings


 * Overall users found the start module (redesigned) clearly laid out the guided steps to begin.
 * The extra “Suggested edits” module below, while not especially confusing, was still not where users expected to go to help them with their task to add an image.
 * Suggested edits was quite intuitive to use, with participants understanding how its different elements (filtering, seeing more articles, etc) worked.  However, users do not see the value of doing Suggested edits beyond learning or boredom.
 * Several people wanted more granular topics to be available than the broad topics listed.
 * Having the detailed difficulty info was educational, but potentially discouraging. All were surprised “Adding images” was classed as hard, with varying degrees of frustration about this fact.
 * Filtering by interests is a big selling point.
 * 3 people towards the end of the test assumed there was some “verification” or requirement to do  some Easy tasks before Medium/Hard tasks could be achieved
 * Everyone understood the purpose of the Suggested edits as giving edits that would users learn to edit, and also emphasize that it showed them some edits were harder to do.
 * All users struggled to use the guidance we offered through the help panel while they were editing. This is a major area we need to think hard about designing before we begin to build it.

Recommendations


 * Suggested edits call to action is inside start module, not its own card.
 * Improve copy and user education imagery to better convey that there is real world value in trying suggested edits beyond learning and that task difficulty is a guide only and tasks can be tried out of order.
 * Add an overlay specifically to introduce personalized introduction to suggested edits.
 * Including real-time counting of filtered results on both task and topic filters.
 * Incorporate more granular searching by interest topics by users.
 * Reiterate when a user opens a suggestion that it is a real, impactful edit.
 * Update design of the in-task help panel so that all available help content is clearly accessible.

Measurement and results
To be written