Continuous onboarding
The goal of this epic is to isolate what we want to achieve within continuous onboarding along with: * isolate what we want to accomplish within the MVC * Set some guardrails on what we want to achieve in the longer-term future vision of continuous onboarding ### Existing mockups | Sam | Kevin | Matej | Mike | Jensen | | ------ | ------ | ------ | ------ | ------ | | ![image](/uploads/887c9837f0729c65615a74aff27f58ec/image.png) | ![image](/uploads/bd639eda6261c907babd6d0631103c37/image.png) | ![image](/uploads/6697d1999ece35995a1a8b5df3495cfd/image.png) | ![image](/uploads/975fc1921daf94296a7e34c85435749f/image.png) | ![image](/uploads/e1eba528761db26571aa53719bded8a2/image.png) | ### MVC In the first test we utilize the same below tasks but break the experience out into three groups control, design 1A, and design 1B. * A set list of onboarding tasks for the namespace to complete, tasks to be included are listed below: 1. Create a repo 1. Set up your first pipeline 1. Open an issue 1. Create a MR and invite a colleague to review your code 1. **a-ha moment:** Review is done, pipeline is green, MR is merged and issue is closed automatically :raised_hands: 1. Start a trial * A progress bar should be displayed to the user on every page to indicate what percent complete they've completed, until the list of items is completed. * It should be built in a way where it's _relatively easy_ for us or another growth team to test swapping what onboarding tasks are present in the list to enable future growth experiments | Control | Design 1A | Design 1B | | ------ | ------ | ------ | | ![image](/uploads/dea10dd9e52d8940918c6b7cd53999a5/image.png) | ![image](/uploads/47a60e46ea755e2b94d4c12ab31b129d/image.png) | ![image](/uploads/2c75cc880188e8636d98b6f5e9fefc5e/image.png) | | Current experience for new users | [Engineering issue](https://gitlab.com/gitlab-org/gitlab/-/issues/281022) | [Engineering issue](https://gitlab.com/gitlab-org/growth/team-tasks/-/issues/306) | ### Future vision * The list should be dynamic based on user/namespace actions - i.e. it should have different content for trials vs free users, if a namespace completes the initial onboarding steps then more advanced tasks should automatically be added * The content should be JTBD specific for the user as well as contain namespace tasks * The list items and their status of open or completed should be shared with the marketing team so it can be included in email content * We should remind users of their incomplete onboarding tasks in-app at appropriate moments
epic