The UX Scorecard is a way for us to identify and score the usability of an experience in our product based on a set of heuristics. We use UX Scorecards to gain an understanding of how a user interacts with our product and to quickly spot opportunities for improvement.
UX Scorecards should be done on every important workflow and should be repeated from time to time so that we can continuously monitor our progress in making experiences better for our users.
As UX practitioners, we must think strategically about fixing usability challenges within the GitLab product in order to give our users a quality experience. Creating a UX Scorecard with associated recommendations enables us to identify, scope, and track the effort of addressing usability concerns within a specific workflow. When it's complete, we have the information required to collaborate with Product Managers on grouping fixes into meaningful iterations and prioritizing UX-related issues.
The UX Scorecard process is meant to balance flexibility and consistency. There are several ways you can create your Scorecard, listed from lightest to heaviest. Select an appropriate approach based on the time you have, the priority of the workflow to users, or whether or not this is a first Scorecard or an update.
When doing a Scorecard, you have several options:
In every case,
This is a process intended to help inform the design process and maintain a high bar of quality.
Below is a recommended step by step process for completing a UX Scorecard. Note that every scorecard is not the same. Product Designers are welcome to adapt the steps to their needs as long as they are as objective as possible and the spirit and outcome remains the same.
Example: “UX Scorecard - Create:Source Code”
Create an experience scoring issue, using the template “WIP: UX Scorecard Part 1”, and add it to the stage group epic.
This issue should have the UX Scorecard label. If it's related to an OKR, also apply the OKR label for easier tracking.
If you'd like to view or edit the templates, you can find them here:
The onboarding experience of your product category can make a big difference in the adoption of GitLab stages. You can use a UX Scorecard to assess the UX of your onboarding experience and identify areas for improvement.
Onboarding can refer to many different scenarios, and this can impact the experience:
If you have a recent UX scorecard or a recent usability test with recordings, you can update these rather than starting over. For example, if you recently did a usability test on creating MRs, you can re-watch the sessions with the onboarding heuristics in mind to infer an initial score for the onboarding experience. However, it is highly recommended that at some point you intentionally evaluate the onboarding experience.