GitLab new user onboarding — Registration Flow/First Mile UX strategy

User persona

Most likely persona to go through the First-mile flow first is the Dev Lead and is most probably trying to learn what GitLab can do and whether it fits their teams' needs.

See also in main onboarding strategy issue:

Based on these, the user at this point is in the second stage of the new user onboarding (First-mile), they're in adoption stage 1 (testing GitLab) and scenario 1.

What is the user's mental model when they decide to try out GitLab?

What do they want to do/find/learn?
What can we do to help them?
What can we do to convince them that GitLab is something they should try out with their team (stage 2 of onboarding)?
How does our current UI and onboarding experience help? How can we do better?

New user sign up	Invited user

Mural

First-mile goals

Main goal: increase interest level and the likelihood of team adoption. (See User scenarios in the main Onboarding UX Strategy issue)

should take users less than 10 mins to complete
users should understand groups & projects
they should get some code into GitLab
NEW: create a flow for invited users that allows them to quickly find & join their team

3 key steps

What are 3 key things that users should know about after they completed the First-mile flow? These 3 key things will help them realise the value of GitLab. It should be enough to increase their interest in GitLab and proceed to the next adoption stage and scenario 2 (pilot team test).

Key Step/understanding	Key Feature	Main problem(s) to solve
They should see how they can collaborate on code	Merge Requests	No code to work with, can't create MRs from the empty state
Integrations with other tools	Project integrations	Project integrations nearly impossible to discover
We can do elaborate CI/CD with GitLab	CI/CD	Don't know where to start?

Forks in the First-mile flow