UX: Define Admin feature discovery experience
Summary
The purpose of this modal is to enable users to learn about the paid features that could make their current tasks easier as well as pitch the overall value of a paid tier. This modal should provide the user with options to Start a trial
Contact sales
and Upgrade now
in the Admin experience. In future when we develop a non-admin experience it will allow non-admins to request access from their admin.
graph TD;
A[User interacts with feature discovery experience]-->B[Admin upgrade module];
A-->C[Non-admin upgrade module];
B-->D[Start a trial];
D-->M[customer.gitlab.com trial / upgrade funnel.];
F-->M;
B-->F[Upgrade now];
B-->I[Talk to sales];
I-->O[Talk to sales form submitted];
B-->H[User selects to close module];
C-->E[Request a trial from your admin];
C-->E[Request an upgrade from your admin];
C-->E[Request an colleague to be invited from your admin];
C-->J[User selects to close module];
E-->K[Submit some type of admin request];
K-->N[Admin gets notified and views request in a UI with all requests];
N-->Q[Trial, upgrade or user gets added if Admin approves];
For this issue we will focus on the UX vision for the Admin experience
The MVC version of this modal should be specific to admins (users capable of upgrading/starting a trial). However, we should leave it open/flexible enough to allow for non-admin to learn about paid features/request access from their admins in future iterations.
Kevin previous worked on this concept gitlab-org/growth/product#35 (closed) coming up with three core designs depending on the location/amount of space in-app:
Accordion:
Embedded:
Full page:
issue)
Highlighting paid feature during a trial (Questions we need to answer:
- From a user experience perspective is it better to have different variations of the feature discovery experience or is better to have one experience that appears via something like a modal or embedded in the page?
- From a scaling perspective if we think about recommending that additional teams utilize the feature discovery experience, is it better for us have multiple variations available or should we consolidate it under a more unified experience like a modal?
- For non-full page versions is it better for us to think about using a modal so all other teams can simply think about needing a CTA that calls open the model and the content they've designated to be within the modal and we intelligently display the right CTA i.e. if they're an admin we show "upgrade now" "talk to sales" "start a trial", if they're not an admin we display "request a trial" "request an upgrade"?
- I think we should ensure all three core CTAs fit within each design, do we think they will fit within these designs? If not, how can they be adjusted to support all three primary CTAs?