GitLab ROI & DevOps Score - Problem Validation
What’s this issue all about?
In DevOps score exploration, we are trying to help users prove the value of using GitLab. We will design an MVC for a new feature section in Instance Analytics which helps users understand and communicate GitLab's ROI.
This issue is to define our research plan for the problem validation and solution validation required to inform this DevOps Score MVC.
Who is the target user of the feature?
- Director of DevOps - Buyer Persona
- Parker, Product Manager - User Persona
- Gabe, Engineering Director - User Persona
Research Goals
- GitLab ROI - Understand how customers best think they can demonstrate the value of adopting GitLab
- Test solution ideas - Show customers some ideas around this topic and get their feedback
What questions are you trying to answer?
Core questions
- What information/metrics do users need to demonstrate the ROI of adopting GitLab?
- What dimensions are important for understanding DevOps maturity?
- What information do users have available currently? What information is missing?
- How will users want to use DevOps maturity information - what actions will they take off the back of it?
Additional questions
- What information/metrics are important for understanding the progress of their DevOps transformation?
- How might benchmarking work?
What hypotheses and/or assumptions do you have?
- Instance-level analytics (rather than group or project) will provide customers with the best short-term solution for proving ROI on GitLab
- Senior business stakeholders needs some education on DevOps metrics and connecting them back to business value
- A “DevOps Score” (single metric aggregate of feature adoption) will help customers justify the purchase/renewal of GitLab as a tool
- GitLab feature adoption is a good proxy for understanding how mature DevOps teams are and how well they are performing
What decisions will you make based on the research findings?
- MVC design decisions
What's the latest milestone that the research will still be useful to you?
- 12.8
Progress
-
Katherine: Recruit from CAB channel on Slack [Deadline: 2020-1-21] -
Schedule 3-5 customers for interviews. [Target Deadline: 2020-1-29] - https://gitlab.com/gitlab-org/ux-research/issues/629 -
Customer 1
-
-
-
Nick: Draft discussion guide [Deadline: TBD] -
Katherine: Finalize discussion guide. [Deadline: TBD]
-
-
Nick, Katherine: Conduct interviews. [Deadline: TBD] -
Katherine: Open an Incentive request issue using the template in the UX Research project [Deadline: TBD] -
Nick, Katherine: Analyze and synthesize data. [Deadline: TBD] -
Nick: Document findings within the UXR_Insights repository [Deadline: TBD] -
Nick: Schedule a meeting to share results with stakeholders. [Deadline: TBD] -
Nick: Update the Research proposal issue. Link to the insights Epic. Unmark as confidential if applicable. Change status to done and close issue. [Deadline: TBD]
Links
Edited by Katherine Okpara