RyderShip | New Inventory Tool
The image above depicts a new tool for inventory relocation. It is optimized for portrait on a tablet and allows you to move one single SKU OR a group of SKUs from one shelf to a new shelf or bin. There is a "from" section on the left and a "to" section on the right with the ability to change the role of an item (in case the reason it is being moved is because it is damaged). There is a summary at the bottom with a button to "Transfer Inventory" or "Reset" if a mistake was made.
Before Updates
The image above depicts a new tool for inventory relocation. It is optimized for portrait on a tablet and allows you to move one single SKU OR a group of SKUs from one shelf to a new shelf or bin. There is a "from" section on the left and a "to" section on the right with the ability to change the role of an item (in case the reason it is being moved is because it is damaged) as a dropdown option. There is a summary to the FAR right with the ability to "Transfer Inventory" via the button. However, there is no way to quickly clear the form if a user were to make a mistake.
TL;DR
Type of Company: Logistics (SaaS, B2B, B2C, DTC)
Problem: Warehouse workers do not have a quicker way to combine inventory in order to make room for new inventory. The current process takes upwards of 15 min! Time is money for warehouse workers - so, if we can reduce the time it takes to do any task - we are ultimately shipping items faster and in higher volume.
Tools: Interviewing, Usability Testing, DataDog RUM, Figma Prototyping, Notion, ADO
Solution: Built a net new tool optimized for tablet based on our DataDog RUM review of analytics. It decreased the time it takes to move inventory from one bin to another by 60%.
Skills: Research, Analysis, Interaction, Accessibility, Information Architecture, Visual Design
Pain Point:
Inside a warehouse, . The current process takes upwards of 15min inside the warehouse - costing the workers precious time they could be utilizing elsewhere.
Objective:
To build a accessible, user-friendly net new tool in order to expedite the process of moving a single SKU or a group of SKUs from one shelf (or bin) to another shelf in order to decrease the time it takes to optimize inventory management inside a warehouse.
Considerations
The persona types who will utilize this feature are warehouse worker, warehouse managers, and dev ops.
Examine what device type the users anticipate to utilize this new tool.
Strategy:
Interview users from every persona type to understand how they each use this feature.
Usability test by building a prototype and running design thinking sessions to ensure we are building the right product for our user persona types.
Any enhanced feature components will be captured in a future sprint via backlog.
Collaborate with engineering to understand code constraints and edge error case handling.
First Iteration
The image above depicts a new tool for inventory relocation. It is optimized for portrait on a tablet and allows you to move one single SKU OR a group of SKUs from one shelf to a new shelf or bin. There is a ""Transfer from Source" column on the top left and a "Transfer to Destination Shelf" right below it. To the right there is a summary section with a "Transfer Inventory" button at the bottom right. There is a link at the top right to "Reset" the form if a user were to make a mistake.
User Testing Results:
"The icons inside the switch feel confusing. I am not sure what they mean and if they are adding anything to the experience for the user."
~ User
Our users are often not bilingual. This is challenging because when all that copy is translated - it can extend wider than the current form allows - meaning we will need to wrap the copy.
Another issue is the actual verbiage before translation - it feels ambiguous.
The added icons inside the switch and to the sections are ambiguous.
The summary section feels hard to read.
The "Reset" link is not obvious enough for our persona types.
Where do we go from here?
Add in the ability to log a job as it transfers and allow that to be viewed by the user. We found that during testing, there will be times when the jobs can take more than 15 seconds. We want to be able to allow a user to continue to make transfers EVEN though the prior job is still initializing and processing.
Create a drawer component to contain all jobs.
Inside this drawer - add in the ability to view all jobs still working and be able to stop jobs which are taking an excess of time.
Consider adding in the ability to "Retry" a job which is extending it's typical time to process or failed to process.