Secure UX Scorecard: dependency list, out-of-date
JTBD
When dependencies are out-of-date, I want to be made aware so I can update them to reduce potential security vulnerabilities and avoid the potentially high cost of larger updates.
Checklist
-
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 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.
Conclusion
Grade: F (see note)
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.
Frustration: Very High
Task Completion: Very Unlikely
Steps to Complete Task: Lacking
Note: It struck me when doing this scorecard that the task wasn't exactly fair- there currently is no way to view whether or not your dependencies are up-to-date within GitLab, so of course the result was going to be a failure. I am going to work with @tlavi to find out from users whether this is a feature they'd like to see. Then we can move forward with some designs.
Ideally we'd like to start small, and simply add a column that shows the latest version of any given dependency. We can highlight this in some way using iconography, color, tabs, filters, etc. The next step would be to give users a way to actually update through the UI, using auto-generated merge requests.