I designed and 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, Lot Management, and other areas of the Requis platform.
Much of my work involved improving existing features while supporting new product experiences, identifying where complex workflows created friction and working closely with Product and Engineering to make them clearer without disrupting processes users already relied on.
One example was Lot Management, where recurring customer support requests helped us identify opportunities to make a complex workflow easier to understand and navigate.
Lot Management helps users prepare and manage surplus materials before listing them for sale through Buy Now, Make Offer, Auction, or Inquire.
We combined support data, internal feedback, and hands-on research to understand where users were getting stuck.
The same questions kept coming up through support, pointing to consistent friction.
Customer-facing, Product, and Engineering reviewed the patterns together.
We stepped through the current experience to see where users got stuck.
I explored the journeys in depth for confusing or unclear moments.
With the problems clear, I worked with Product and Engineering to shape a response.
I brought the findings back to the team to review the problems together and understand technical considerations.
I looked at similar platforms and relevant UX patterns to inform possible approaches.
I developed initial directions, reviewed them with Product and Engineering, and refined the solutions before development.
Three areas became a particular focus: action clarity, filtering, and navigation through long editing workflows.
The Lot Listing Preview relied on icon-only controls for several management actions. During my review of the workflow, I identified these controls as a potential source of ambiguity because users had to recognize each icon before knowing what action was available.
I paired the icons with visible text labels for actions such as Unlist Lot, Edit Lot, Attach, Edit Images, Add Assets, and Go Back, making the available actions explicit without changing where users accessed them.
Managing a large number of lots required users to narrow the list by attributes such as sale method and status, but the available filtering options weren't immediately visible from the main Lot Management view.
I introduced a dedicated filter panel that kept the lot list visible while users refined their results. Active selections were surfaced above the table, making it easier to understand which filters were affecting the results and remove individual filters when needed.
The Edit Lot experience contained multiple sections of information, but the overall structure wasn't visible from the main editing view. Users had little indication of what information was available or where to find it as they moved through the workflow.
I introduced persistent section navigation for key areas, including Info, Description, Seller Terms, Finance, Questions, Inspection, Shipping/Pickup, and Images, so users could see the structure of the lot and move directly to the information they needed.
The redesigned experience was released behind a feature flag and tested with selected users through our customer-facing team.
During testing, users were able to navigate and manage their lots without needing support during the workflow. Based on those results, the changes were released more broadly.
Over time, the customer-facing team started receiving fewer support tickets about the areas we had reworked, the same recurring questions that had surfaced the problems in the first place.
The same approach extended beyond Lot Management to other areas of Requis.
Designed and refined responsive interfaces and interactions across complex procurement workflows, including the mobile experience of a procurement project, from the workspace overview to requests, suppliers, and commercial questions.
A new feature I designed: from a CRM account, users find the matching company in the Requis network, verify it's the right one, and create the connection, and when the company isn't in the network yet, they can invite it directly from the same flow.
Working across multiple areas of a large platform meant thinking beyond individual screens. I used familiar layouts, interaction patterns, components, and visual hierarchy to create experiences that felt connected as users moved between different parts of the product.
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.
Responsive behavior. The same lot detail adapting from desktop to tablet to phone: multi-column on larger screens, a single readable stack on mobile.
Collaboration with Product and Engineering was part of my process from early investigation through implementation. I worked closely with the Product Manager and engineers to review customer feedback, investigate problems, discuss technical considerations, and evaluate potential solutions.
Design reviews continued as features moved into development rather than ending at handoff. I reviewed implementations with the team, discussed technical constraints, and adjusted designs when necessary while preserving the intent and usability of the experience.
For changes such as the Lot Management improvements, new experiences were released behind feature flags so they could be tested with selected users before wider release.
Working on Requis reinforced that meaningful improvements didn't always require rebuilding an entire experience. In complex enterprise products, changes to terminology, hierarchy, navigation, and interaction patterns could remove meaningful friction, especially when those decisions were grounded in recurring customer problems.
The most effective solutions often came from understanding where users were struggling, collaborating closely across teams, and improving familiar workflows without adding unnecessary complexity.
