I improved experiences across Requis, a B2B supply chain platform, simplifying complex workflows through clearer information architecture, intuitive interactions, and responsive UI.
I worked across Marketplace, Procurement, CRM, Supplier Storefront, onboarding, and other areas of the Requis platform.
Much of my work involved improving existing features — understanding where users were getting stuck and making complex workflows easier to navigate without disrupting familiar processes.
Lot Management helps users prepare and manage surplus materials before listing them for sale through Buy Now, Make Offer, Auction, or Inquire. The functionality was there, but parts of the experience were difficult to understand.
Important controls relied heavily on icons, making their purpose difficult to understand at a glance.
Managing images and viewing existing images weren't clearly separated.
Users needed clearer context when moving between managing a lot and understanding how it would appear in the Marketplace.
I added clearer labels and hierarchy around important controls instead of relying primarily on icons. The goal was simple: users shouldn't have to guess what an action does.
I created a clearer distinction between uploading and managing images and previewing how those images would appear. This made the purpose of each part of the experience easier to understand.
I introduced clearer navigation cues and a more obvious way to move through the workflow. Small changes helped users understand where they were and what they could do next.
The same approach extended beyond Lot Management to other areas of the Requis platform.
Improved hierarchy, responsive layouts, and browsing experiences across the Marketplace.
Refined responsive interfaces and interactions across procurement workflows.
Designed experiences for managing buyers, sellers, contacts, and Salesforce-imported information.
Improved how supplier information and products were presented within the Marketplace experience.
Working across different areas of the platform meant thinking beyond individual screens. I used familiar layouts, interaction patterns, components, and visual hierarchy to make the experience feel more consistent as users moved between features.
Used familiar interactions and components that could work across multiple features.
Created consistent treatment of primary information, actions, and supporting content.
Considered how layouts and interactions adapted across different screen sizes.
Applied familiar spacing, typography, controls, and interaction patterns throughout my work.
I worked closely with Product Managers and Engineers in an Agile environment, iterating as features moved from design into development.
Reviewing implementations, discussing technical constraints, and incorporating feedback helped keep the final experience aligned with the design intent.
Complex products don't always need bigger redesigns. Clearer hierarchy, familiar patterns, and small interaction improvements can remove meaningful friction without disrupting workflows users already understand.