Design a consistent empty state pattern that drives Team Activation and early stage adoption
Placeholder issue to capture insights around empty states.
Previous experiments have aimed at leveraging empty states as a lever to drive early adoption:
- https://gitlab.com/gitlab-org/gitlab/-/issues/340436#note_1312120443
- #352850 (comment 1312139478)
- https://gitlab.com/gitlab-org/gitlab/-/issues/291165
However we decided that we should develop a consistent strategy for empty states rather than develop them one-off.
Ideas:
- We should audit all empty states and focus on ones that drive Team Activation / early adoption of important features (like Secure)
- If appropriate, we should include "invite" CTAs on empty states: #389827
Edited by Paige Cordero