Left Side Navigation Tree-Test: Project-Level (top-level items)
What's this issue all about? (Background and context)
What are the overarching goals for the research?
-
Propose and test new IA structures based on research findings.
-
Assess the findability of the left side navigation structure of GitLab.com and identify areas for improvement.
What hypotheses and/or assumptions do you have?
What research questions are you trying to answer?
- How do users expect to navigate GitLab?
- Which content is easy to find?
- Which content is difficult to find?
What persona, persona segment, or customer type experiences the problem most acutely?
All GitLab users. Prioritizing GitLab users who have knowledge of a variety of features.
What business decisions will be made based on this information?
We will make improvements to the left sidebar IA based on the research results. Results from phase 1 will influence Phase 2 research approach.
What, if any, relevant prior research already exists?
#43 (closed) #109
Relevant links (opportunity canvas, discussion guide, notes, etc.)
Progress
-
UX Researcher: Draft tree-test tasks. -
UX Researcher: Enter tasks and navigation into TreeJack. -
UX Researcher: Open a Recruiting request
issue. Assign it to the relevant Research Coordinator. - #1119 (closed)-
Research Coordinator: Distribute the tree test to a sample of participants. -
UX Researcher: Review responses received so far. Amend survey if necessary. Advise Research Coordinator to continue recruitment.
-
-
UX Researcher: Notify Research Coordinator of survey closure. -
UX Researcher: Update the Recruiting request
issue. -
Research Coordinator: Pay participants.
-
-
UX Researcher: Synthesize the data and identify trends, resulting in insights. -
UX Researcher: Document insights in Dovetail -
UX Researcher: Update the Problem validation
research issue. Link to findings in Dovetail. Unmark asconfidential
if applicable. Close issue.
Edited by Ashley Knobloch