Home / Search
Single entry point for all booking flows. Hero banner + Flights / Hotels tab toggle.

Enterprise UX case study
Keep travelers moving, keep finance happy. Even when supplier prices spike and travel plans fail.
Client
JPMorgan Chase Travel
Design team
Cybage UX team
My role
UX Designer
Duration
13 months
At a glance
The problem
A business trip is several bookings, each from a different supplier, all under company policy, and often booked for a colleague.
What I owned
Seat selection, the trip cart, checkout for two kinds of booker, policy and exception states, and booking recovery.
What shaped it
Five things the supplier APIs revealed midway. Each one changed part of the flow, and each chapter starts from one.
Where it ended
Approved, partly built, then paused before launch.
One trip can involve several bookings.
JPMorgan Chase Travel already supported air travel and corporate mobility through its own channels. Hotels were spread across outside vendors and offline steps. Proximo was designed to bring flights, hotels and cars into one booking, with Obex supporting the journey after booking.
Flights
Hotels
Cars
One booking
Users
Travel arrangers
Build a whole trip for a colleague, within policy, while prices and availability change underneath them. Chapters 3 to 5.
Travel managers
See which bookings broke policy, and the reason given for each. Chapter 1.
Finance teams
A record of every booking, cancellation and reference they can export. Chapter 6.
Design ownership
I designed the steps where supplier limits and company policy reach the booker: choosing seats, reviewing the cart, paying, and recovering when a supplier fails.
I owned
The UX for seat selection, the trip cart, checkout, policy and exception states, booking recovery and API error handling.
I collaborated on
Flight and hotel search and results, fare and price updates, trip review, policy logic and the information architecture, with the wider Cybage UX team.
What fed the work
Workshops with travel consultants, client reviews, the BA's checks against business rules, policy documents, existing tools, and regular reviews with the API team.
The limit of the evidence
I had no direct access to travellers, and the project paused before launch. So this shows decisions and the cases they cover. Nothing here was measured.
Project timeline · 13 months
Feb 2024
Joined the project
Early exploration
Feature design
Iterations as the APIs changed
Mar 2025
Project paused
Sitemap
Search, the trip cart, checkout, confirmation, trips and profile, with policy running across every step.
How it fits together
I mapped the journey so the team could see where each rule and each failure appeared.
The cart sits in the middle. After adding a flight, people add a hotel or a car from the cart itself, so the trip is built in one place and checked once before payment.
User flow
The main booking path. Its two decisions: is the fare in policy, and who is booking. The bands show where each constraint applies.
End to end
Every screen in order, from searching for a flight to the booking confirmation.
This is the main path most bookings follow. The chapters below cover the places where it branches.
What changed the design
We started from a tidy picture of the backend. As the API team connected each supplier, five assumptions broke.
Each one changed the design, and each chapter that follows starts from one of them. Other changes came from client reviews and the BA's checks against business rules.
Chapter 1 · Choosing a flight
If policy only appears at checkout, people find out about a problem after they have built the trip around it.
So I carried policy through four points of the journey: in results, when choosing a fare, in the cart, and at checkout.
Started from assumption 01
Owned: policy states · Shared: flight results
1 · In results
Each fare shows its policy status before it is opened. An In Policy filter narrows the list.
2 · On choosing
Choosing an out-of-policy fare opens an alert, and the booker can still continue.
3 · In the cart
The policy tag stays with the item, so the exception is still visible when the trip is reviewed.
4 · At checkout
A reason is required for each out-of-policy flight, hotel and car before booking.
Revised alert
The first alert only asked whether the booker was sure. The revised one names the item, lists why it is out of policy, and says a business justification will be asked for at checkout, so nothing there comes as a surprise.
01 · Flights
02 · Hotels
The same alert, with the hotel's reasons: the nightly rate, the booking area and preferred vendors.
03 · Cars
The same alert, with the car's reasons: the vehicle class, the daily rate and optional upgrades.
In the build
A capture from the development build. The All / In Policy toggle sits above the results, so the list can be narrowed before any fare is opened.
The business team clarified late that a restricted fare and a policy exception are different things. Mixing them up would have blocked bookings that were allowed.
A detail
Flight data came from several sources, and they didn't all send the same fields. Details such as CO₂ or the operating airline appear only when the source returns them, and the card keeps its layout either way.
Chapter 2 · Choosing seats
The cart holds one flight itinerary at a time, so a multi-city trip reaches seat selection as a single booking, sometimes with six legs or more.
Legs can differ in aircraft and seat prices, and some have no seat map. The interaction had to stay the same whether someone picked seats for one leg or for many.
Started from assumption 02
Owned: seat selection
One-way trips. Round trips sold as one package or as two separate flights. Multi-city trips of up to five legs, and of six or more. A trip where a flight is already in the cart.
Opened from
Flight summary
Proceed to Select Seat
Flight results
Choose This Flight
Trip cart
Select Seat, per segment
A tab for each leg, whatever the trip
One-way
one tab
Round trip
package or 2 flights
Multi-city
up to 5 legs, all shown
Multi-city
6 or more legs, arrows
What a leg tab can show
Six explorations, grouped by the question each one answered. The real order wasn't recorded.
Question 1 · Where does seat choice live?
Inside fare selection
Choosing a fare and choosing a seat blurred together, and the page grew very long. Seats became their own step after the fare.
Question 2 · How much aircraft to draw?
Aircraft silhouette
The outline took space without telling people anything. The final uses a plain grid with wing and exit markers.
Question 3 · How do people move between legs?
Dropdown
The list of legs covered the seat map while switching.
Vertical list
Every leg stayed visible, but the list took width from the map.
Horizontal strip
The map got its width back, but leg details became too small to read.
Leg tabs. Kept.
Each tab shows its leg's seat status. Up to five tabs fit; from six legs, arrows bring in the rest.
Final design
Leg tabs across the top, a plain seat grid, and a flight total with a line for every leg. A tooltip gives the seat, cabin and price per passenger.
In the build
A capture from the staging build on a five-leg trip. The leg tabs and the plain seat grid carried through into the working product.
When the airline can't help
The seat map couldn't be loaded for this leg.
This airline only allows seat choice after booking.
Starting a second flight when one is already in the cart.
Chapter 3 · Building the trip
Each item in the cart has its own supplier, price rules and hold time.
The arranger still needs to review the whole trip, and change any part of it, before paying.
Started from assumptions 03 and 04
Owned: trip cart · Shared: price updates
The brief
The brief asked for one place to review every service and its price, edit the trip before confirming, and leave with a confirmation number and itinerary.
I turned it into a board the client could react to before any flow existed. The items in red, such as promo codes, booking deadlines and a chatbot, were open questions for the client to decide.
The brief called this stage Checkout and Confirmation. Most of what it asked for became the cart, so the board was where the cart started.
One-way, round-trip and multi-city flights, several hotels and cars in one trip, adding and removing any item, clearing the cart or starting over, and a price summary that changes with the trip type.
Comes in from
Seat map
Add to Trip
Hotel details
Choose This Room
Car listing
Choose Car
One-way, round trip (package or 2 flights), multi-city
One or several, in date order
One or several
Five explorations, grouped by the question each one answered.
Question 1 · How much detail per item?
Detailed cards
Full flight cards with amenity chips filled the screen and pushed hotels and cars out of view.
Compact rows
Shorter items, with prompts to add whatever the trip was missing. Each leg was still priced on its own.
Question 2 · How is a trip with several products organised?
Grouped panels
Grouping by product made the itemised summary very long.
One row per item. Kept.
Easy to scan, with price changes shown on the row that changed.
Question 3 · How is a round trip priced?
One package price
Some sources price a round trip as one package. Others price each leg on its own. Picking one model would have broken the other, so the final cart and price summary handle both.
Final design
Flights, hotels and cars as rows, each with Remove and View More. One item is shown expanded with its photo, details and rules.
The empty cart points back to adding a trip.
Clearing the cart asks first.
Chapter 4 · Checkout
Many business trips are booked by a travel arranger, not by the person travelling.
Both go through the same two steps: confirm who is travelling, then choose a corporate card and accept the travel policies. Book now stays off until both are done. What changes is what can go wrong at each step.
Started from client review
Owned: checkout for both bookers
Traveller
Only corporate cards are accepted, so the flow covers a card that can't be found, a card that has expired, and choosing another card from the saved list.
Travel arranger
Starts by searching the company's travellers, with loading, matches and no-results states. Only one traveller is booked per checkout.
What the arranger has to resolve
Missing profile details
The missing fields are named, an Update Profile link appears, and Continue stays off until they're fixed.
Someone else's card
For an arranger, the message says it is the traveller's card that has expired, not their own.
Chapter 5 · Booking
We first assumed a booking would succeed or fail as a whole. In practice the flight books first, then the hotel, then the car, and each supplier can fail on its own.
By the time a hotel fails, the flight already has a ticket. Telling the arranger "booking failed" would have been wrong: they could book their colleague a second, duplicate flight. This was the biggest change to the design.
Owned: booking recovery and API error handling
Book Now
at checkout
Book the flight
a ticket is issued
Book the hotel
after the flight
Book the car
after the hotel
Trip booked
a reference for each item
The flight fails
Nothing is booked, so there is nothing to undo
The hotel fails
The booked flight is kept
The car fails
The booked flight and hotel are kept
The booking runs in order, and each failure says what is already booked and what to try next.
01
Nothing is booked, so there is nothing to undo. The message says so and offers to try again.
02
The flight is already booked. The message says so, and the hotel can be booked again on its own.
03
The flight and hotel are booked. Only the car needs another try.
The rule for every message
Not designed: what the arranger sees if they leave before retrying. It's the first gap I'd close.
Prices are only confirmed at booking. If one changes during checkout, a message appears and the changed item shows its old and new price, with a link back to the cart.
From assumption 04
Chapter 6 · After booking
Once a trip is booked, a traveller wants to know what happens when, and what can still change.
Arrangers and finance teams also need a record of it. Trip details can be read by product or by day, each item can be cancelled on its own, and the list exports to CSV.
Shared work with the Cybage UX team
One confirmation for the whole trip
Trip, traveller and payment details in one place, with a booking reference for each item.
All trips, by traveller and date
Upcoming and past trips, with status and export to CSV.
Cancel one item, keep the rest
Cancelled items stay on the page, marked as cancelled, so the record still shows what was dropped.
Design decisions
Each chapter solved one screen. These four apply across several of them, and the map shows where each one lands in the journey.
Outcome and reflection
Design output
Approved designs from search to trip management
One cart for flights, hotels and cars, policy at four points, checkout for two kinds of booker, and a recovery model for partial bookings.
Project outcome
Partly built, then paused
Seat selection, multi-city search and the In Policy filter were running in the development and staging builds.
What the team shipped in design
12
Pages
105
Page states
21
Pop-ups
78
In flows I owned
126 distinct screens, counted from the final design files. The 78 are seat selection, the trip cart, checkout for both bookers, booking recovery and the policy alerts.
What I'd do earlier next time
Here they arrived midway, and one of them meant restructuring booking into three outcomes. Next time I would list what each supplier can and can't do at the start, and review that list alongside the designs.
What I would test first
With travel arrangers, at the moments where a decision matters.
01
Seats across several legs
Can they tell which legs still need seats, and what those seats add?
02
A changed price
Can they find the item that changed and decide whether to continue?
03
A partial failure
Can they see what is already booked and finish the rest without booking anything twice?