Improve empty states to drive feature adoption for first-time users

Context

  • Multiple UX studies have cited that users struggle with GitLab terminology, especially coming from other platforms.
  • Empty states help onboard new users to GitLab terminology and features and can be used as a lever to drive adoption

Scope of this issue

  • Audit empty states for features tied to team activation
  • Ideas to explore:
    • UI copy improvements - how do we better onboard users from another platform?
    • Show empty states for users joining an existing namespace (closed issue, consolidated into this issue)
    • Show call-to-action to invite members to the namespace (closed issue, consolidated into this issue)
  • Conduct solution validation on design exploration
  • Potentially roll out new empty states as an experiment

Further information

UX research - users struggle with GitLab terminology:

Previous experiments have aimed at leveraging empty states as a lever to drive early adoption:

Edited by 🤖 GitLab Bot 🤖