Survey on code owners experience
What’s this issue all about?
We know that code owners provides tremendous value to those making use of it, however, the feature is not very discoverable and once discovered, has a medium learning curve.
We'd like to empower everyone to make use of this feature, by making it more discoverable and easier to use.
This survey will help us gain understanding around the experience of initial code owners use. We are trying to identify users who found it hard to get started. Once we find said users, we will attempt to conduct solution validation with the applicable cohort.
What is the goal of the survey
The main goal is to find users who use code owners and found it difficult to get started. We will use this cohort to conduct user interviews and validate the problem.
Further info
- Make it easy to get started with code owners &5888 (closed)
- High-level summary of insights from CMS
- JTBD 3 (some code owners content) Results
- Related canvas lite gitlab-com/Product#2486 (closed)
- Recruiting https://gitlab.com/gitlab-org/ux-research/-/issues/1445
What hypotheses and/or assumptions do you have?
- Users facing the problem code owners is designed to solve don't know about the feature
- Ramp-up may seem too lengthy and users may abandon use when reading docs
- Users who find out about the feature may abandon use in favor of plain approval rules to save time on ramp up
Some of the activities we can carry out to increase confidence:
- Interview users who don't currently use the feature and have team sizes where ownership signals help other developers finding out who to reach out to and who is the expert in a particular area.
- Interview users who don't currently use the feature and are looking to implement approval rules for their workflow.
- Interview users who currently use the feature on their team but not necessarily company-wide. This would help us validate that the problem of initial setup correlates to the learning curve and possibly discoverability of the feature.
- Run contextual interviews for users who are about to embark on the journeys above (not sure if realistic).
What questions are you trying to answer?
- How do you signal code-base ownership?
- How do you ensure relevant users review code changes?
- Do you know about code owners?
- Does all projects in your org use code owners? Why, why not?
- How would you rate the ease of setup for code owners?
- Do you know about code owners sections?
Core questions
Based on the above answers we may know what to ask next, but the core validation we're after is around the discoverability and usability of the feature.
Additional questions
What persona, persona segment, or customer type experiences the problem most acutely?
Timescale
Initial survey completion in 2 to 3 weeks, where hopefully we can find ~10 users to conduct interviews with.
Relevant links
- Opp canvas lite gitlab-com/Product#2486 (closed)
- Full opp canvas https://docs.google.com/document/d/18g7bUoXX4-gDXwp72GSjzdSCLFya7JYBo_s--naVn-Q/edit?usp=sharing
- Qualtrics survey https://gitlab.eu.qualtrics.com/surveys/SV_3PLuw89N16WvSqW/edit?Section=SV_3PLuw89N16WvSqW
- Dovetail project https://dovetailapp.com/projects/d2a803a0-b4c7-4931-a11f-934ae1ef8f45/