Solution validation for: Revisit the Kubernetes cluster UX after the Agent is released
What's this issue all about? (Background and context)
We are redesigning the Kubernetes homepage to include both Agents and cluster integrations in a single page. We are also working on the language we use for GitLab's Kubernetes management in the UI and in the docs (hopefully we can collaborate with Marketing as well to ensure consistency across all channels).
What hypotheses and/or assumptions do you have?
- That the user mental modal is that both installing an Agent on a cluster and connecting a cluster with its API certificate are ways to integrate your cluster to GitLab and not regarded in a different way.
- That users want to have a view of all their Kubernetes integrations.
- That most users would use both types of integrations and, hence, a combined view would have a purpose.
- That the right way to speak about Kubernetes management in our UI and docs is by referring to them as Kubernetes integrations.
- That the right way to speak about the GitLab Agent is by referring to it as "Kubernetes integration with Agent" and that the right way to speak about connecting a cluster with its API certificate is "Certificate based Kubernetes integration".
What questions are you trying to answer?
- Whether our hypotheses are correct.
- What information do users expect to see in the Kubernetes landing page?
- What design patterns are the most suitable for the Kubernetes landing page to accommodate the information the users want to see?
What research methodology do you intend to use?
Remote usability evaluation with usertesting.com.
What persona, persona segment, or customer type experiences the problem most acutely?
- Allison (Application Ops)
- Priyanka (Platform Engineer)
- Sidney (Systems Administrator) and maybe Sasha (Software Developer)
What business decisions will be made based on this information?
How we speak about Kubernetes.
What, if any, relevant prior research already exists?
Who will be leading the research?
TBD
What timescales do you have in mind for the research?
Milestone 14.0 onwards
Relevant links (problem validation issue, design issue, script, prototype, notes, etc.)
Design issue: #254998 (closed)
Tasks
-
Finalise the design and choose which designs we want to test -
Create usability study in usertesting.com -
Recruit participants (not sure it's needed) -
Publish research
Edited by Maria Vrachni