UX Scorecard - Secure FY21-Q2 - managing licenses (accountability)
For those accountable for compliance:
JTBD: When my organization has license compliance rules to follow I want to be able to whitelist or blacklist licenses so that I can ensure any new code merged in a project is in compliance.
Rating: F (Poor) Workflow leaves user confused and with no direction of where to go next. Can sometimes cause the user to go around in circles or reach a dead end. Very high risk of abandonment, and user will most likely seek other methods to complete the task.
Managing licenses in project settings, proactive license compliance:
|i. User navigates to settings (Project > Settings > CI/CD > License Management)||Neutral: Given the user type, the person responsible for compliance, the location of this feature may be confusing to find|
ii. User expands the license management section, info display notes that no licenses have been added. CTA
||Negative: There is a specific configuration needed for the feature to be functional. The UI is displaying the ability to add/remove license rules; but in the case that the configuration was not completed adding/removing ability could deceive the user into thinking the feature would be functional.|
iii. User selects the
||Negative: There is a preset list - it is not clear what to do if the license the user wanted to add is not on the list.|
|iv. User could not find license they wanted to add in list. User types in the name to try to add to the list.||Negative: It may not be clear that the user can add a license type to the list. Scanning may not identify correct license (from user input).|
v. User may now see added licenses and toggle the classification to either
||Negative: The table would get challenging to manage once 10+ items are listed.|
Managing new licenses detected in a MR, reactive license compliance:
- 1. Document the current experience of the JTBD, as if you are the user. Capture the screens and jot down observations. Also, apply the following Emotional Grading Scale to document how a user likely feels at each step of the workflow. Add this documentation to the epic's description.
- 2. Use the Grading Rubric below to provide an overall measurement that becomes the Benchmark Score for the experience, and add it to the epic's description.
- 3. Once you’re clear about the user’s path, create a clickthrough video that walks through the experience and includes narration of the Emotional Grading Scale and Benchmark Score.
- 4. Post your video to the GitLab Unfiltered YouTube channel, and link to it from the epic's description.
- 5. If your JTBD spans more than one stage group, that’s great! Review your JTBD with a designer from that stage group for accuracy.
- 6. Create an issue to revisit the same JTBD the following quarter to see if we have made improvements. We will use the grades to monitor progress toward improving the overall quality of our user experience.