Investigation of new onboarding wizard for Access (organization building)

Problem Statement

In our CMS of Subgroups we determined that new users have a difficult time of understanding how they "start" in working within the GitLab environment in order to build an organizational system that can mirror their company.

Reach (1.5 = ~5% to ~25% of new users)

The reach of this problem affects system admins or platform engineers who set up the environment for their organizations.

Personas:

• Sidney (Systems Administrator)
  • I maintain and scale our infrastructure and configurations, and my priority is to automate as much as possible. When needed, I also build servers and help developers deploy to them.
• Priyanka (Platform Engineer)
  • I have responsibility for providing, maintaining and operating a shared modern cloud platform which my application development teams utilize to develop, test, ship and operate software more quickly. My team is increasingly being asked to manage our cloud platform like a product - internal.

This presumably affects a small number of users, (1.5 = Small reach presumably ~5% to ~25% of new users).

Impact (2.0 = High impact)

Allowing users to quickly:

• set up their organization
  • define organizational structure
  • enact security controls
• import their users and manage memberships
  • assign to teams/projects
  • define access roles/restrictions ... would allow for less time spent in the set up phase for new GitLab accounts.

Confidence

80% = Medium confidence, see related CMS: gitlab-design#1370 (closed)

• Further research needed

Effort

Currently there is a collaborative effort to improve onboarding by the devopsgrowth team. The work involved might be rated a 3.0 on first guess.