Internal Hardware Management Interface
Hearing Instrument Management System (HIMS)
GN ReSound had a need for an update of their internal management system used to structure XML files for new and existing hearing instruments developed. This system essentially allows for the building and setting of features for instruments resulting in the compilation of XML files used upon installation of the software in markets across the globe. This involved rebuilding the outdated interface no longer used involving a major UX component to enhance the speed and efficiency of internal employees upon software version releases.
Client GN ReSound
Skills Interface Design, Information Architecture
Role Design Lead
Simplifying Complex Processes
Early on in the project, I saw the need to simplify this process with a clean interface that would reduce clicks and allow users to complete multiple tasks in an efficient manner. This involved building out the basic wireframes in Axure and heavy prototyping to illustrate the flow and functionality of the interface. These prototypes were used in the early phase to present to stakeholders as a means of determining if we were meeting the primary requirements set forth.
Interviews with stakeholders were conducted as a means of data gathering as well as a heuristic analysis of the previous tool to understand the essential needs involved in the HIMS process. We also used flowcharts and diagrams to map out the various scenarios stakeholders were presented with and to ensure we all had accurate mental models of what was to be built. In addition, we involved developers located in Copenhagen to communicate the interface needs of the project and align development with design.
Axure was the primary tool used for this project and was supplemented with Screenflow. As noted above, initial wireframes were built and used internally as discussion tools. Once we were satisfied with the wireframes, prototyping began to show the complex flows and interactions. We used these prototypes in meetings to show quick interactions and flows. In addition, I decided to record the interactions using Screenflow and made videos of the flows. These videos were then uploaded to an online repository for stakeholder review. Having a video of the different interactions became a powerful tool for selling our design. You can read more about this process here.
Axure is a powerful tool. However, I realized we would need pattern libraries to work more efficiently and developed them in the early phases of the project. In addition, we also used ScreenSteps to develop functional specifications. While specifications and documentation of this sort is often not considered agile, we found it necessary to both document design changes and speed development by providing a reference for the designs.