Self-managed Upgrade Insights from Admins.
What’s this issue all about?
We are in the workflowproblem validation stage for this epic which consists of 4 MVC's that we considering to enhance the upgrade experience for self-managed admins.
We are looking to conduct some research to further validate our ideas.
Who is the target user of the feature?
The target user for these MVCs are billing admins of self-managed accounts.
We don't have a persona documented for this user today but If i had to align them with one of the personas we have they'd be these: Buyers personas
- Directors
- Managers
What questions are you trying to answer?
- How do they navigate GitLab to upgrade their account
- How do they find information about their account
- What do they do when they want to upgrade
- Are they aware of our technical documentation for upgrading and or the customer portal?
- FYI we reference the customers' application internally as the customers' app but in the documentation, we call it the 'GitLab Subscription Manager'
Core questions
What would make it easier for them to know to either contact their sales rep or use the GitLab Subscription Manager to self-serve?
Additional questions
What hypotheses and/or assumptions do you have?
- We are assuming that admins don't have all the information they need to make an educated purchasing decision without contacting sales.
- We are assuming that admins would want to have an easier path to self-serve from the GitLab ui.
- Another assumption would be that an admin was provoked by a user to upgrade the license or buy an add-on
What decisions will you make based on the research findings?
- We'll update/course correct the MVCs outlined in this epic.
What's the latest milestone that the research will still be useful to you?
Edited by Tim Hey