Product & project context
eazle Distributor is used by distributors to manage customer orders, track order progress, and perform operational tasks throughout the ordering process. As the product evolved, the Order Detail Page gradually accumulated additional information, statuses, actions, and business requirements. While functionality continued to grow, the overall experience had not been revisited holistically, creating an opportunity to improve clarity, information hierarchy, information structure, and usability. Important order information often competed with secondary details for attention, making it difficult for users to quickly understand the state of an order and identify relevant actions. At the same time, opportunities existed to better support user workflows by reorganizing information, introducing clearer prioritization, and exploring additional functionality that could improve the overall experience. This project explored how the Order Detail Page could be restructured to better support operational workflows, simplify information access, and establish a clearer foundation for future product development. The work focused on understanding how information should be organized, prioritized, and presented to help users navigate complex order details more efficiently.
From Structure to Concept
Wireframing and testing
With the information architecture in place, I explored multiple concepts for restructuring the Order Detail experience. Rather than optimizing the existing page, the explorations investigated different ways of organizing information, supporting operational workflows, and improving information hierarchy. Each concept tested a different approach to balancing clarity, usability, and future scalability.
Design approach
1. Defining the ideal structure
Based on the information grouping exercises and user journey mapping, I created an ideal information structure for the Order Detail experience. The objective was to establish what information users need, how content should be grouped, and where hierarchy should be introduced to support faster understanding and decision-making.
2. Translating structure into concepts
The proposed structure was then used as a foundation for exploring different interface directions. Rather than focusing on visual design alone, the concepts investigated how information hierarchy, workflow support, and page organization could be expressed within the experience.
3. Exploring alternative approaches
Multiple concepts were developed to evaluate different ways of presenting order information, balancing clarity, usability, and operational efficiency while maintaining the same underlying information architecture.
4. Building a future vision
The final explorations expanded beyond immediate improvements and explored how the Order Detail experience could evolve over time, providing a scalable foundation for future functionality and business requirements.








