[Part 2] UX scorecard Product Analytics - Recommendation

• UX Scorecard Part 1: #2236 (closed)
• Resulting Recommendations: 👇

Recommendations

Setting up a dashboard / Getting started with Product Analytics

Overall workflow

• Add the ability to export the data / share
  • Allow Product Analytics data to be exported to ... (&9340 - closed)
  • Allow users to download/share/embed a chart pan... (&8940)

The need can be defined through problem validation / JTBD research.

Minimal set-up and Guidance

• Optimize the number of set-up steps. What can be simplified so we minimize back and forth. gitlab#388629 (closed)
• Clearly call out the number of steps needed to set up Product Analytics. Explore using a stepper. (eg. Security Policy set-up)

Visibility of system status

• Ensure breadcrumbs reflect users' current location gitlab#396327 (closed)
• Explore a different pattern for the edit mode. De-correlate content and appearance editing. Align with the current platform patterns. gitlab#389274 (closed)
• Ensure every state has a clear call to action
• Remove data filters when in edit mode

User control & Freedom

• Ensure the user's panel arrangement preferences are stored.
  • Is dashboard saved check (gitlab#387641)
  • Save Visualization to file (gitlab#385700 - closed) maybe?

UI polish

• Update By GitLab labels. Align with dashboard name and update styles to neutral (eg. Owner, Maintainer labels...). Add tabs to separate GitLab's dashboard listing and user generated dashboards gitlab#404610
• Change back button placement
• Move the label above the input field for the Dashboard title field (remove from the placeholder)

Creating a visualization with the "Visualization designer"

Overall workflow

• All the Visualization Designer issues are in this epic - Product Analytics Visualization Designer and Da... (&9386)
• Where should the Visualization designer live? In or out of a given dashboard? Why?
• Should we retain the name Visualization designer?

The above can be answered through problem validation / JTBD research.

Visibility of system status

• Ensure the Add to dashboard button performs the action of adding visualization to a dashboard. Highlight the main action using primary styling.
  • Save Visualization to file (gitlab#385700 - closed)
  • Add saved visualizations as panels to dashboard (gitlab#385705 - closed)
• Update 3 columns layout to 2. Keep actions on one side, and output on the other.

Flexibility and efficiency of use

• Limit progressive disclosure and fix nested interactions when picking dimensions and metrics. Swap list items for dropdown / comboboxes. Remove the Add another dimension button. gitlab#404586
• Swap metrics and dimensions badges and labels for tokens. gitlab#404586
• Introduce a back button, just like the dashboard view?

UI polish

• Move the label above the input field for the Dashboard title field (remove from the placeholder)
• Ensure the Dashboard title field is vertically aligned with the main CTA

User control and freedom

Later on

• Allow users to create/duplicate from an existing chart template

Experience Recommendations Checklist

Learn more about UX Scorecards

1. Add this issue to the stage group epic for the corresponding quarter's UX scorecards.
2. 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.
3. 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-rec label 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.
4. 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.