Skip to content

UX Scorecard (Part 1): Review apps

  • 🕺 Personas: Sasha (Software Developer)
  • 💪 JTBD: When reviewing a user interface change before a software is released, I want to reduce unexpected negative impacts to the end user, so we can retain usability while releasing changes.
  • Previous score and scorecard: N/A
  • 🗺 Experience map: Mural
  • ✨ Benchmark score: B
  • 🎥 Walkthrough video: GitLab Unfiltered Video
  • 💻 Walkthrough deck: Figma
  • 🧩 Recommendations: #1631 (moved)

Onboarding information

🛠 Evaluation setup

💪 JTBD

When reviewing a user interface change before a software is released, I want to reduce unexpected negative impacts to the end user, so we can retain usability while releasing changes.

🎬 Scenario

You are a frontend developer who is responsible for developing and testing new features, and successfully pushing them to production. To enable yourself and teammates to easily review new UI features, you need an environment to see and review the new changes, before it goes to production. This should help reduce any bugs and undesired or unexpected behavior before users interact with it.

Primary project: https://gitlab.com/gdoyle/ux-scorecard-review-apps

Tasks to complete the scenario:

  • Set up a review app for your project by configuring an environment to deploy changes to
  • Create an MR with a simple UI update on the home page that triggers the review app
  • Review the update and make any changes necessary to obtain the expected features
  • Merge the MR

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. Select the appropriate scorecard approach and evaluate the current experience.
  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/witnessed within the existing experience. Begin the video with a contextual introduction including: your role, stage group, specify how you acquired the data (ex: internal or external users, or self-heuristic evaluation), and a short introduction to your JTBD and purpose of the UX scorecard. 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.) At the end of the video, make sure to include narration of the Benchmark Score. Examples here and here.
    • If you're re-scoring the experience, walkthrough the entire flow again. For narration, you can highlight the recent improvements but still call out any areas that could still use some tweaking (in the next round of iterations, if applicable). The re-score video, in theory, should be shorter since we've hopefully eliminated a few bumps in the user flow.
    • 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.
  12. Don't forget Update the categories.yml file for the category so the Category Health page fills in up - gitlab-com/www-gitlab-com!98926 (merged)
Edited by Gina Doyle