Liquidation Hub
Role
Timeline
Product Designer
10 months – Present
Description
This was a work project to create an innovative feature and problem solve current UX/UI for a B2B E-commerce site. Some name changes have been used for the sake of confidentiality.
Project goals
1
Create a feature to help the sales team reduce transaction times & minimize the risk of lots selling out while in cart.
2
Innovate a feature to allow users to offer by category.
Our adventure began with a request from our sales team, but as we dove into brainstorming and designing, we unveiled an exciting opportunity to create an innovative experience that benefits both users and the business.
Background & users
How
it works
Currently on Liquidation Hub, users can make purchases through our sales team, buy now, or make an offer. Users often rely on our small sales team to help them navigate the purchasing process, but this reliance can lead to delays and potential losses. Each lot is one-of-a-kind and once it's gone, it's gone for good. With limited team members available to fulfill orders, we recognized the need for a solution that would empower both the sales team and users to efficiently gather the lots they desire. The goal? Reduce transaction times and minimize the risk of lots selling out while in cart.
Here’s some Liquidation Hub terminology:​
​
Lots= Consists of pallets or boxes
MSRP= Manufacturer's Suggested Retail Price
Our users:
Initial request
The journey
begins
Our first requirement was to create a feature called "Lot Builder". This was supposed to allow users to create their own lots and make offers based on those lots. Fast forward, we shared our first solution with leadership and shortly an additional request came in based on conversations from our top clients. Remember how I told you our users can purchase through the phone? Well when they do, they are able to make purchases based on the MSRP or by categories rather than just the ask price however we do not have this available on the platform.
Here was our first solution before the new requirements
Solution 1 - Lot builder
That being said...
Our new request was to Implement a feature that allows users to be able to offer by category.
Defining the problem
New goals in mind
With this new requirement, the goal was to provide users the option to offer by category while still keeping the purchasing process user-friendly for others who are still getting familiar with the platform. We needed to make sure that introducing this new feature enhances the experience without overwhelming new users. By addressing these needs, we aim to elevate the user experience while optimizing sales processes on our platform.
Here are our new problem statements:
Challenges
Here comes the hard part
The project presented unique challenges, primarily due to the absence of predefined business requirements, as this initiative had never been undertaken before. As we navigated through the development of our solutions, our business analysts and product team engaged in a collaborative process to identify and define what was necessary to meet user needs and business goals. This iterative journey involved constant communication and feedback, allowing us to adapt and refine our approach in real-time. By working closely together, we were able to establish a framework that addressed the complexities of the project and set the stage for innovative solutions tailored to both users and the business.
The first solution, known as the Lot Builder, faced significant challenges due to its overly simplistic approach to grouping categories. By categorizing all items under broad headings—such as placing all men's athletic shoes into a single section—we overlooked the complexity inherent in the lot listings, where a single pallet could contain multiple categories. This fundamental flaw in our initial design led to the solution's failure, underscoring the need for a more nuanced understanding of the product's structure.
Ideation & archived solutions
Innovation ahead
At first, we assumed offer by category would be one input per category. We received more details about how it could work:
-
Offer by category can only be done by % of MSRP so the business side can determined what percent goes to each category to understand how users are buying
-
Categories and conditions work like this: Mens athletic shoes brand new is one input and Men’s athletic shoes brand new damaged box is another input
-
We won’t be able to determine who is the highest offer if they offer by category
Some solution brainstorming after the details:
Here were some other failed solutions
(Unfortunately I do not have the low-fi wireframes and sketches so please enjoy everything in High-fi Yay!)
Offer / Buy separation in cart
Mini cart to track offers if user selects "Bulk offer"
Then there was also the category calculator...
Category calculator
Iterations & end results
Making changes
The iterative process that followed was extensive and marked by continuous trial and error. Since exact requirements were not provided, as this had not been attempted before, our team engaged in numerous meetings and workshops with stakeholders to gather insights and feedback. These collaborative sessions were crucial in identifying how our proposed solutions would impact both users and the business. Through these discussions, we gained a clearer perspective on the diverse needs of users and the intricacies of the inventory, which guided us in refining our approach. This experience taught us the importance of adaptability and thorough stakeholder engagement in the design process, ensuring that we could develop a solution that accurately reflected the complexities of the lot listings while enhancing the overall user experience.
Here are some questions we formulated after the
category calculator:
Which led us to our final solution:
After feedback and more brainstorming here was the final solution:
List:
Solves gathering lots in one place (for both users and sales)
Offer by category modal:
Provides details of selected lots, a break down of categories and is done by % of MSRP
![Modal- Offer by category [Empty].png](https://static.wixstatic.com/media/c452de_470474330768417ca366fa81d408785d~mv2.png/v1/crop/x_66,y_41,w_1308,h_878/fill/w_979,h_659,al_c,q_90,usm_0.66_1.00_0.01,enc_avif,quality_auto/Modal-%20Offer%20by%20category%20%5BEmpty%5D.png)
Offer by lot modal:
Lets users offer on individual listings all at once after gathering them in their list
![Modal- Offer individually [Empty].png](https://static.wixstatic.com/media/c452de_eb6186b67e2143728b6504698c103052~mv2.png/v1/crop/x_66,y_41,w_1308,h_877/fill/w_978,h_656,al_c,q_90,usm_0.66_1.00_0.01,enc_avif,quality_auto/Modal-%20Offer%20individually%20%5BEmpty%5D.png)
Final prototype
Offer by category / lot
Conclusion
Where we currently stand
While our project is still in progress and has not reached completion, we have made significant strides in addressing the complexities surrounding the offer process by developing a category calculator that empowers users to calculate their offers based on MSRP. This solution offers flexibility by allowing users to choose whether to apply their calculated percentages, thereby not mandating category-based offers. Throughout our iterative design process, we encountered numerous challenges, particularly in balancing business requirements with user experience. These experiences have highlighted the importance of prioritizing user needs, as certain business-driven demands could compromise the overall usability of the platform. As we continue to refine our approach, the insights gained will guide us in creating a more seamless and satisfying experience for our users, ultimately benefiting both the business and its customers.
Key take aways:
1
2
3
Developing over seven different solutions taught me invaluable lessons, particularly in navigating the absence of predefined business requirements. Our early attempts, such as the Lot Builder, taught valuable lessons about the intricacies of user needs and the importance of nuanced design. My team and I learned that grouping categories too broadly could overlook the unique nature of our lot listings, prompting us to refine our approach with each round of feedback.
The iterative feedback process was a significant component of our journey. This collaborative spirit not only fostered innovation but also deepened my appreciation for the balance between business objectives and user experience. As we explored the request to implement a feature that allows users to offer by category, I realized the importance of keeping the user experience at the forefront, especially for those still familiarizing themselves with the platform.
This project has reinforced my belief that effective solutions emerge from a dynamic process of adaptation and empathy. As I continue to enhance the Liquidation Hub, I am excited about the impact my efforts will have on elevating the user experience and optimizing sales processes. While the project is still in progress, I am eager to see how these lessons will culminate in a transformative solution for our users.
And finally the biggest take away of all...
The meetings I participated in felt like navigating a conversation between two distinct languages. The product team and the business side often operated with different vocabularies, and it was only in these collaborative sessions that we truly began to understand each other's perspectives. Each discussion became a translation exercise, revealing why certain ideas might falter or succeed. By bridging the gap between our viewpoints, we created a shared vocabulary that allowed us to align our efforts, ultimately enriching my understanding of the design process and emphasizing the importance of collaboration in developing effective solutions.The path is rarely linear.