Skip to content

Revise navigation proposal process to support experimentation

Jeff Tucker requested to merge jtucker_gl-main-patch-58de into main

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

I've spoken with several GitLab team members about the process for changing the navigation. We ask for quite a bit of user research currently, which makes sense when making changes that impact the entire user base. Some teams (like the Incubation team) are so early in their journey that this research isn't viable though. I'm exploring ways to support teams doing experimental feature development with a lighter-weight nav proposal process.

  • Add more background on why this process matters by detailing the user feedback we receive about the navigation
  • Break down "how to propose a navigation change" into three sections based on scope of access for the feature:
    • Feature flag only
    • Disabled by default
    • Enabled by default

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
Edited by Jeff Tucker

Merge request reports