Growth/Understanding first day/eu

Orri honetan deskribatuta dago Hazkunde taldearen lana, «Lehenengo eguna ulertzea» proiektuari dagokienez. Proiektu hori Editore Jardunaldia izenaz ere ezaguna da. Orri honetan jasota daude helburua, planak, erabakiak eta emaitzak. Aurrerapenei buruzko eguneratze inkremental gehienak Hazkunde taldearen eguneratzeen orrian argitaratuko dira. Eguneratze handi edo xehetasunezko batzuk, berriz, hemen argitaratuko dira.

Proiektu hau osorik instrumentazioari eta neurketari buruzkoa denez, Wikimedia Fundazioko lantalde asko ari dira proiektua eratzen, hala nola: Legeetakoa, Segurtasunekoa, Ingeniaritza Analitikokoa eta Produktu Analitikakoa. Guztiontzat garrantzitsua da gure erabiltzaileen pribatutasuna errespetatzea, erabiltzaile horien esperientziak hobetzeko behar duguna oraindik ikasten ari garen bitartean. Hori egiteko bide egokienaren bila etengabe lanean ari garenez, orri honetan deskribatutako planak aldatuz joango dira.

Given the attention we have about privacy, we won't deploy EditorJourney to new wikis.

Uneko egoera

 * 2018-11-19: Editore Jardunaldia eredua ezarri da Txekierazko Wikipedian eta Koreerazkoan.
 * 2019-01-15: Editore Jardunaldiari buruzko hasierako txostena argitaratu da hemen.
 * 2019-01-16: Editore Jardunaldia eredua ezarri da Vietnamerazko Wikipedian.
 * 2019-07-01: EditorJourney schema deployed on Arabic Wikipedia.
 * Hurrengoa: 2019ko lehen hiru hilabetean, Vietnamerazko Wikipediako lehen emaitzei begiratuko diegu, eta datu multzo osoaren azterketa sakonagoa egingo dugu.

Laburpena
Kontua sortzen duten erabiltzaile gehienek ez dute inoiz ediziorik egiten. Hala ere, ediziorik egiten duten gehienek kontua duten lehenengo egunean egiten dituzte. Ezer gutxi dakigu kontu berrien jabeek kontua sortu ondorengo egunean egiten dutenaz: ea laguntzeko edukia irakurtzen duten, ea gero argitaratzen ez dituzten edizio probak egiten dizuten, edo besterik egiten duten. Hasierako saio horiei buruz gehiago jakiteak haien esperientzia hobetzen lagunduko liguke; eta kontu berrien jabe gehiagok lehen egunean edizioak egin ditzaten lortuko genuke. Kontu berrien jabeek beren lehen egunean zer egiten duten ulertzeko, Txekierazko Wikipediako eta Koreerazko Wikipediako erabiltzaile berrien esperientziak jaso ditugu, galdera hauei erantzuteko:


 * Zein dira Txekierazko Wikipediako eta Koreerazko Wikipediako kontu berrien jabeen lan fluxu ohikoenak, beren lehen 24 orduan?
 * Kontu berrien jabe horietatik zer proportziok jotzen du lan fluxu horietako bakoitzean barrena?
 * Zer lan fluxu dira kontu berrien jabe horiek edizioetara eramaten dituztenak eta ez dituztenak?

Hazkunde taldea galdera horiei erantzuteko lanean ari da. Horretarako, aztergai diren wikipedietako (txekierazkoa, koreerazkoa eta vietnamerazkoa) erabiltzaile berri guztientzat Gertaera-erregistratze tresnak gehitu ditu, erabiltzaile horietako bakoitzak kontua sortu ondorengo 24 orduan. Erabiltzaile berriaren esperientziaren ikuspegi garbia izan dezagun, halaber gure asmoa da hainbat eginbideren (hala nola Echo, Ikusizko Editorea eta Ibilaldi Gidatua) inguruko beste Gertaera-erregistratze ahalegin batzuekin konektatzea eta haietatik ateratako datuak erabiltzea. Gaitasun hori lehenengoz 2018ko azaroan ezarri zen Txekierazko Wikipedian eta Koreerazko Wikipedian, eta hasierako txosten bat argitaratu zen 2019ko urtarrilean.

Hemen dago jasota proiektu horri buruzko jatorrizko komunitate eztabaida.

Why this project is prioritized
Our research has taught us a lot about the motivations and needs of new editors, and one of the most important things we learned is that a new editor's very first experiences with editing can be the deciding factor for whether they continue to edit. Most people who create accounts in Wikipedia never make an edit, but of those who do, that edit tends to happen on the day they create their account. In conjunction with the "Personalized first day" project, this project is critical for continuing our learning on those first moments of attempting to edit. We need to know more about how new editors approach their first edits, so we know where to plug in and help. For instance, if we see a lot of new editors reading help content, but then not attempting an edit, we might conclude that help content is important but not helpful as currently written and presented. Or if we see a lot of new editors going straight to opening the editor, but then leaving before saving an edit, we might conclude that the most important place to provide help is inside the editing experience.

We prioritized this project because:


 * It helps us increase our learning at this early stage of our team's work with new editors.
 * Community members were positive in their feedback on the idea.
 * It lays the groundwork for learning whether changes we make to the new editor's experience change their behavior.
 * It will be easy to translate and apply to other wikis in the future.

Specifications
This section contains the evolving plans for measurement.

