THE PROBLEM:
Craft a diagnostic notification experience for an in-flight navigation application that:
Accurately reflects real-time system performance
Allows for component-level troubleshooting
Provides actionable recommendations that allow for fast resolutions
MY ROLE:
LEAD UX DESIGNER
THE TEAM:
2 DESIGNERS, 2 ENGINEERS, 2 PRODUCT MANAGERS
THE TOOLS:
FIGMA, REACT, PROTOPIE, IPAD MINI
CHALLENGES:
DATA TRANSFER
Security guideline adherence
Resource constraints
Data must be transferred from other platforms
Usable understand intense physical strain (G-Force)
Must provide rapid executable recommendations
OVERVIEW
IN-FLIGHT ERROR NOTIFICATION SYSTEM
ACTION PLAN
USER INTERVIEWS
BUILDING VISION BOARD
AFFINITY MAP
EISENHOWER MATRIX
ASSUMPTIONS *
!
*based on our findings
Users are willing to adopt manual workflows to have an optimal training experience
Our first version of this system will focus on manual data entry and management with long-term system architecture subject to change based on contract
Future iterations may require SD card
data management
1
2
3
PROVIDE ACCURATE TROUBLESHOOTING RECOMMENDATIONS
SOLUTION MUST BE SCALABLE TO INCLUDE FUTURE FEATURES
QUICKLY DIAGNOSE AND RESOLVE PROBLEMS IN UNDER 2 MINUTES
ALLOW FOR A FULL SYSTEM RESET IN UNDER 1 MINUTE
PROVIDE LOGS AND ERROR CODES
VISUALLY INDICATE HEALTH OF COMPONENTS
SEPARATE SOFTWARE AND HARDWARE ELEMENTS
Avoid information overload while providing
EXECUTABLE INSIGHTS
AVOID INCREASING MISSION COMPLEXITY OR TRAINING TIME
pROVIDE EXPERIENCE FOR LESS TECH LITERATE USERS
requirements
must:
nice to haves:
goals
1
2
3
iNTERFACE THAT IS INTUITIVE FOR INTERNAL USERS AND EXTERNAL CLIENTS
Diagnostic interface that visually indicates system health
Rapid troubleshooting ability for users of all skill levels
user flows
Identifying & Diagnosing problems
To better understand what system notifications users would need, we collaborated with the hardware, software, and firmware team to understand what system messages were being sent to the front-end. After a few conversations, we began drafting an error matrix. This established a general Rule set for the notifications/alerts, and dictated severity and color of the relevant UI elements
process:
error matrix
wireframes
Reference and inspiration were taken from the Apple Human Interface Guidelines and the standard iOS control panel. To avoid clutter while allowing for quick access and scaling, Apple implements a flexible controls system that varies what information is present based on the page context and the input of the user. Attention was also given to the Garmin Pilot systems, and their web experiences. Garmin interfaces are common in most modern aircraft.
Users would like additional visual indicators of successful network connection before or
at startup.avoiding covering map and flight data to prioritize safety during flight.
Audience may include back-seat pilots and technicians,who desire a deeper technical understanding. But Front-seat pilots are priority.
key takeaways:
Users were given the application for 30 minutes in a moderated, testing session.
after 10 minutes of exploration, users were asked to complete the following tasks:
Identify which system is failing
Identify a warning notice
Open the troubleshooting options
review/validate
process:
Notification stacking:
When multiple errors occur, but are left unaddressed, They are converted to buttons.
More than 3 urgent level errors are considered a safety of flight risk, and users are transitioned to a captive portal until the concern is addressed.
Visual indicators:
A challenge we faced is when to trigger a captive state, As pilots rely on situational awareness and rapid response to complete their duties.
results
