Customer journeys
Background:
As part of https://gitlab.com/gitlab-org/gitlab-ce/issues/32638, I want to understand the customer journey(s) as someone gets started with GitLab, and especially GitLab CI/CD. My badly captured thoughts:
Customer journeys: problem, search, grok, signup, play?, browse?, push? (New to git vs new to GitLab vs new to CI vs new to GitLab CI vs just new install (new to installing, vs just another install, leave me alone). ), issue, MR, board, label, milestone, CI...
What questions are you trying to answer?
How and why do people get started with GitLab, and especially GitLab CI/CD? Assuming the farther/deeper someone gets into the journey, the higher their LTV, what can we do to make that journey more successful?
Are you looking to verify an existing hypothesis or uncover new issues you should be exploring?
What is the backstory of this project and how does it impact the approach?
We want to increase adoption of CI/CD/DevOps in general, but also explicitly part of our Q3 OKRs.
What do you already know about the areas you are exploring?
What does success look like at the end of the project?