User Testing - Seats Usage - Vision
Summary
This is the UX issue to capture testing of the Seat Usage Vision described in &5872.
Research Questions
- What do users need to know when managing seats?
- Do users understand the elements within the view?
- What do they think is useful? Useless? Why?
- Does this proposal meet their needs? Why/why not?
Test Plan
Recruiting
- 5-6 Participants who are group/subscription owners in companies with at least dozens of GitLab user accounts in a subscription.
Prototype
Test Questions
Background Questions:
- What is your role at your current company?
- What are your responsibilities around subscription management at your company?
- What are the critical things you need to know to manage seats within your organization?
Feature-specific questions:
- Can you explain to me what you're seeing here?
- Can you explain the purpose of the graph? How do you interpret it? Why do you think that?
- What is the table below the graph showing? Why do you think that?
- What is the purpose of the expand/collapse? Why do you think that?
- Where would you expect to find this page within GitLab?
Post-test questions
- On a scale of 1 (useless) to 5 (useful), how would you rate the usefulness of this page? Why did you give that rating?
- We focused on three components today (list out each one). Which is most useful? Why? Which is least useful? Why?
- Can you please rate how easy or difficult it is to interpret the information on this page (1 - Difficult to 5 - Easy). Why did you give that rating?
- Do you feel any information is missing from this page to help you with seat management? (If yes: 'what's missing? Why is that useful for you?').
- (Also, refer to their answer to question 1, where they told you what they needed to know, prior to looking at this. If there are differences, call those out and have them explain.)
- 'Lastly, can you please rate how this proposal may/may not meet your current needs around seat management (1 - Does not meet my needs to 5 - Meets my needs). Why did you give that rating?
Edited by Matthew Nearents