Validate Code Review JTBD
From https://gitlab.com/gitlab-org/competitor-evaluations/-/issues/27#note_695553428 and a recommendation from Create hypothesis-based user journey map of Cre... (&6964 - closed): create-stage#12950 (closed)
To move forward and build one or more research-based maps, we need to do more investigation. Our recommendations, in order:
- Validate the JTBDs for Code Review. In particular, looking at the JTBD that was chosen for this exercise to understand if it's at the right altitude and properly phrased.
- After the JTBDs are validated, we should be in a better place to answer the general questions.
- Depending on what we've learned, we may need to dig deeper into the other least confidence areas.
Problem
Our current JTBD are quite broad and don't necessarily encompass all that Code Review offers.
When product improvements are identified, I want to propose changes that address them, so that I can help build a better product.
When my teammates propose changes, I want to review them before they are accepted, so that I can help increase the quality of changes, minimize the risk of defects, minimize the risk of out-of-scope changes, and grow the team’s expertise.
When my teammates propose changes, I want to ensure they are reviewed and accepted according to internal guidelines, so that we can increase the quality of changes, minimize the risk of defects, and maximize the reliability of product data.
Proposal
Reevaluate (possibly rewrite, expand upon, add to, and validate) our current JTBD.