FY22-Q3 KR: Improve the quality of design MR reviews => 27/27, 100%

🔗 Objective in Ally

Objective: Increase our SUS score to 72.5 or higher through UX design improvements

This KR is part of our Actionable Steps for FY22 and is in alignment with the MDI themes and feedback from user research to help improve our SUS score.

The goal is to create guidelines for designers to use when conducting MR reviews so we're consistent and efficient in how we address them.

We'll also look into ways to increase the number of MR reviews across the sub-department, including having designers help with MR reviews in our most used areas of the product. This is in alignment with Product Designers https://about.gitlab.com/handbook/engineering/ux/ux-designer/#priorities and an upcoming UX KPI.

Criteria

• Retro on the current state of MR design reviews with product designers (Due 2021-09-13)
• Collect 5 good examples of MR design reviews (Due 2021-09-17)
• Update handbook with comprehensive MR design review guide (Due 2021-10-01)
  • Move Product Designer MR review guide to new page: !90409 (merged)
  • Understand MR
    • Which kind of changes are required to review and in what capacity: !90410 (merged)
    • Stretch: Encourage complete MR descriptions and assigning designers (see gitlab-org/gitlab!68892 (diffs)): !91000 (merged)
  • Preview MR
    • When to use which tool (pros/cons; see review apps current blockers): !90597 (merged)
    • What to do in case of problems (see https://about.gitlab.com/handbook/engineering/ux/how-we-work/#using-gitlab-development-kit-gdk-and-gitpod): !91171 (merged)
    • How to use which tool (switching branches, feature flags, login credentials, etc.): !91171 (merged)
    • Stretch: How to quickly set up and populate a test environment
  • Review MR
    • Provide clear acceptance criteria checklist with required and nice-to-have aspects (focused on the GitLab project; see gitlab-org/gitlab-design#244 (closed), gitlab-org&5487 (comment 517384369), https://docs.gitlab.com/ee/development/code_review.html#acceptance-checklist): gitlab-org/gitlab!70930 (merged), !91000 (merged), gitlab-org/gitlab!71636 (merged)
    • How to give feedback (multiple threads, praise, conventionalcomments.org): !91000 (merged), !91446 (merged)
  • Handoff MR (assignee, reviewer, approval flow): !91000 (merged)
  • Stretch: Balancing MR reviews (how to balance them with other responsibilities): !91000 (merged)
  • Cleanup scattered references to point to SSOT: !89661 (merged), !89660 (merged), !91090 (merged)
• Have 1 designer per stage complete an MR review using the guidelines (Due 2021-10-15)
  • Retrospective/feedback issue
  • Monitor: @ameliabauerly
  • Secure & Protect: @andyvolpe
  • Verify:Pipeline Authoring: @nadia_sotnikova
  • Package: @katiemacoy
  • Release: @dfosco
  • Growth: @emilybauman
  • Fulfillment: @esybrant
  • Enablement: @sunjungp
  • Plan: @uhlexsis
  • Manage: @dmoraBerlin
  • Ecosystem: @jareko
• Baseline and analyze design MR review data (Due 2021-09-30) @vkarnes
• Drive target from x to y according to baseline @vkarnes