Problem validation: Understanding MRs without pipelines
What's this issue all about? (Background and context)
The Expansion team has a belief that MRs without pipelines are a good opportunity for paid growth. They're currently running an experiment to prompt users on MRs without pipelines to create one. However, we still don't have a great understanding of why users don't utilize CI, their understanding of it or how they interpret the value of CI.
We also have a Growth OKR for Q2 to increase stage usage for active namespaces, so hopefully this will contribute to that.
What are the overarching goals for the research?
Learn about some of the reasons why users have not enabled CI, whether technical or conceptual.
What hypotheses and/or assumptions do you have?
- There are some straightforward reasons why people are not using CI that we could address via UX changes.
- There are gaps in understanding of CI that are knowledge or value-based that could be addressed through educating the user.
What research questions are you trying to answer?
Why do users that use MRs not utilize CI pipelines? What is these users' understanding of CI? How do they perceive the value of CI?
What persona, persona segment, or customer type experiences the problem most acutely?
- Authors of recent merge requests that are not using CI in any of their groups
- Members of subscription groups with at least 5 seats but not more than 50 seats
- Groups do not have a Jenkins integration currently active
What business decisions will be made based on this information?
Whether (and how) to iterate on our current experiments to encourage CI usage on MRs without pipelines.
What, if any, relevant prior research already exists?
TODO Checklist
-
UX Researcher: Create recruiting data warehouse query and pull user list. -
UX Researcher: Create the screening survey in Qualtrics. -
UX Researcher: Draft discussion guide -
Product Manager & Designer: Review the discussion guide. -
UXR/PM/PD: Conduct the interviews. -
Research Coordinator: Pay participants. -
Product Manager and UX Researcher: Synthesize the data and identify trends in Dovetail, resulting in insights. -
UX Researcher: Update the Problem validation
research issue. Link to findings in Dovetail. Unmark asconfidential
if applicable. Close issue.
cc: @timhey @matejlatin