Vast and Complex Data: Users encounter difficulties locating required information, leading to time wastage and inefficiency as they spend significant time searching and filtering data in the backend.

Non-Modern UI Interaction Patterns: The current flow doesn't follow modern UI standards, confusing users during using the component and extending their adaptation period.

Readability: One of critical issue was readability.

In order to facilitate the organization of RFQs on this page, we implemented a foldering approach. It facilitates the organization of RFQs by vendors. In order to facilitate organization, users may establish folders for various RFQs or location-based RFQs.

As I was examining the application, I noticed that there was no way for the user to extend the RFQ deadline; if the user needed to extend the time, he would have to resubmit the RFQ from the beginning. This was an ineffective solution, and I recognized an opportunity to enhance the user experience.

This "Add More Time" functionality has been suggested to enable users to extend the RFQ time if necessary. The "Time Remaining" field has been colored red, and a condition has been incorporated to indicate that the RFQ has 24 hours remaining. In addition, I have devised a reminder email to inform users that they may require additional time.

It is not a prudent decision to request this much information from the user. By redesigning the application, I sought to reduce the number of steps that the user must complete and to save time during the operation. I combined the "Products Details" and "Header Details" into a distinct page.

The RFQ creation process has been simplified by reducing the number of redundant inputs. The "Tag Part Number" system was implemented to improve the efficiency of order management on both the Bryzos system and the buyer's internal system.

The RFQ negotiation module is a complex program in its own right, and we must add a "Line" level note system on top of it. The obstacle was that we were unable to modify the existing functionalities, as this would have resulted in a lengthy development process that would have taken several months.

Approaching the iterative design process was our strategy. Several sessions later, we generated a multitude of solutions; however, we must select one that is both simple to use and understandable. Two concepts were combined to form a single entity. After conducting numerous assessments, I delivered it over to the development team.