UX Scorecard - Fulfillment FY25-Q2 - Purchase a Premium subscription for GitLab.com Recommendations
- UX Scorecard Part 1: gitlab-org/gitlab-design#2554 (closed)
Recommendations
# | Insight/Finding | Recommendation Issue | Comments |
---|---|---|---|
1 | Errors on checkout screen with state and company name. | There is an issue when a user types in an apostrophe in their company name an error shows up. State drop-down appears empty if country isn't selected first. | |
2 | Error message on checkout screen does not match real work language. | Got an error message after entering in a state and city + zip that didn’t match. The error message was not helpful and language should be changed. | |
3 | Empty state list on checkout screen. | If you do not select a country first the app appears broken on the checkout screen. Need to disable the "state" dropdown until a country is selected so it doesn't look like an empty list of states. | |
4 | Jump down button on FAQ section didn't work. | Upon clicking the button it jumps you upward to the add on section instead of jumping you down like it should. | |
5 | When signing up for a new account, had to click next on verification screen after verifying email address. | Would be nice if it gave me a confirmation screen that it has been verified and then automatically navigated me to the next screen after I verified so I didn’t have to click the next button. | |
6 | On the "Welcome to gitlab..." sign up screen where it asked for your role information the text under label "Create new project" should be updated. | The text doesn't not look like it belongs to the label. It should be smaller or indented to show the user the text below belongs to the label. |
Experience Recommendations Checklist
Learn more about UX Scorecards
-
Add this issue to the stage group epic for the corresponding quarter's UX scorecards. -
Brainstorm opportunities to fix or improve areas of the experience. - Use the findings from the Emotional Grading scale to determine areas of immediate focus. For example, if parts of the experience received a “Negative” Emotional Grade, consider addressing those first.
-
Create an issue for each recommendation using one of the Actionable Insight templates in the GitLab project, depending on if it relates to a product change or needs more exploration. Alternatively, you can create a separate epic to hold all your recommendations. Add a UX scorecard-rec
label to every issue or epic for traceability. To help with prioritization, add a severity label to communicate appropriate urgency and impact to the experience. Link to the epic or issues here.- Recommendations do not need to be documented in your Dovetail project.
-
Think iteratively, and create dependencies where appropriate, remembering that sometimes the order of what we release is just as important as what we release. - If you need to break recommendations into phases or over multiple milestones, create multiple epics and use the Category Maturity Definitions in the title of each epic: Minimal, Viable, Complete, or Lovable.
Edited by Lina Fowler