Change Details

This task is about designing what the user experiences as we ask them additional questions. This will evolve even as engineers begin to prototype the experience in T206371, and it will affect the requirements listed in that task. @RHo will own and drive this task, potentially making sub-tasks and mock-ups. Below are notes from previous conversations with the team around design. * Although for the very first version, we will not deploy on mobile web, we will add mobile soon thereafter (within weeks), so the below considerations are also applicable to mobile web. * We may need to develop user flows for where users come from when they create accounts, so that we can be mindful of how disruptive the new experience is for users who were in the middle of editing when they created their account. * Should this be an overlay, a new page, or something else? * Should the form contain information besides the questions we want users to answer, such as links to help documentation? * Should the form prompt users again to enter an email address? * When does the form get displayed? Immediately after account creation? Back in the editing context? After saving that first edit, if the user created their account mid-edit? * Should users be allowed to complete the form later? If so, how do we prompt them, and where do we send them? Some ideas: ** An echo notification prompts them several hours after first declining the form. ** Via email. ** The overlay pops up again at some other time. ** A bot could request that they do it via their talk page.

== Background Per the epic task T206365, part 1 of the "Personalized first day" idea will be to gather more information from New Editors when they first create an account. The following outlines the form design to present to newly created accounts. == User job story **When** I finish creating an account on Wikipedia... **...I want to** get guidance on what I can do post-sign up... **...so that I** feel welcomed and and can easily get started on contributing to Wikipedia. == Proposed design The following outlines initial designs of the form informed by previous a comparative review of similar post sign-up survey forms (see T206373), initial feedback from Community consultations, and Engineering recommendations (see task T206371#4659748) . In all variations, the user is only being shown the form AFTER successfully creating a new account. === Variation A. Form on a single Special page ====Mocks - see Invision prototype at: https://wikimedia.invisionapp.com/share/PBOLQ4KX479#/screens/326072425 - **Notes on the design:** - "Getting started" secondary section is included to see if providing more upfront help for editing increases Editor activation, esp. for user who do not complete the form. - All fields are shown on one page, with user returning to their pre-account creation context after selecting Skip or Submit. === Variation B. Multi-step form on a simplified Special page ====Mocks - see Invision prototype at: https://wikimedia.invisionapp.com/share/PBOLQ4KX479#/screens/326251031 - **Notes on the design:** - The reduced chrome (no sidebar and simplified top navigation) is modeled on the [[ https://en.wikipedia.org/wiki/Special:ContentTranslationStats | Special:ContentTranslation ]] tools pages - One to two questions per step makes it less daunting for the user - Selecting the radio options for Q1 and Q2 will auto advance users to the next step - There is a more prominent SKIP button - Added another side section about privacy and data collection for consideration per initial feedback (can also apply to other design variations) === Variation C. Form shown on a modal over pre-account creation context ====Mocks - TBC This proposed design is based on the comparative review and initial testing suggesting that showing users an optional form in this format is seen as less imposing and distracting from their original context. ____________ **Open questions: ** * Should users be allowed to complete the form later? If so, how do we prompt them, and where do we send them? Some ideas: ** An echo notification prompts them several hours after first declining the form. ** Via email. ** The overlay pops up again at some other time. ** A bot could request that they do it via their talk page. **Subtasks: ** - Survey question copy - update task T206375 - Test usability of design - RHo to file task to create UserTesting study - Provide Mobile version of flow: Although for the very first version, we will not deploy on mobile web, we will add mobile soon thereafter (within weeks), so the below considerations are also applicable to mobile web.

This task is about designing what the user experiences as we ask them additional questions. This will evolve even as engineers begin to prototype the experience in T206371== Background Per the epic task T206365, part 1 of the "Personalized first day" idea will be to gather more information from New Editors when they first create an account. The following outlines the form design to present to newly created accounts. == User job story **When** I finish creating an account on Wikipedia... **...I want to** get guidance on what I can do post-sign up... **...so that I** feel welcomed and and can easily get started on contributing to Wikipedia. == Proposed design The following outlines initial designs of the form informed by previous a comparative review of similar post sign-up survey forms (see T206373), initial feedback from Community consultations, and it will affect the requirements listed in that taskEngineering recommendations (see task T206371#4659748) . @RHo will own and drive this task,In all variations, the user is only being shown the form AFTER successfully creating a new account. === Variation A. Form on a single Special page ====Mocks - see Invision prototype at: https://wikimedia.invisionapp.com/share/PBOLQ4KX479#/screens/326072425 - **Notes on the design:** - "Getting started" secondary section is included to see if providing more upfront help for editing increases Editor activation, esp. for user who do not complete the form. potentially making sub-tasks and mock-ups. Below are notes from- All fields are shown on one page, with user returning to their previous conversations with the team around design-account creation context after selecting Skip or Submit. * Although for the very first version,=== Variation B. we will not deploy on mobile web, we will add mobile soon thereafter (within weeks), so the below considerations are also applicable to mobile web.Multi-step form on a simplified Special page ====Mocks - see Invision prototype at: https://wikimedia.invisionapp.com/share/PBOLQ4KX479#/screens/326251031 * We may need to develop user flows for where users come from when they create accounts, so that we can be mindful of how disruptive the new experience is for users who were in the middle of editing when they created their account.- **Notes on the design:** * Should this be an overlay, a new page, - The reduced chrome (no sidebar and simplified top navigation) is modeled on the [[ https://en.wikipedia.org/wiki/Special:ContentTranslationStats | Special:ContentTranslation ]] tools pages or something else?- One to two questions per step makes it less daunting for the user * Should the form contain information besides the questions we want users to answer, such as links to help documentation?- Selecting the radio options for Q1 and Q2 will auto advance users to the next step * Should the form prompt users again to enter an email address? - There is a more prominent SKIP button - Added another side section about privacy and data collection for consideration per initial feedback (can also apply to other design variations) === Variation C. Form shown on a modal over pre-account creation context * When does the form get displayed? Immediately after account creation? Back in the editing context? After saving that first edit, if the user created their account mid-edit?====Mocks - TBC This proposed design is based on the comparative review and initial testing suggesting that showing users an optional form in this format is seen as less imposing and distracting from their original context. ____________ **Open questions: ** * Should users be allowed to complete the form later? If so, how do we prompt them, and where do we send them? Some ideas: ** An echo notification prompts them several hours after first declining the form. ** Via email. ** The overlay pops up again at some other time. ** A bot could request that they do it via their talk page. **Subtasks: ** - Survey question copy - update task T206375 - Test usability of design - RHo to file task to create UserTesting study - Provide Mobile version of flow: Although for the very first version, we will not deploy on mobile web, we will add mobile soon thereafter (within weeks), so the below considerations are also applicable to mobile web.