CMS Recommendations : Manage | Groups & subgroups
- CM Scorecard: https://gitlab.com/gitlab-org/gitlab-design/-/issues/1331
- Resulting Recommendations: {{when ready, add a link to your recommendations epic}}
Experience Recommendations Checklist
Learn more about CM Scorecards
-
Brainstorm opportunities to fix or improve areas of the experience with your PM and any relevant counterparts. -
Create an issue for each recommendation. Create an epic to hold all your recommendations. Add a cm-scorecard-rec
label to every issue or epic for traceability. -
Add the link to the recommendations epic to this issue. -
Product Manager: Prioritise the recommendations, involving the Product Designer and Engineering team as needed.
Recommendations
This epics follows the CMS recommendations issue.
1. Address confusion around Projects / Groups
Test participants were immediately unable to differentiate between a project and a group. The idea of group being an organizational element, and project being a code repo was not understood by many participants.
-
Merge groups and projects -
Break apart New Group / Project
button -
Add a tree visual to Projects
(low value)
2. Improve sharing capabilities
Test participants were not easily able to share groups/projects across their organization. There was confusion as to what was being shared and how to enable sharing. As well as no confirmation of sharing once objects were connected. Visual queues were lacking and did not explain what was done.
-
Needs further investigation for specifics and problem definition and solution proposals
3. Improve navigation
Test participants did not easily understand where to begin. The navigational logic is not easily interpreted. "Home" or "Start" is missing in the GitLab environment.
There is actually a lot of work already happening in other groups to try to improve this.
-
gitlab#225465 (closed) -
&4413 -
&3389 -
gitlab#260298 (closed) -
gitlab#255325 (closed) -
gitlab#216608 (closed)
4. Reduce complexity of getting started
Test participants did not know how to build an organization. There was no visual hints or user flow that lead them to a organizational overview, or understanding of where their organization would exist as an object map, for example:
- Creating an org building projects/groups was completely lost in testing for new users.
- Terminology was complicated and users did not understand
group
/project
difference - In App help / documentation hard to find.
Proposals
-
Onboarding wizard (low value) devopsgrowth has some work being done here. -
In App help tool