Solution Validation for role overview, details and assigned users

What did we learn

Results
Overall, feedback to the proposed interface from participants to be positive, they found the experience to be intuitive and well aligned with their expectations. We validated that a progressive disclosure pattern for group and project hierarchy is the best option for listing out user's access details.
More details can be found on dovetail.

Proposed role overview page with name, description and directly assigned users is clear and informative

Participants noted that descriptions for each role in the table is clear and informative, giving the right level of information to understand when best to use each role.

Participants had similar positive sentiment for the proposed role details page, noting that "it's helpful to see how many permissions are enabled" and "to see how many users are assigned"

Recommendation: Move forward with proposed role overview and detailed permissions page.

Participants expected to navigate from the overview page to view all users assigned

When prompted to view the number of users assigned a role, 3/15 participants expected to navigate directly from the role overview page by clicking on number of users.

Design improvement: Update number of users assigned to be clickable and route them to the users assigned list for each role.

Listing out group and project details (version 2) in expandable pattern tested best with user expectations

We tested 16 participants in total across 3 versions of the user assigned list, task completion and sentiment detailed below:

	Version 1	Version 2 ✨	Version 3
Mock-up
Task completion: View groups and projects for a specific user in that role	60%	100%	80%
Sentiment	2/5 participants expected to click on user to view details	1/5 participants needed to understand the difference between membership types 2/5 participants liked being able to expand the list 1/5 participants expected a search function	2/5 participants didn't expect a pop-up window to show group or project details

Recommendation: Move forward with Version 2 of the user list with expandable groups and projects. Add additional context when presenting membership types. Add the ability to search for users or groups and projects when viewing users assigned a role.

What's this issue all about? (Background and context)

We have a proposal for:

• Admins and groups owners to view all roles available on their group or instance
• Show how many users are assigned each role
• Provide details on which users are assigned this role and for which groups and projects

What hypotheses and/or assumptions do you have?

• Admins and group owners lack the visibility into what role and access users have in groups, subgroups and projects
• Having detailed information on users assigned to a role will help admins and group owners maintain compliance with their internal access policies
• Access policy maintainers will use the information to audit users and their role
• Access provisioners will leverage the information to remove or increase users access

What questions are you trying to answer?

• Can users navigate easily to find the level of information they need?
• What questions do admins and group owners want to answer using the data in roles and permission, user assigned tab?
• Are there any gaps in the information presented? What are some of ways in which they would want to transform or manipulate the data?
• Do admins and group owners need to know user's inherited, direct and shared access of a user to a group, subgroup and project?
• How often will they access this information?

What research methodology do you intend to use?

• Unmoderated user testing, there will be multiple options for the UI tes

What persona, persona segment, or customer type experiences the problem most acutely?

• Administrators / Top level group owners

What business decisions will be made based on this information?

• Move forward with proposed designs

What, if any, relevant prior research already exists?

Who will be leading the research?

• @ipelaez1

What timescales do you have in mind for the research?

Relevant links (problem validation issue, design issue, script, prototype, notes, etc.)

• Screener and script (WIP)
• Usertesting links - Figma Prototype
  • Test for Option 1 - Prototype for Option 1
  • Test for Option 2 - Prototype for Option 2
  • Test for Option 3 - Prototype for Option 3
• Results
  • Usertesting result extract
  • Dovetail

Checklist

• Draft goals and objectives, review with collaborators
• Create test plan, review with collaborators
• Build prototypes
• Launch study on usertesting.com
• Analyze and communicate findings
• Close issue 🎉