Follow-up from "Review of Navigation & Settings Direction page as part of DPM onboarding"
The following discussions from !105121 (merged) should be addressed:
-
@ogolowinski started a discussion: I like the logical separation of the two main focuses, however, I think once we complete an effort on the future navigational issues, they will become existing navigation improvements. Is there any other way to name these?
-
@ogolowinski started a discussion: Great overview!
-
@ogolowinski started a discussion: Can you add an intro to this page?
- Done in: !108974 (diffs)
-
@ogolowinski started a discussion: What does this mean?
- Staying up to date on their important projects
-
I've updated to include this under "Pick up where you left off" which is one of the themes we had for SUS - LINK TBD
-
Pick up where you left off (Confidence: Medium)
- Switching contexts
- Watching pipelines
- Things in draft
-
@ogolowinski started a discussion: I think there should also be an addition around visibility of settings and permissions
- Agreed - I added a line for visibility of settings and permissions in this commit: !108974 (ecb46d8f)
-
@ogolowinski started a discussion: We are focused on gathering information to understand the current state. This will allow us to make informed decisions on the best iterative steps we can take to improve navigational tasks, once the team is more fully formed.
- Removed this paragraph!
-
@ogolowinski started a discussion: Please capture the highlights on the page instead of sending the readers to go watch youtube
-
Done - added a new biweekly update that gives more granular progress and linked it. !108974 (34bbaf51)
-
@ogolowinski started a discussion: Is this epic active? It doe not hav a due date nor are the linked issues assigned to a milestone
-
- UXR: Learn how different personas use GitLab navigation:. This is a multi-quarter deep dive: https://gitlab.com/groups/gitlab-org/-/epics/7661
-
This has since been removed and the focus has shifted. The UXR team owns that epic, in the future I'll make sure that the issues are more closely aligned
-
@ogolowinski started a discussion: (+1 comment) This is awesome and really important! Great focus point!
Be great at delivering new concepts: Spike on delivering behind a feature flag or A/B test: https://gitlab.com/gitlab-org/gitlab/-/issues/361002
-
Thanks! I had to pull this off until we get our north star and engineering has more time. We had a lot of churn with our roadmap as we fit the full North Star Vision work into it. With the current work, I see us scheduling this near the beginning of Q4.
-
@ogolowinski started a discussion: (+1 comment) Excited to see this! Do you happen to know which feature flag tool we are using? (Are we dogfooding our own?)
- For this one, I believe we would be using the normal chatops feature flags,
our own feature flagsor use an opt-in setting in the user profile. In the last 30 days, I don't see us using A/B tests for the big navigation rollout.
-
@ogolowinski started a discussion: An example of how ~"group::authentication and authorization" overcame this: https://about.gitlab.com/direction/manage/auth/#maturity-plan
-
@ogolowinski started a discussion: What is the most requested issue that was raised?
-
I've added this section to the direction page with top issues
-
Most of the feedback comes in a lot through SUS feedback versus issues. We've also seen project/group switching, which we are addressing with the North Star vision and the Menu Menu changes.
Themes from SUS are the best mechanism right now to find this. We plan to do this exercise quarterly and keep updating this direction and the roadmap based on the trends we see.
-
@ogolowinski started a discussion: What is the most requested internal/dogfooding issue that was raised? I imagine that we will dogfood any navigational change before releasing it to the public with a feature flag/A/B test
-
Mostly requests to overpower the left navigation, but there isn't a specific issue