We invited two lead ship engineers to document their workflow. The workflow was then approved by the six-member principal ship engineers committee and incorporated into the software requirements document.
As building, assessing, and reporting do not share common functions, and users often use these three functions in distinct scenarios, I developed separate graphical user interfaces (GUI) for each process. This allows users to easily identify which process they are in and navigate each one more efficiently
The Building, Assessing, and Reporting functions are nested in different areas which is confused to use.
Similar to the building, assessing, and reporting functions, the processes involved in building a ship model also differ significantly depending on the task. For instance, engineers may enter data to create the coordination, whereas selecting specific materials from the library may be a crucial task for other engineers.
The main functions in building the coordination was entering large amount of data. In the first phase, I designed the example image to refer the data, and planned to include interactive data.
This product had 4 default libraries, and users are able to add more libraries. I used the same layout for all the library to keep the experience consistent.
Loads is special part before building the ship model. I designed the interactive tables to help engineer adjust the data to see the load trends.
Problem 01: Unclear information structure of ship element (aka, in figma, how to design the relationship components, pages, frame);
Problem 02: Limited place to put 40+ functions;
Ship Engineers were focusing on individual modeling functions experience, and I tried to use metaphor to communicate how important and urgent for the application to organize the ship structure.
In accordance with business requirements, I structured the information architecture (IA) and tested it with our two principal engineers.
Other part of this project is to rebrand the software
After this project, I realized that had been in UX team in my previous company for 3 years, I have not realized the work my design manager and senior had done which is fundamental and incredibly important. It is difficult to implement UX design successfully without first educating your teammates on UX basics, particularly in traditional industries that still rely on recording tutorial videos.
After discussing with other senior designers and managers, I realized that if I could go back in time, I would have spent more time educating my colleagues on UX principles and tried to hire more UX experts to provide backup support. If this was not possible, then we should have started by using UX strategies to plan our work first.
It is crucial to communicate work process, advocate for UX principles, and build up the team. This is even more important than simply finding clever solutions to design problems.