Background
The app is not popular among users.
I was assigned to improve the Inventory functionality of Turvo's software product. Although Inventory 1.0 had been available for a few years, it did not gain much popularity among Turvo's customers due to its limited features.
Discovery
Qualitative user interviews
The most effective method for identifying gaps in the current functionality is through direct user engagement. To achieve this, I put together a detailed discussion guide and conducted qualitative user interviews via remote meetings with our existing customers - Watsonville, Freshpet, Applegate, Orca Bay, and B&G Foods.
Product and research objective
To understand end-user use cases, feedback, and decision-maker input.
Identify the gaps where user needs are not met.
Research methodology
Conducted 7 remote group interviews with Ryder and customers of Lineage (Watsonville, Freshpet, Applegate, Orca Bay, and B&G Foods)
2-6 participants/representatives from the customers for each group
Collected information on:
Use cases for using Inventory within Turvo
Tasks performed
Reports referenced
Personas
Who are the users?
I defined two primary personas for the project: Customer Inventory Analyst and Facility CSR
The participants we talked to:
C-suite / director-level decision-makers
Facility CSR
Customer Inventory Analyst
Sales representatives
Shipping & Receiving
Warehouse manager
Logistics coordinator
What is their current experience?
Findings and Outcomes
Limited functionality to find the needed inventory and analyze it
★ What we heard from end-users in their own words
Feature requirements
The primary focus is to enhance inventory visibility and address data inaccuracies.
Enhanced Inventory Search & Filtering
The system should provide robust inventory filtering options, enabling users to sort and search by lot number, code dates, pallet ID, and traceability IDs for quicker and more precise inventory searches.
Inventory Detailed View with Traceability Details
The system must provide a detailed inventory view, including traceability details such as location, hold codes, substatuses, related orders, and documents.
Inventory Subtotals
Implement subtotals in the UI, displaying quantities, weights, and other measurement units
Accuracy of System Status Reports
Ensure accurate system statuses are reported in outputs and during reconciliation to uphold data reliability and support operational accountability.
Backend fix
Ideation
Search and filter enhancement
I began working on helping users locate and filter lists to find the needed inventory. I put together user stories to define filter requirements, which led to the low-fi mocks.
Item filter
Traceability ID filter
Attributes (substatus, hold code)
FIlter’s Placements
Inventory detailed view
Another requirement was to show inventory details. User stories helped me identify which specific details our customers need to see and guided me in creating mocks for how those details could look.
First prototype
Assembling all parts to identify gaps in functionality and interaction.
We played with the prototype within the team and also shared it with some folks from customer success. Several changes were made based on feedback, and I highlighted some of them.
Hi-Fi mockups
Applying existing patterns and adding new ones.
Filter modal, filter states
I mostly applied existing patterns and styles from our design system. In the filters, I added color coding for substatuses and hold codes to add emotional impact and improve interface readability.
Cards
Design for each card for inventory details: the item card and facility card with traceability details and attributes were completely new additions to the system. Related orders/shipments followed existing patterns of similar cards.
Inventory list view
Prototype
Follow-up research
Evaluate the effectiveness of our updated designs
I conducted follow-up research to evaluate the effectiveness of our updated UX designs with Customer Inventory Analysts and Facility CSRs, whom we had previously identified as the primary personas for Inventory. All of them are part of the same group of customers with whom we had earlier discussions.
Research methodology
Remote user testing and design feedback were collected from 3 Customer Inventory Analysts and 3 Facility CSRs.
Each test session was 30 minutes and moderated
Participants were asked to view designs and complete tasks using clickable prototype while being observed via Zoom video.
Test outcome
Overall Usefulness of Inventory 2.0
Factors influencing participants' ratings of Inventory 2.0's usefulness:
Extremely/Very Useful: The ability to track inventory from the highest to the lowest level and see what is happening at each level was greatly appreciated.
High Rating: The short learning curve and ease of learning over time.
Moderately Useful: Some confusion regarding terminology.
Each large company uses different terms for certain filters, such as "Substatus codes" vs. "Production code.