Overall parameters

 * Will apply to all new accounts created in Czech and Korean Wikipedias, but will exclude auto-created accounts from other wikis.
 * Will be active for the first 24 hours of the existence of a new account.
 * At the user level, will record visits to pages in namespaces where new editors might be seeking help, such as the Help, Wikipedia, or User namespaces (and their associated Talk spaces).
 * For pages in more sensitive namespaces, such as Article, Draft, or Portal, will record only that the namespace was visited, not the specific page title.
 * Data will only be available to people with NDA access.
 * Data will be anonymized, deleted, and/or aggregated after 90 days.

Specific questions
The outline below lays out the specific questions we want to answer with this instrumentation effort. Most of these questions will be answered with the new EditorJourney EventLogging schema being built for this project. Some questions, especially those under #4 ("After the editing experience begins") will be answered by connecting with existing EventLogging schemas built to measure existing features.


 * 1) Context: How often do accounts get created from the different possible account creation contexts?
 * 2) * Homepage
 * 3) * Reading experience
 * 4) * Editing experience
 * 5) Survey: When shown the “Personalized first day” survey right after account registration, do users respond to one or more questions in the survey, or skip the survey altogether and go back to what they were doing prior to account registration?
 * 6) After account creation, what are the various common workflows that new account holders go through before making an edit (or before never making an edit)?  We want to count the frequency of workflows such as, but not limited to, the following.  The reason it’s “not limited to” is that we don’t yet know which workflows we will discover.
 * 7) *Reading articles first: reading many pages in the Article namespace and then either leaving or editing.
 * 8) * Learning first: Consuming some sort of learning content and then either leaving or editing.  This content is found in namespaces other than Article namespace, or through certain actions that may not be captured in page views or existing schemas:
 * 9) ** Viewing content in the Help, Wikipedia, or User namespaces (among others), including help desks
 * 10) ** Clicking on a link in a welcome message on their own user talk page
 * 11) ** Opening and reading notifications
 * 12) ** Opening and updating account settings / preferences
 * 13) ** Verifying or adding/updating email address.
 * 14) * Straight to editing: going straight to editing without reading many articles or any learning content
 * 15) ** This can either happen because the account was created from the editing experience, or the reader opened the editor from the reading experience soon after account creation.
 * 16) ** Is this the creation of a new page?
 * 17) ** When opening the editor, some wikis display a GuidedTour or GettingStarted.  Did the user click on anything in GuidedTour or GettingStarted?
 * 18) * Any combination of the above, such as a workflow in which users read some articles, followed by reading a help page, followed by starting and abandoning an edits, followed by a successful edit.
 * 19) After the editing experience begins, what percent of users successfully save an edit?  And for those who abort their edits, what do they do in the editor before aborting?
 * 20) * On what page is the attempted edit happening?
 * 21) * How often do users quickly exit the editor without actually interacting with the page?
 * 22) * How often do users do a substantial amount of interaction with the page before aborting?
 * 23) * How often do users switch the type of editor?
 * 24) * If the edit was saved, how many bytes changed in the edit?
 * 25) * Was the resulting edit reverted or thanked?
 * 26) After saving or aborting an edit, what happens next?  (Return to Step 3).

Other schemas
This is a list of some of the other EventLogging schemas we may use to enrich the picture of what new account holders do in their first hours on the wiki:


 * ServerSideAccountCreation
 * Echo
 * EchoInteraction
 * PrefUpdate
 * EditAttemptStep
 * VisualEditorFeatureUse
 * Page creation
 * GettingStartedRedirectImpression
 * GuidedTourButtonClick
 * GuidedTourExited
 * GuidedTourExternalLinkActivation
 * GuidedTourGuiderHidden
 * GuidedTourGuiderImpression
 * GuidedTourInternalLinkActivation

User flows
In planning out this project's measurement and analysis needs, our team's designer assembled some visual user flows that help us chart out the journey of new users during their first hours in the wiki. As it says in the slides linked below:"'The following user flows document the various pathways newly created Wikipedia accounts can take to become a newly 'activated' editor (after making a first edit), to being retained (2nd edit), through to 'survival' (3rd edit within first 6 weeks). The diagrams note the desired data to be captured at each user interaction, with the intention to both help the Growth team identify the various points for instrumentation, as well as helping visualize the funnel of New Editor retention.'"Though the flows extend our thinking to multiple edits in a new user's journey, we have since decided to constrain our measurement to just their first day.

The full slide deck is here, and also linked on this Phabricator task. At right is the image of the full user flow, which is the main slide from the slide deck. Please note that these are presented as an artifact of our team's thinking, but are no longer being updated as our approach continues to evolve. The Specifications section above reflects the current approach.

Analysis
Because the EditorJourney data records much detail on what newcomers do on their first day, we'll be able to ask and answer many questions using the dataset. In this sense, our analysis will never be complete, and we can always use the dataset to answer additional questions about newcomers. This section lists the analyses that have been completed. Community members should feel free to translate any of these reports into their languages. Future analyses will continue to address the list of questions in the "Specifications" section above.


 * EditorJourney initial report: the first report using the EditorJourney dataset, addressing the questions of what context newcomers create their accounts from, and how many newcomers do which activities at some point on their first day. Some important toplines:
 * This data substantially clarifies our understanding of newcomers: many of them notice outreach, look for help content, and a majority of them open an editor. It's good news that so many are engaged and trying to succeed, and the clarity gives us opportunities to meet them where they are, so that when they go looking for something helpful, they find it.
 * Large numbers of users view help or policy pages on their first day: 41.5% in Czech and 27.8% in Korean.
 * Large numbers of users view their own User or User Talk page on their first day: 33.8% in Czech and 39.3% in Korean.
 * A majority of new users open an editor on their first day – but about a quarter of them do not go on to save an edit during that time.