Geo Administrator Interface User Observations
Project Links
- Recruiting Request
- Recruiting Worksheet
- Project Folder
- Interview Script
- Interview Recordings
- Synthesis Board
Project Checklist
-
Submit research request (Jan. 24) -
Submit recruiting request #683 (closed) (Feb. 6) -
Create V1 interview script draft (Feb. 10) -
Finalize interview script based on feedback/input from stakeholders (Feb. 13) -
Recruit & schedule sessions with 5 target customers (Feb. 28) -
Participant 1 (Feb. 13) -
Participant 2 (Feb. 25) -
Participant 3 (Mar. 5) -
Participant 4 (Mar. 10)
-
-
Conduct research sessions and takes notes along with design, PM, and others as applicable (Feb. 13-Mar. 10) -
Participant 1 (Feb. 13) -
Participant 2 (Feb. 25) -
Participant 3 (Mar. 5) -
Participant 4 (Mar. 10)
-
-
Upload video recordings to shared UX Research drive (March 10) -
Participant 1 (Feb. 13) -
Participant 2 (Feb. 25) -
Participant 3 (Mar. 5) -
Participant 4 (Mar. 10)
-
-
Synthesize the data and identify trends, resulting in findings -
Create an epic in the UXR_Insights repo to collect videos and high level notes about the project. Each subsequent finding is created as an issue and linked to the parent epic. -
Share insights with all applicable stakeholders and discuss next steps
Original Request
What’s this issue all about?
GitLab Geoallows distributed teams across the world to use GitLab at speed. Geo provides read-only Geo nodes close to users that they can pull data from. Geo nodes can also be used to failover in a Disaster Recovery scenario.
Some parts of Geo can be configured, monitored and changes using an administrator interface; however, not all tasks are available throughout the UI.
I believe the main activities that the UI can/should be used for:
- Configuring Geo
- Activating replication of data sources
- Monitoring of replication
- Troubleshooting replication
Who is the target user of the feature?
- Systems administrators in large enterprises
What questions are you trying to answer?
- What are the main jobs to be done for systems administrators in the administrator interface?
- What are the main pain points while using the Geo interface?
- What functionalities are missing?
- What functionalities are difficult to use?
Core questions
- What are the main jobs to be done for systems administrators in the administrator interface?
Additional questions
What hypotheses and/or assumptions do you have?
- I assume that the UI is confusing and incomplete and that systems administrators are frustrated with some parts
- I assume that a main job to be done is to troubleshoot replication if it is not showing 100%
What decisions will you make based on the research findings?
Based on the research findings we will likely
- redesign (large) parts of the interface in line with user feedback
- Add/remove new features to the interface to tackle missing functionalities
When do you need this research to be completed? (Milestone or date)
12.9
I'd love to schedule first improvements in 12.10.