<!--Actionable insights must recommend an action that needs to take place. An actionable insight both defines the insight and clearly calls out action or next step required to improve based on the result of the research observation or data. Actionable insights are tracked over time and will include follow-up. Please follow the tasks outlined in this issue for best results. Learn more in the handbook here: https://about.gitlab.com/handbook/engineering/ux/ux-research-training/research-insights/#actionable-insights This issue template is for an actionable insight that requires a change in the product.--> ### Insight <!--Describe the insight itself: often the problem, finding, or observation.--> Users are often confused on the different between 'start a review' and 'add comment now' -- they do not know when to use each one, what the differences are in effect, and why certain ones are the default option.  ### Supporting evidence <!--Describe why the problem is happening, or more details behind the finding or observation. Try to include quotes or specific data collected. Feel free to link the Actionable insight from Dovetail here if applicable instead of retyping details.--> In the Q1FY23 Create stage benchmarking study, participants were confused by these two buttons and what actions they represented. It seemed strange to them that ‘start a review’ was the default choice, even when simply replying to a comment. Users appreciated the idea of submitting multiple comments together as a review, but the presentation made it unclear how to properly make use of it. > I was a little confused about ‘starting a review’ versus adding a comment. I’m still not sure if ‘adding a comment now’ starts a review, or if starting review initiates another workflow. – S-04 > ...that term completely threw me off - ‘comment’ versus ‘code review’. I know those are two different things. I just hoped that comment meant code review. – S-10 Additionally, several comments during the recommendations workshop support this evidence: > I still don't fully understand why we have comments AND "start a review" and I never know which one to pick. -Workshop participant > I've always been confused about the utility of the `Start Review` button. Consider making that more clear or removing it as the primary action. -Workshop participant Sept 16th 2025: https://gitlab.slack.com/archives/CLW71KM96/p1757632568156499 ### Action <!--Since this is an actionable insight that requires a change in the product, ensure the action is algned to that. Describe the next step or action that needs to take place as a result of the research. The action should be clearly defined, achievable, and directly tied back to the insight. Make sure to use directive terminology, such as: change, update, add/remove, etc.--> The following recommendation was voted for during the recommendations alignment workshop after the Create stage benchmarking: - Clarify the different between 'start a review' and 'add comment now' (6 votes) ### Resources <!--Add resources as links below or as related issues.--> - :dove: [Dovetail project](https://dovetailapp.com/projects/30oYRVm3wl8esIuImxTdrz/v/5hZuPwhf3XBWiHicyCchQ9) - :mag: [Research issue](https://gitlab.com/gitlab-org/ux-research/-/issues/2882) - :footprints: Follow-up issue or epic ### Tasks <!--Fill out these tasks in order to consider an Actionable Insight complete. Actionable Insights are created as confidential by default, but can be made non-confidential if the insight does not include information about competitors from a Competitor Evaluation or any other confidential information.--> - [x] Assign this issue to the appropriate Product Manager, Product Designer, or UX Researcher. - [x] Add the appropriate `Group` (such as `~"group::source code"`) label to the issue. This helps identify and track actionable insights at the group level. - [x] Link this issue back to the original research issue in the GitLab UX Research project and the Dovetail project. - [ ] Adjust confidentiality of this issue if applicable