UX Case Study
Emdund Optics' Knowledge Center houses over 1,500 resources, including videos, application notes, technical tools, webinars, and more. The previous design consisted of disconnected lists, lacking organization. The goal was to create a filterable, user-friendly experience.
Old Resource organization:To ensure a successful project, we followed a general process:
A small committee was assembled, consisting of myself (UX and design), a content engineer, and the marketing manager. We conducted a competitive analysis, reviewing companies with similar filterable resource sections to guide our approach. Additionally, we gathered feedback from customers and engineers and outlined key personas who would use the Knowledge Center. Based on this research, the following decisions were made:
After gathering all the feedback, I began working on a mock-up, which went through several iterations and discussions with the committee. The final working mock-up, shown below, was coded in HTML, JavaScript/jQuery, and CSS.
The personas revealed that a mobile-first experience was essential, as students and research customers primarily access content via mobile. This was in contrast to our B2B marketplace site, which is designed with a desktop-first approach.
After the webpage was built, it was handed over to the programming team to integrate with the database and ensure functionality. Once the technical setup was complete, the project was passed back to me for final clean-up and to ensure the design aligned with the original vision. The page then went through testing and quality assurance by various internal volunteers, identifying and fixing any bugs.
This version of the Knowledge Center was live for over a year when another round of analysis was proposed.
Our analysis team collected feedback and tracked customer usage to inform the next set of changes:
Once the requirements were received, I began working on the next "working mock-up" and took the opportunity to refresh the design. After I completed the new design, I collaborated with our analysis team and a programmer to review it, and a few changes were proposed. The final design was then approved for implementation. See below for the updated version.