Internal code review process problems
✨ Insights📺 Insights walkthrough (8 min)🕊 Dovetail project❓ Qualtrics survey- Survey outline (Word)
What's this issue all about? (Background and context)
In the 2020-12-16 Code Review UX Sync, @pedroms and @phikai discussed aligning the philosophy of the Code Review stage group with the code review principles of GitLab the company.
If we’re trying to align our philosophy with the way we work as a company, we thought about looking inward and ask our team members what's the most frustrating part of the code review process.
What are the overarching goals for the research?
Understand how GitLab engineers prioritize problems in the code review process. This will help inform our roadmap for the Code Review group.
What hypotheses and/or assumptions do you have?
What research questions are you trying to answer?
What's the most frustrating part of the code review process for GitLab engineers?
What persona, persona segment, or customer type experiences the problem most acutely?
What business decisions will be made based on this information?
Research findings will be used as inputs to plan the roadmap of the Code Review group.
What, if any, relevant prior research already exists?
What timescales do you have in mind for the research?
Who will be leading the research?
Relevant links (opportunity canvas, discussion guide, notes, etc.)
TODO Checklist
-
Product Designer: Draft the survey. -
Product Designer: Transfer the survey questions to Qualtrics. -
Product Designer: Distribute the survey. -
Product Designer: Review responses received so far. Amend survey, if needed. -
Product Designer: Close survey. -
Product Designer and UX Researcher: Synthesize the data and identify trends, resulting in insights. -
Product Designer: Document insights in Dovetail. -
Product Designer: Update the Problem validation
research issue. Link to findings in Dovetail. Unmark asconfidential
, if applicable. Close issue.