Experience Recommendations - Plan FY24-Q4 - Optimize CICD Analytics
- UX Scorecard Part 1: #2437 (closed)
| Thoughts | Pain Point | Opportunity/Recommendation | Insight Issue | |
|---|---|---|---|---|
| 1 | Sparse, some inconsistency of term usage, missing any failure or error info. | There’s not a lot of help being given on what I can or should do with this data. No additional info about failed pipelines beyond the link to the failed pipelines page. |
Show me the problems, recommend how I can fix them and get better. As an efficiency optimizer, I want to know why pipelines failed, what point did they fail, how long did they run before they failed. Right now, the only way I can see any facet of this is to click through and go to the pipeline list detail page. Would be nice to get some charts here. Maybe each of the failed pipelines consistently fail at the same time?
|
|
| 2 | Not a lot of help interpreting the data, helping me get better, or knowing what it should look like. | There’s not a lot of help being given on what I can or should do with this data. |
Show me the problems, recommend how I can fix them and get better. Fix inconsistencies across charts. Could be useful to compare this data across different tiers (e.g., development, staging, production). Comparing Deployment against other stages might help me see bottlenecks before production deployment.
|
|
| 3 | Not a lot of help interpreting the data, helping me get better, or knowing what it should look like. Some inconsistencies with previous chart info. | There’s not a lot of help being given on what I can or should do with this data. |
Show me the problems, recommend how I can fix them and get better. Fix inconsistencies. It could be nice to be able to compare data across tiers to see if there's anything happening that's different. Difficult to interpret. How many "days" is 0.2 days?
|
|
| 4 | Not a lot of help interpreting the data, helping me get better, or knowing what it should look like. Some inconsistencies with previous chart info. | There’s not a lot of help being given on what I can or should do with this data. |
Show me the problems, recommend how I can fix them and get better. Fix inconsistencies. Fix inconsistencies to align with Lead time hover/tooltip. Difficult to interpret. How many "days" is 0.2 days?
|
|
| 5 | Not a lot of help interpreting the data, helping me get better, or knowing what it should look like. Some inconsistencies with previous chart info. |
There’s not a lot of help being given on what I can or should do with this data. Confused as to what the Change Failure Rate stat of 8.5% is in related to in the chart. |
Show me the problems, recommend how I can fix them and get better. Fix inconsistencies. It would be great if we could help our users understand why these spikes are happening. Everything is pretty consistent, but then you get these blips. What's causing them? Help the user fix them! Fix inconsistencies to align with Lead time hover/tooltip.
|
Experience Recommendations Checklist
Learn more about UX Scorecards
-
Add this issue to the stage group epic for the corresponding quarter's UX scorecards. -
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 using one of the Actionable Insight templates in the GitLab project, depending on if it relates to a product change or needs more exploration. Alternatively, you can create a separate epic to hold all your recommendations. Add a UX scorecard-reclabel to every issue or epic for traceability. To help with prioritization, add a severity label to communicate appropriate urgency and impact to the experience. Link to the epic or issues here.- Recommendations do not need to be documented in your Dovetail project.
-
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.