UX Scorecard Recommendations for Verify::Runner - Runner Concept Discovery / Understanding
UX Scorecard Checklist
Expand/collapse checklist
-
After completing the Experience Baseline for a JTBD, create a “{{YYYY}}{{Quarter}} Recommendations for…” issue for each JTBD and include them in the Part 2: Experience Recommendations sub-epic. -
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 and link them to the corresponding JTBD recommendations issue. -
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.
Part 1: Original UX Scorecard and JTBD
UX Scorecard: UX Scorecard for Runner: Runner Concept Discovery / Understanding
JTBD: I need to quickly understand the role of unner in their projects CI/CD, how it works, how to configure it and its underlying features. I should be able to setup builds and other Runner specific setups with ease.
Related JTBD: I need to migrate from existing systems like Jenkins / I need to setup a dedicated runner for my project / I need to inspect an existing job and understand the role runner.
Part 2: Experience Recommendations
Pain Points
- Fragmented Path or User Flow
- Lack of Context / Lack of a Feature Narrative
- Disjointed Experience
- Unclear Concepts and Sub-Concepts
Fragmented Path or User Flow
In the existing GitLab experience, there's no entry point that takes the user to the areas where they can manage, configure and oversee their Specific and Shared Runners configurations. If users look for any Runner related setting menu or view, is unlikely they will find it without actually having to Google it first.
Recommendations:
- 33744 - Create a user path from common Web UI areas where the Runner configuration may be required. For example from the Project buttons. This path doesn't need to be specific to Runner. It could be a generic shortcut to the CI/CD settings.
Lack of Context / Lack of a Feature Narrative
In the existing GitLab experience, it's not clear what's the goal of the Runners in the context of the CI/CD settings. Users who find this setting have to dig deeper and likely Google the GitLab docs to get the full context of the features and role of the Runner. In comparison, other available settings in the CI/CD settings, like Variables, provide more literature and informational artifacts to contextualize the users about that feature.
Recommendations:
- 33745 - Improve Runner settings helper texts to increase the context of the feature.
- 33745 - Provide a link to the documentation in the context of the helper text / literature.
Additional (Not-Related) Recommendations:
- Update "linking to documentation" pattern in the CI/CD settings page.
Disjointed Experience
In the existing GitLab experience, the Runner concept seems to be sparsely mentioned in certain areas of the web console, but there's no clarity on what type of functionality is supported via the Web UI and what functionality can be accessed exclusively through the CLI. This creates a disjointed experience since the user has no defined expectations on what's the best way to achieve something (e.g: deleting a Runner)
Recommendations:
- 33745 - Improve Runner settings helper texts to increase the context of the feature.
- 33745 - Provide a link to the documentation in the context of the helper text / literature.
- No issue yet. Needs more exploration - Add "copy value" functionality to URLs and other information provided in the Web UI and needed for the CLI.
Unclear Concepts and Sub-Concepts
In the existing GitLab experience, certain Runner specific concepts like tags, IDs and Runner addresses are not explained or properly labeled. Users have to figure out the meaning of this information and its usage/role in the context of setting or managing a Runner.
Recommendations:
- 33803 - Change the layout of the Runner settings to improve readability and comprehension.
- 33804 - Add labels to unlabeled concepts and/or helper text to expand on Runner sub-concepts.