Project Process
Starting point
The existing alert interface was outdated and over-engineered. The options presented didn't always make sense to first time users, but customizing your notification had unnecessary steps and felt like you may be breaking it altogether. User confidence in alerts was low.
Using personas as our guide
I reviewed our user persons with stakeholders and developers and together we were able to identify which alert settings were best for the three key scenarios.
The Traveler Alert Settings:
You want to know when you'll actually depart.
The Ride Alert Settings:
You're picking someone up and want to know when they'll arrive.
The Operator Alert Settings:
You're need updates on the full flight, from takeoff to landing.
Simplified flight alerts
The answer was right in front of us. By adding a step at where users could select which scenario they needed an alert for, we could properly customize the alert for them and they could feel confident in the options presented.
The new design presented the information clearly and followed common UI patterns so users would feel more comfortable interacting with it should they choose to modify their settings.
