Group page overview: Vision design feedback
Right now, the Overview landing page of a GitLab group is not very intuitive. It does not provide much context about what you are looking at, is very similar to the project overview (due to the re-used header UI) and has a potential to improve information architecture and structure. Right now, it typically only lists the subgroup hierarchies and child projects. (source: https://gitlab.com/gitlab-org/gitlab-ce/issues/50836)
Aim of the Research
- Get user feedback on the Group Page overview 'vision' mockup.
- Understand how users currently interact with group overview page.
- Determine if anything from the mockup makes the overview more useful.
Methodology
User interviews with 5 GitLab users.
Who we spoke with
You can access video recordings by clicking on the user number.
User 1 | User 2 | User 3 | User 4 | User 5 | |
---|---|---|---|---|---|
Job Title | Software Engineer | Development Team Lead | Software Engineer | Director, Software Engineering | DevOps Engineer |
Organization Size | 11-100 people | 11-100 people | 1,001-10,000 people | 1,001-10,000 people | 101-500 people |
GitLab Features being used | CI/CD, Merge Requests, GitLab Pages, Groups, Issues, Issue Tracker, Milestones, Projects, Snippets | CI/CD, Merge Requests, Groups, Projects | CI/CD, GitLab Pages, Issues, Projects, Snippets, Wiki | CI/CD, Merge Requests, Groups, Issues, Issue Tracker, Issue Boards, Milestones, Projects, Snippets, Todos, Wiki | CI/CD, Merge Requests, GitLab Pages, Issues, Issue Tracker, Issue Boards, Milestones, Snippets, Todos, Wiki |
GitLab package | GitLab.com, Core | GitLab.com | GitLab.com | GitLab.com, Core, Starter | Premium |
Primary use of GitLab | Work use | Work use | Personal use (used it for work in the past) | Work use | Work use |
Experience with GitLab | Started using GitLab about 4-5 years ago | Using GitLab for about 2 years | Started using GitLab about 1.5-2 years ago | Started using GitLab 5-6 years ago | Has been using GitLab for about 3 years |
Results
- Full Research Report: https://docs.google.com/document/d/14Bl0Km1DFWwyItUbEHxXpRFddLyW-0xjuQp6mJcraBQ/edit?usp=sharing
Next Steps
- Consider research results for next discovery: https://gitlab.com/gitlab-org/gitlab-ce/issues/54663 (11.8 tentatively)
- Implement second iteration: https://gitlab.com/gitlab-org/gitlab-ce/issues/54665 (12.0 tentatively)
Progress
-
Write screener survey [Deadline: Fri Nov 9th] -
Send out screener survey to segment of research panel [Deadline: Thurs Nov 8th] -
Write interview script [Deadline: Fri Nov 9th] -
Get feedback on interview script [Deadline: Fri Nov 9th]
-
-
Schedule 5 users [Deadline: Mon Nov 12th] -
Conduct interviews [Deadline: Thurs Nov 15th] -
Pay users [Deadline: Fri Nov 16th] -
Edit videos [Deadline: Fri Nov 23rd] -
Schedule "wash-up" meeting to discuss results with PM + designers [Deadline: Mon Nov 26th] -
Communicate results in issue -
Determine next steps
-
-
Write up findings into a blog post [Deadline: Weds Nov 28th] -
Add link to research report to issue description [Deadline: Weds Nov 28th]
Deliverable added so that issue will appear in UX team board.
Edited by Matej Latin