Skip to content

Clarify UX review structure for teams without designer

Marcel van Remmerden requested to merge ux-review-team-specific into master

What does this MR do and why?

We have seen an increase in the number of MR UX Review requests over the last couple of months with the trend continuing into May. To align with our current capacity, we are updating the documentation in the handbook to reflect a modification in how we handle UX Reviews for the foreseeable future. We will no longer be conducting MR reviews for stage groups without a design DRI, unless it is from a community contributor.

The reasons why these are the MR reviews we are no longer supporting:

  • We have aligned designers to support areas of the product that have been given the highest prioritization.
  • MRs from teams without design support tend to require significantly more time for a variety of reasons such as, missing designs to compare, missing context, unfamiliarity with long-term goals and aligning short-term iterations, and so on.
  • This change allows for the volume of MR reviews designers are assigned to ease opening up their capacity for their stage group work.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports