UX Scorecard: Package FY22-Q3 - Investigate metadata and historical information on a dev dependency

Evaluation

JTBD

When I am investigating a dev dependency, I need easy access to metadata and historical information related to the specific dependency, so that I can deliver a consistent and stable experience to customers.

Scenario

You are collaborating on an existing project in GitLab that has package dependencies. To troubleshoot issues related to a specific package, you need to see the historical information about the package, such as who published it and how it was published. You also need to see information about the package such as version and any error messages related to the package.

Tasks to complete scenario

  1. trigger pipeline, pipeline fails
  2. investigate build job failure, see it has something to do with package
  3. navigate to packages & registries > packages
  4. find package that I think caused the failure from the list, click on that package
  5. investigate history, version, branch etc. to see if I can determine the problem

UX Scorecard Checklist

Learn more about UX Scorecards

  1. Add this issue to the stage group epic for the corresponding UX scorecards. Verify that the "UX scorecard" label is applied.
  2. After working with your PM to identify a top job, write it using the Job to Be Done (JTBD) format: When [situation], I want to [motivation], so I can [expected outcome]. Review with your manager to ensure your JTBD is written at the appropriate level. Remember, a JTBD is not a user story, it should not directly reference a solution and should be tool agnostic.
  3. Make note of which personas might be performing the job, and link to them from this issue's description. Keeping personas in mind allows us to make the best decisions to address specific problems and pain points. Note: Do not include a persona in your JTBD format, as multiple types of users may complete the same job.
  4. If your JTBD spans more than one stage group, that’s great! Review your JTBD with a designer from that stage group for accuracy.
  5. Consider whether you need to include additional scenarios related to onboarding.
  6. Review the current experience, noting where you expect a user's high and low points to be based on our UX Heuristics. Using an experience map, such as the one found in this template, capture the screens and jot down observations.
    • If you're re-scoring the experience, review the entire flow, but feel free to reuse existing artifacts (i.e. a UI screen that wasn't changed).
  7. Use the Grading Rubric to provide an overall measurement that becomes the Benchmark score for the experience (one grade per JTBD), and add it to this issue's description. Document the score in the UX Scorecard Spreadsheet.
  8. Once testing is complete, create a walkthrough video that documents what you experienced when completing the job in GitLab. Begin the video with a contextual introduction including:
    1. Your role, stage group
    2. Specify how you conducted the heuristic evaluation
    3. Add a short introduction describing the JTBD and the purpose of the UX scorecard (i.e. you're performing the evaluation in partnership with {stage group} and {product designer}.
    4. This is not a "how-to" video, but instead should help build empathy for users by clearly showing areas of potential frustration and confusion. (You can point out where the experience is positive, too.)
    5. At the end of the video, make sure to include narration of the Benchmark Score. Examples here and here.
    • The walkthrough video shouldn't take you long to create. Don't worry about it being polished or perfect, it's more important to be informative.
  9. Post your video to the GitLab Unfiltered YouTube channel, and link to it from this issue's description.
  10. Link to your video in the Engineering Week in Review.
  11. Create a recommendation issue for this JTBD and add it to the same stage group epic as this issue. Also add a link to your recommendation issue to this issue.
Edited by Rayana Verissimo