[2019Q3] UX Scorecard - Setting up GitLab-CI (Revisited)
Revisit gitlab-design#480 (closed) to see if any positive changes have occurred
The grade was intended to be influenced by the following issues scheduled for Q3:
-
gitlab#30808 (closed)
12.312.4 - gitlab#30807 (closed) 12.4 (merged)
- https://gitlab.com/gitlab-org/gitlab-ce/issues/65843 12.4 (Merged)
-
gitlab#30809 (closed)
12.5backlog - gitlab#30810 (closed) 12.5
- gitlab#30811 (closed) 12.5
Next steps
The bigger themes were yet to be tackled for this JTBD thus leaving us with enough opportunities to dive into next:
- &2288 (closed) includes multiple issues scheduled for 12.7+ and a discovery issue intending to influence 12.8+. This follows multiple whiteboarding sessions on the following mural.ly document.
- gitlab#38132 (closed) has been planned to re-evaluate this after improvements have been implemented.
Emotional Grading Scale
Expand/collapse scale
-
🎉 Positive: The user’s experience included a pleasant surprise—something they were not expecting to see. The user enjoyed the experience on the screen and could complete the task, effortlessly moving forward without having to stop and reassess their workflow. Emotion(s): Happy, Motivated, Possibly Surprised -
😐 Neutral: The user’s expectations were met. Each action provided the basic expected response from the UI, so that the user could complete the task and move forward. Emotion(s): Indifferent -
😠 Negative: The user did not receive the results they were expecting. There may be bugs, roadblocks, or confusion about what to click on that prevents the user from completing the task. Maybe they even needed to find an alternative method to achieve their goal. Emotion(s): Angry, Frustrated, Confused, Annoyed
Grading Rubric
Expand/collapse rubric
A (High Quality/Exceeds): Workflow is smooth and painless. Clear path to reach goal. Creates “Wow” moments due to the process being so easy. User would not hesitate to go through the process again.
- Frustration: Minimal to none
- Task Completion: Successful
- Steps to Accomplish Task: Minimal
B (Meets Expectations) Workflow meets expectations but does not exceed user needs. User is able to reach the goal and complete the task. Less likely to abandon.
- Frustration: Low
- Task Completion: Successful
- Steps to Complete Task: Minimal
C (Average) Workflow needs improvement, but user can still finish completing the task. It usually takes longer to complete the task than it should. User may abandon the process or try again later.
- Frustration: Medium
- Task Completion: Successful but with unnecessary steps
- Steps to Complete Task: Average complexity
D (Presentable) Workflow has clear issues and should have not gone into production without more thought and testing. User may or may not be able to complete the task. High risk of abandonment.
- Frustration: High
- Task Completion: Unlikely, but there may be a chance that there is completion
- Steps to Complete Task: Excessive
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
Updated experience
Validation effort
This effort has been validated with research observing 9 participants:
Grade
Grade: C
Video walkthrough: https://youtu.be/bYEIiy0XY6w
Previous grade: C
- Frustration: Medium
- Task Completion: Successful but with unnecessary steps
- Steps to Complete Task: Average complexity
Experience walkthrough:
The experience the participants displayed quite closely followed the steps documented at gitlab-design#480 (closed)
Synthesis mural.ly document displays each individual participants road towards setting up GitLab CI in a comparable view.