UX
Business Cloud Essentials
Business Management Software • User flow • Screen flow • Wireframes • Prototyping
Project Overview
Slow adoption of the new tracking app was linked to the tracking funationality causing confusion in the core product.
Fixing the issues in the core product with the intention of improving confidence across product and increase app usage.
My Contributions
I was the sole UX Designer on this project and took the project from start to finish alone.
Understanding the problem
A new app was developed to support warehouse workers tracking stock whilst on the floor. Pre-development the app had lots of traction from customers, but post-release less than half of the expected customers had adopted it.
The common denominator across the customer feedback is that they didn't feel confident in the tracking functionality in the core product, and therefore wouldn't trust the data in the app.​
The current process around tracking numbers:
​
To add tracking to a stock item they check the 'Use serial numbers on the stock item details
-
All 4 of these checkboxes are very poorly worded
-
Tooltips are very wordy to compensate
-
When the user adds new stock to the stock type the system uses a mix of Serial number and Batch number headings
-
Although the system handles batch number and serial number tackign the same way, users were confused which number to use
Ideation workshop
I hosted a workshop to understand the limitation of the product and user journey for tracking numbers
-
Although the system handles batch number and serial number tracking the same way, users were confused about which number to use.
-
If we change the journey now how will that affect the existing stock items?
-
Is the tracking number field used anywhere else in the system?
Create new stock item
When selecting yes on tracking they then have to pick the type of tracking:
.jpg)
Editing exsisting stock settings
These items have tracking selected, but they need to pick the type of tracking:
Wireframes
If I were designing the full new stock item flow I would change a lot of things about the current screens. Basic best practices and accessibility failures existed throughout the product. But for this project, the scope was limited to areas around the tracking numbers.
​
In the wireframes, I've followed the existing layout to show how the tracking process can fit into the current UI.
Final outcome
I'm really pleased with the end result, although there were challenges with the existing UI. We created a simple, easy-to-follow process for selecting the tracking type on new stock entries and correcting the existing stock tracking entries, either in batch or singular.
​
6 Months post-implementation, adoption of the scanning app increased by 73%
