

Role
UX and UI Designer
Timeline
January 2026-March 2026
Tools/Lanuguages
Figma
Problem
Process
Product
Ordering from the screen
Seatback ordering is a two-sided transaction that Delta is building for the first-class customers. Another team designed the passenger-facing experience, but the need was the flight attendant experience to be built out and work seamlessly with the seatback application.

FAs have always taken first-class orders, but it's always been a human, verbal exchange
The design had to feel familiar enough to earn FA trust, but structured enough to capture everything a natural conversation absorbs
Needed to be future proof for all cabins
The Busy Schedule of a Flight Attendant
In the initial phase of this project, I was able to speak to a handful of flight attendants and understand their usage of the MyFlight app and their general behaviors while on duty. This shaped my strategy designing the ordering feature to fit cleanly into their ecosystem.
Designing for flight attendants meant designing for one of the most demanding and diverse user groups I have worked with. The demographic spans a wide range of technical comfort levels, and as a group they are notoriously resistant to new processes.

The first set of wireframes/low-fi screens I created were based off the simple set of requirements given. This led to designs created off the assumption that ordering is a linear process with little flexibility for changes needed from FAs.
As I moved through iterations and design critiques with the team, I kept surfacing questions about the FA service experience that the designs couldn't yet answer. It became clear that the assumptions the team was working from were shifting with every session. Rather than continuing to design around a moving target, I guided the team to pause and invest in a proper discovery before going further.

Non-Linear Ordering System Realized
Assumption
Ordering is a linear flow similar to restaurant ordering- passenger orders, FA receives, FA delivers

The service design blueprint was created to assist myself and the team for future proofing the product. I wanted to align with the stakeholders and other teams on how all the aspects of ordering "talked" to each other and where MyFlight could fill in the gaps for flight attendants.

Using the workshop output and the service blueprint, I altered the process map to create a comprehensive story that captured what was previously thought of as edge cases, now in the happy path itself.
FAs needed to decline, not just accept, and for multiple reasons that each required a different system response
More information upfront reduced errors downstream, not the other way around
Actions could happen at the order level and the item level, not just at the moment of acceptance

Discovery Proving Designs Wrong
After discovery, I went back to old designs realizing how the assumptions were challenged and designs didn't work for the service design the team and I had mapped out.


UX navigation changes were put into place to help FAs have flexibility in their tasks and personalize their experience based on where in the service journey they are.

Want to see more?






