DRI for "not_owned" category

Problem

Currently we have some GitLab functionality that is shared across multiple stages:

  • Navigation used throughout the application, including the top bar and side bar.
  • Shared project views, like the project overview and settings page.
  • Functionality specific to the admin area and not tied to a feature belonging to a particular stage.

We need a long term solution that could help solving already existing issues and ones that will be coming up in the future:

Opportunity

Issues related to these areas do not have a DRI and should be owned on a case-by-case basis, depending on the problem to solve. We have an opportunity to influence overall GitLab’s user experience in order to keep user loyal to the product by:

  • Own a cohesive experience across all GitLabs navigation (avoid fixing small issues at a time without looking at a global picture)
  • Perform proactive user research to avoid missing out on major user experience challenges
  • Win from competition by working on simplicity and innovation of the shared functionality
  • Avoid product and UX debt we’re currently accumulating

Proposal

Find a DRI to look after, research and drive items that are currently falling under the “not_owned ” category. The best fit here seems to be UX department, as lots of these issues are needed lots of user experience guidance.

I have outlined some thoughts in this proposal document with the goal of proposing a DRI for these cases.

Let's use this issue for the discussion on the next possible steps.

Action for Product Design Managers

  1. Go to list
  2. Each of us will take 7 Issues and begin working on them as soon as we are able
  3. Click into an issue and immediately apply the 🍉 label
  4. Read the issue description and comments and try to reproduce the problem
  5. Ask clarifying questions in the issue if needed
  6. Determine what group** it likely applies to (reference Product Categories) --> You may have to make some judgement calls, closing issues that have had no activity for several years, or no longer seemed relevant.
  7. @ mention the PM, Product Design Manager, and Product Designer of the group to get it on their radar

** If the Issue seems to fall under any of the following Groups, don't change the Group label just ping the relevant parties to get the Issue on their radar:

Category Stage:Team
Navigation Growth:Expansion & Retention
Settings TDB
Projects Project Mgmt

Progress tracker

Manager Review 7 issues
Jacki
Justin
Marcel
Mike
Nadia
Taurie
Valerie
Edited by Valerie Karnes