B777x Instructor interface
Human factor engineer, UX researcher, UX & IxD designer
Project brief
Redesigning the interface focusing on maximising efficiency within the tight timeframe for reaction. This involved ensuring intuitive controls reflective of training patterns and consolidating all functions onto a single layer for immediate accessibility and accommodating new features such as the folding wingtip of the B777x seamlessly.
Defining the requirements
The first step was to gather data. Access to simulator being costly and limited, the ideal method was that of task analysis which due to the procedural nature of the work made it a reliable source. Through interviews with the instructor and SMEs, user flows and requirements were established from which user stories were derived.
Understanding the user
The subsequent step involved establishing user journeys. Initially, card sorting was utilised, followed by prototyping to validate with the assistance of the instructor and other Subject Matter Experts (SMEs). The 'talk aloud' method was employed in conjunction with prototype testing. Pain points were identified and incorporated into the design iteration.
Establishing the user flow
The final stage entailed translating all findings into a tangible design. The collective expertise of the designers, alongside the developers employing an XP method, offered insights into design limitations and options. The resultant design is presented below.
User Flow for Turbulence Set Up
Visualisation
The final step was to translate all the findings into a concrete design. The experience of the designers on one side and developers working on a XP method on the other provided insights into design limitations and options. The final result can be seen below.
Interface for Storms settings
Fighter jet maintenance app
Human factor engineer, UX analyst, UX & IxD designer
Project brief
Redesigning the interface focusing on maximising efficiency within the tight timeframe for reaction. This involved ensuring intuitive controls reflective of training patterns and consolidating all functions onto a single layer for immediate accessibility and accommodating new features such as the folding wingtip of the B777x seamlessly.
Context
Fighter Jet escadrons are made up of older planes that although very reliable need frequent maintenance. It is executed very meticulously and methodically. Any of the planes can be call to mission at any time and there is no space for delays.
The main responsability for this project was to generate sufficient ideas to confront them to the requirements. It also included the frequent holding of meetings with the stakeholders in order to validate each steps of the ideation and design process.
A channel of communication was also maintained daily between the in house developers and the UX team in order to ensure design and objectives alignement.
Issues
The previous software was very complex to use and meant duplicating the information into various tables. Due to the secrecy nature of the project, no data was provided and only general work flow. The task was to rethink completely the software to ensure that all requirements were met.
Methodology
The first step was to establish a Customer Journey Map in order to assess all the pain points and touch points of the process. As the application was used as a specific B2B product within very constraining environnement it needed particular attention.
Customer Journey Map on the B2B app
Revisiting the Site Architecture
An analysis was conducted to define the main requirements for this type of software. Typical user flows were extracted from this analysis. In collaboration with the stakeholders, the flows were validated and generic user stories were identified to help with the ideation for the software interaction and design.
Sitemap of the software
Getting the big picture
Once validated, the user flows were translated into simple design. The technical nature of the work meant that very little manipulation was wanted as the technicians usually enter data on their desktop computer while working (dirty hands).
Comparaison between actual and proposed navigation
Innovating the Interaction Design
The main navigation needed to be provide direct access to the 4 possible tasks. As the use of a touchscreen was essential, a minimalistic screen was created.
Comparaison between actual and proposed Interaction
Translating into concrete Design Interface
For data entry, the use of a conventional keyboard was required. Some of the requirements included a notification center, printing, sharing and favorite capacities as well as direct access to various parts of compiling tables and timeframe selection.
Typical table display with search field and other functions