Web ·
Delta ·
2025-26
Standby List
Designed TravelNet, an internal web app at Delta that helps employees book flights, manage standby travel, and navigate the employee travel experience.
Company
Delta
Role
Lead product designer
Team
A product manager, 3 engineers, and QA tester
Year
2025-26
Duration
4-5 months
Platform
Web
Context
The existing Standby List experience presented a lot of information in a single view, making the interface feel crowded. The opportunity was to simplify the experience by separating employees’ personal standby information from the broader airport list.
Working with my product manager, I explored how the information could be organized into two distinct views, making it easier for employees to focus on the information most relevant to their travel.
My role
I led the design exploration and UI development for the Standby List experience, collaborating with my product manager to evaluate the existing interface, explore solutions, and align on the proposed direction.
I also used Kiro to turn my designs into a functional prototype, helping communicate interaction behavior and translate the design into clearer requirements for engineering.
Approach
I approached the problem by focusing on three priorities:
1. Simplify the existing interface
I reviewed the existing interface to identify opportunities to reduce clutter and improve the information hierarchy. In collaboration with my product manager, I explored potential features and ways to reorganize the experience using Delta’s MACH 1 design system.
2. Separate personal and airport standby views
I explored a direction that separated the experience into two views: a Non-Rev List focused on an employee’s position and an Airport List providing a more comprehensive view of the standby list. This helped distinguish personal standby information from the broader airport standby list.
3. Bring the designs to life with a functional prototype
After aligning on the initial designs with my product manager, I used Kiro to build a functional prototype. This allowed me to explore interaction behavior, test layout constraints, and demonstrate how the experience could work beyond static screens.
Old TravelNet Experience
Solution
The proposed solution introduced two distinct views tailored to different information needs.
Non-Rev List: A focused view that helps employees understand their position on the standby list without the additional information associated with other passengers.
Airport List: A broader view that provides a more comprehensive look at the airport standby list.
Using a functional prototype, I demonstrated the intended layout, interactions, and behavior to my product manager and engineering partners. This gave the team a tangible reference for evaluating the design and understanding what needed to be implemented.
Result
After Standby List launched in March 2026, and we got a good read on how employees felt about the new experience.
4.29 out of 5 satisfaction score (145 responses). Employees liked the new TravelNet experience. Splitting the Non-Rev List from the Airport List meant they could see where they stand without digging through everyone else’s info.
89% of employees agree TravelNet lets them complete tasks quickly. This was the main goal. Cut the clutter so people can get in, check their standby info, and get out.
94% are excited about new features in TravelNet. People want to see where the app goes next, which is a good sign for what we build from here.
What I learned
Building functional prototypes with AI-assisted coding gave me a more practical way to evaluate my designs and communicate design intent. It helped me consider implementation constraints earlier, explore interaction details more concretely, and give engineers a clearer reference for translating designs into a working product.
It also reinforced the value of bringing design and development closer together, especially when working in a fast-moving Agile environment.