Collaborators Case Study
I reduced friction and time on task for users add, editing and removing collaborators from their account.
Problem statement & the process
Defining the problem we're solving
Problem
Users are spending an unnecessary amount of time adding, editing and deleting collaborators due to the page's composition.
The main concern was that each collaborator would be added and appear multiple times rather than consolidating into a table row per role. Some customers would have more than 1500 rows in this table.
The solution
The solution reduces friction when adding, editing and deleting collaborators as well as consolidates each role into its own table row.
Find out how I saved time on task below.
Before & After
A snapshot of what the Collaborators page used to look like.
A quick brainstorm
After a couple conversations with a customer and their admin, I collated my notes and started the following:
- Empathy mapping
- Current vs future concept (text based for IA purposes)
- Wireframing ideas
Prototype
I created components for the proposed solution, then prototyped to test.
Testing & Feedback
I interviewed 4 customers and 1 internal stakeholder to validate my solution.
Customer / User feedback
Overall they liked the consolidation of site permissions under one role.
Time on task
Their time on task will be significantly lower when making changes.
Customer / user feedback
Mentioned that they would like to see the address of where a site is located.
Customer / user feedback
Mentioned that they would like to filter by site / state.
Updates based on feedback
The updates that came out of testing were implemented as slight improvements to the overall solution.
Final Product
Future considerations
The solution outlined is only the start of the journey. I proposed this concept as a future enhancement to further consolidate collaborators.
