Case Study: vMOX
Company: vMOX, helps businesses better manage their corporate-liable mobile assets. Through technology and the team’s efforts, they optimize costs, increase efficiency, and provide visibility and control into the mobile environment.
Role: UX/UI Designer
Tools: Confluence for usability test plan and reports, paper sketches, and Axure
Timeframe: 2 weeks
Users: The procurement team
Challenge
The procurement team needs an updated interface to review and confirm device updates from the carrier before they are customer-facing.
Approach
After receiving the project requirements, I identified gaps in my understanding that needed to be explored. Thus, I set out to interview Tim and Sarah the procurement specialists with further questions.
Some Questions Asked:
Could you walk me through your process of reviewing catalog items?
What are some pain-points you regularly encounter with this process?
How frequently are you checking catalog items?
“I want to be able to take a quick peak every morning and see if there are any red flags.”
“ The typeahead is super finicky, I’m not sure why that is. But it can definitely delay the process”
“ I would like there to be more visibility into the product name. Often when I Google search to confirm the product name, I have to search around to make sure I’ve found the right one.”
Meeting with the procurement team really helped to clarify some questions I had regarding the process. Some points I learned were that each team member is in charge of checking their own assigned customer items and catalog staged changes are made once a week as opposed to the original daily assumption. Also, a common pain point was that the typeahead dropdown was sensitive to cursor movements resulting in a poor user experience. Moreover, there was a desire to include more valuable information with the hope that it would allow them to make decisions more easily.
Mocking it Up
Insights from my PM and users was enough to get me started with potential design directions. Since I needed to utilize the design system as much as possible, I went ahead and did some rough sketches with our design system’s list view template in mind. Sketching it out to start helped to provide enough information needed before moving into high fidelity. Once I had a mockup ready, I presented it in front of users for testing.
User Testing Feedback
😞 Losses
Desired an additional action after selecting statuses to help prevent accidental errors
Would like to hover over the warning icon to see the previous price
Preferred to see the categories displayed in a different order
😀 Wins
Information was scannable and easy to understand
Appreciated seeing the total amount in each filter section
Interaction to select ‘accept’ ‘deny’ or on ‘hold’ was considered to be useful
Final Design
Main Catalog Page
Filter View
Outcome & Results
Overall, the design was well-received as it met the initial requirements. Moreover, the users felt it saved them time and granted greater visibility into the catalog review process. Not every user request could be met, as there are often trade-offs to keep in mind. Such as the desire by one user to integrate a reporting feature. Unfortunately, that had the potential UX drawback of slowing down the application. All in all, the overall success of the project was by far a team effort and it couldn’t have been completed without the help of my PM, fellow designers, users, and developers.