Skip to content

UX Scorecard - Foundations - FY25-Q2 - Notifications

Summary

Grade: Notifications
Badge level C Average Average
Grade: To-dos
Badge level D Poor Poor
  • Personas: All personas theoretically use notifications but our initial research is focused on Delaney (Team Development Lead) and Parker (Product Manager).
  • JTBD: "I want to be notified when key events occur so I can take any actions necessary to keep my project moving forward."
  • Scenario: You are a team lead who is trying to stay up-to-date on discussions and changes in an important project. Use GitLab's todos and notifications to assess what's happening in the project, and if there's anything important you need to act on to keep the project moving forward.
  • Tasks:
    • Review your notifications and todos.
    • Decide which notifications and todos require follow-up.
    • Follow up as needed.
    • Adjust notification and todo settings to increase or decrease the number of updates you receive.
  • Figma canvas: Link
  • Previous score and scorecard: N/A
  • Benchmark score: Notifications: C // To-dos: D
  • Walkthrough video: Unfiltered Link
  • Recommendations: Rather than a specific recommendation issue, we're reconsidering the whole workflow as part of Design discovery: notifications (gitlab#456349 - closed).

UX Scorecard Checklist

Learn more about UX Scorecards

  1. Work with your PM to identify a top Job to be Done (JTBD). All GitLab JTBD can be found in the jobs-to-be-done.yml file. If creating a new job, write it using the JTBD format: When [situation], I want to [job], 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.
  2. 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.
  3. Select the appropriate scorecard approach and evaluate the current experience.
  4. 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.
  5. 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.
    • 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.
  6. Tag PM and UX DRIs for this JTBD in this issue to share findings.
  7. Post your video to the GitLab Unfiltered YouTube channel, and link to it from this issue's description.
  8. 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. (Opting to re-examine the whole workflow as part of Design discovery: notifications (gitlab#456349 - closed).
Edited by Amelia Bauerly