Effectiveness of GitLab Service Status Dashboard
What’s this issue all about?
Today with GitLab, there is no place to go check on the status of the instance. For example if I am seeing slow or strange behavior, is it me? Is it the server? Is it my connection?
We have come up with a possible dashboard design to help answer these questions, as described on https://gitlab.com/gitlab-org/gitlab-ce/issues/50061.
What questions are you trying to answer with this research?
- How is this design performing with users?
- Are these the correct metrics to show?
- Is the presentation clear and understandable? (If not, what details should be added to make it more clear?)
- Do users understand what these metrics represent, and why they should care?
- Is there something else they want to see here?
As a secondary focus, it would be good to follow up on the question of where this dashboard should be located, as discussed in #120 (comment 130352580). Doing this would help follow-up on the initial research that was done on this topic. An additional issue can be added, in future, to look into this piece further if needed.
What assumptions do you have?
We should make sure we sample primarily users of the platform, and not administrators. As we want to ideally make this available to all users of GitLab. Administrators would have another workflow, usually Grafana, to get a more detailed look under the hood.
What decisions will you make based on the research findings?
We will decide how to refine the design concept to better suit users' needs, and finalize where to put the instance health information.
What's the latest milestone that the research will still be useful to you?
@evhoffmann
Researcher checklist --
Schedule users. (Deadline: Feb 8) -
Write script. (Deadline: Feb 11) -
Test the script. Conduct 1 usability testing session. Edit the script if required. (Deadline: Feb 15) -
Conduct remaining usability testing sessions. (Deadline: Feb 22) -
Pay users. (Deadline: Feb 22) -
Analyze videos. (Deadline: Feb 25) -
Edit videos and add them to the Research proposal issue. (Deadline: Feb 25) -
Schedule a wash-up meeting. (Deadline: Feb 25) -
Add the study's key findings to the wash-up meeting calendar invitation. (Deadline: Feb 25) -
Record and facilitate the wash-up meeting. (Deadline: Feb 26) -
Document the study's findings within a blog post. (Deadline: Mar 1) -
Update the Research proposal issue. Link to the blog post. Unmark as confidential if applicable. Change status to done and close issue. (Deadline: Mar 1)
Researcher prep doc