Enterprise UX case study

Proximo

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.

Context

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

Where a trip can go wrong

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

The product at a glance

Search, the trip cart, checkout, confirmation, trips and profile, with policy running across every step.

Sitemap
Areas, the pages in them, and the sections inside each page
ProximoCorporate travel booking
1.0
Search
1.1Flight booking
1.1.1Flight results
Filters
Flight details
Fare selection
Seat map preview
1.1.2Flight summary
1.1.3Seat selection
1.4Rails Later phase
1.2Hotel booking
1.2.1Hotel listing
1.2.2Hotel details
Overview
Amenities
Rooms
1.3Car booking
1.3.1Car listing
Pickup and drop-off
Vehicle results
Vehicle details
Add-ons
2.0
Trip cart
Flights
Hotels
Cars
Trip summary
3.0
Traveller and payment
Traveller information
Payment method
Review and book
4.0
Booking confirmation
Confirmation header
Booked items
Payment summary
Traveller details
PNRs
Documents
5.0
Trips
5.1Trips listing
5.2Trip detail
Flights
Hotels
Cars
Documents
Payment summary
6.0
Profile
Personal information
Traveller preferences
Saved payment methods
Loyalty programmes
Policy governance
Applies to every area
In policy and out of policy indicatorsPolicy alerts and justificationsCompliance score and messaging

How it fits together

The journey, with the cart in the middle

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

01Discover02Select03Assemble04Checkout05Book06ManageAdd a hotel or a car from the cart01Search02Choose a flight03Pick seatsHUB04Trip cart05Traveller06Payment07Booked08Manage the tripFlight, hotel orcarOne-way, roundtrip or multi-cityPolicy tag onevery fareIn policy?Yes: selectitNo: confirm,then continueOne tab per legSeat fees shownper legFlights, hotelsand cars in onelistChecked oncebefore payingWho is booking?Traveller:own profileArranger:picks acolleagueCorporate cardReason for anyout-of-policy itemAccept policies,then Book nowFlight, hotel andcar booked inorderOne reference peritemTrips by travellerand dateDetail by categoryor by dateWHERE EACH CONSTRAINT APPLIESPolicyTagged on the fare, justified at payment.02 Choose a flight06 PaymentPrices and availabilityFares, seats and rooms can change or be missing until the booking goes through.02 Choose a flight07 BookedRecoveryOnly the failed item is retried.07 Booked08 Manage the trip

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

One trip, start to finish

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.

Home and searchScreen 1 of 10
Home page with the search form and recent searches
Where a trip starts
One search form for flights, hotels and cars. Recent searches sit underneath, so a trip can be picked up where it was left.
1. One search pattern
Flights, hotels and cars use the same form, so switching between them takes no relearning.
2. Recent searches
Earlier searches stay on the page, so a trip doesn't have to be typed in again.

What changed the design

Five assumptions that turned out to be wrong

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.

TopicWe assumedWhat the API revealedHow the design changedChapter
01Policy
Policy is in or out.
Some fares are restricted and can't be booked at all. Others break policy but can still be booked with a reason.
Two treatments: blocked, or allowed with a reason at checkout.
Ch 1
02Seat maps
Every flight has a seat map.
Some suppliers send no seat map. Some airlines only allow seat choice after booking.
Two fallback states. Booking continues without a seat map.
Ch 2
03Fares
A round trip has one price.
Some sources price each leg separately.
The cart and summary handle both package and per-leg pricing.
Ch 3
04Prices
Cart prices hold until payment.
Prices are only confirmed at the moment of booking.
A price check at checkout, with the old and new price on the item that changed.
Ch 3, 5
05Booking
A booking succeeds or fails as a whole.
Flight, hotel and car book in order, and each can fail on its own.
Three recovery outcomes, each with its own message.
Ch 5

Chapter 1 · Choosing a flight

Policy shows up where the choice is made

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

Flight results with policy status tags and the In Policy filter

1 · In results

Each fare shows its policy status before it is opened. An In Policy filter narrows the list.

Confirmation shown when choosing an out-of-policy fare

2 · On choosing

Choosing an out-of-policy fare opens an alert, and the booker can still continue.

Trip cart item keeping its out-of-policy tag

3 · In the cart

The policy tag stays with the item, so the exception is still visible when the trip is reviewed.

Checkout asking for a reason for each out-of-policy item

4 · At checkout

A reason is required for each out-of-policy flight, hotel and car before booking.

Revised alert

One alert for flights, hotels and cars

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.

Revised out-of-policy alert for a flight, with the reasons it is out of policy

01 · Flights

The same out-of-policy alert for a hotel, with the hotel's reasons

02 · Hotels

The same alert, with the hotel's reasons: the nightly rate, the booking area and preferred vendors.

The same out-of-policy alert for a rental car, with the car's reasons

03 · Cars

The same alert, with the car's reasons: the vehicle class, the daily rate and optional upgrades.

In the build

The In Policy filter, built

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.

Multi-city search in the development build with the In Policy toggle

Three questions, kept separate

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.

In policy?Out of PolicyCan still be booked. The booker confirms the choice and gives a reason at checkout.
Bookable?RestrictedCan't be selected. The fare is shown so people understand why, but the action is off.
Still there?UnavailableThe fare has gone since the search. The booker searches again.

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

One seat map, from a one-way flight to a multi-city trip

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

Trip structures it had to handle

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.

Diagram · Seat map
Pagegoes to another pageAsks firstconfirmation first

Opened from

Flight summary

Proceed to Select Seat

Flight results

Choose This Flight

Trip cart

Select Seat, per segment

Seat mapOne layout

A tab for each leg, whatever the trip

One-way

one tab

Leg 1Selected

Round trip

package or 2 flights

OutboundSelected
ReturnSelect Seat

Multi-city

up to 5 legs, all shown

Leg 1Selected
Leg 2Selected
Leg 3Select Seat
Leg 4Select Seat
Leg 5Select Seat

Multi-city

6 or more legs, arrows

Leg 1Selected
Leg 2Select Seat
Leg 3Select Seat
Leg 4Select Seat
Leg 5Select Seat

What a leg tab can show

Select Seatnothing chosen yet
Selected · 19Eseat shown on the tab
No seat mapa message for that leg
Airline-managedseats chosen after booking
Seat tooltipFree Seat+$37.00 Per Passengerand the flight total adds each leg's seat cost
Add to TripTrip cart
Asks firstif the cart already has a flight
BackFlight summary

How the seat map evolved

Six explorations, grouped by the question each one answered. The real order wasn't recorded.

Question 1 · Where does seat choice live?

Iteration: seat map inside fare selection

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?

Iteration: aircraft silhouette seat map

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?

Iteration: legs in a dropdown

Dropdown

The list of legs covered the seat map while switching.

Iteration: vertical leg list

Vertical list

Every leg stayed visible, but the list took width from the map.

Iteration: horizontal leg strip

Horizontal strip

The map got its width back, but leg details became too small to read.

Iteration kept: leg tabs with running cost

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

The final seat map

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.

Final seat map with leg tabs, seat grid and flight total
Decision 01Progress per legEach tab shows whether that leg's seats are chosen, so people see what is done and what is left.
Decision 02Cost per legThe flight total lists every leg with its seat fee, before anything goes into the cart.
Decision 03Not colour alonePaid seats show a $ and unavailable seats an ×. Early versions relied on colour, which some people can't tell apart.
Decision 04Seats stay optionalIf a seat map is missing, booking continues. Where the airline requires it, seats are chosen after booking.

In the build

Running in staging

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.

Seat map running in the staging build

When the airline can't help

Seat map unavailable for a leg

The seat map couldn't be loaded for this leg.

Airline that allows seat choice only after booking

This airline only allows seat choice after booking.

Alert when a flight is already in the cart

Starting a second flight when one is already in the cart.

Chapter 3 · Building the trip

A cart that reads as one 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

I started by making the brief visible

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.

Requirements board from the brief's checkout and confirmation section, mostly covering the cart

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.

What the cart had to handle

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.

Diagram · Trip cart
Pagegoes to another pageAsks firstconfirmation first

Comes in from

Seat map

Add to Trip

Hotel details

Choose This Room

Car listing

Choose Car

Trip cartHubNav badge none29+
Flights

One-way, round trip (package or 2 flights), multi-city

  • View More
    itinerary and layovers
  • Select SeatSeat map
    per segment
  • Start OverAsks firstHome
    flights only
Hotels

One or several, in date order

  • Add HotelHotel listing
  • View More
    photos, room, amenities
  • Rules and Policies
    pop-up
  • RemoveAsks first
Cars

One or several

  • Add Car
    when the trip has none
  • View More
    specs, pick-up and drop-off
  • RemoveAsks first
Payment summary layoutsPackaged round tripRound trip as 2 flightsEverything else, per item
Proceed to CheckoutPayment
Traveller and payment details
Clear Cart
Asks firstthen the empty cart

How the cart evolved

Five explorations, grouped by the question each one answered.

Question 1 · How much detail per item?

Cart iteration: detailed flight cards

Detailed cards

Full flight cards with amenity chips filled the screen and pushed hotels and cars out of view.

Cart iteration: compact rows with add hotel and car

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?

Cart iteration: grouped panels per product

Grouped panels

Grouping by product made the itemised summary very long.

Cart iteration kept: table rows with price alerts

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?

Cart iteration: round trip as one package price

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

The final trip cart

Flights, hotels and cars as rows, each with Remove and View More. One item is shown expanded with its photo, details and rules.

Final trip cart with flights, hotels and cars
Decision 01Details on demandOne row per item. Details open in place, so the trip stays readable at a glance.
Decision 02What's missingAdd Hotel and Add Car appear for whatever the trip doesn't have yet.
Decision 03Changed pricesA banner on the changed row shows the old and new price, so nobody has to compare the whole summary.
Decision 04Ask firstRemoving an item, clearing the cart and starting over all confirm before acting.
Empty trip cart

The empty cart points back to adding a trip.

Confirmation before clearing the cart

Clearing the cart asks first.

Chapter 4 · Checkout

Two kinds of booker, one 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

Books for themselves

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.

Traveller checkout with policies accepted

Travel arranger

Books for a colleague

Starts by searching the company's travellers, with loading, matches and no-results states. Only one traveller is booked per checkout.

Travel arranger searching for a traveller

What the arranger has to resolve

Arranger checkout flagging missing profile details

Missing profile details

The missing fields are named, an Update Profile link appears, and Continue stays off until they're fixed.

Arranger checkout flagging an expired corporate card

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

When a booking only partly succeeds

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.

Started from assumption 05

Owned: booking recovery and API error handling

Diagram · Booking
main pathfails
Checkout

Book Now

at checkout

Step 1

Book the flight

a ticket is issued

Step 2

Book the hotel

after the flight

Step 3

Book the car

after the hotel

Done

Trip booked

a reference for each item

The flight fails

Flight failedHotel not bookedCar not booked

Nothing is booked, so there is nothing to undo

Try Book Now again

The hotel fails

Flight bookedHotel failed

The booked flight is kept

Book the hotel again on its own

The car fails

Flight bookedHotel bookedCar failed

The booked flight and hotel are kept

Try the car again

The booking runs in order, and each failure says what is already booked and what to try next.

01

The flight fails

Nothing is booked, so there is nothing to undo. The message says so and offers to try again.

Flight booking fails

02

The hotel fails

The flight is already booked. The message says so, and the hotel can be booked again on its own.

Flight booked, hotel booking fails

03

The car fails

The flight and hotel are booked. Only the car needs another try.

Flight and hotel booked, car booking fails

The rule for every message

Say what is booked, what failed, and what to do next.

Not designed: what the arranger sees if they leave before retrying. It's the first gap I'd close.

Prices can still move at the last step

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

Price change banners at the last step

Chapter 6 · After booking

The trip stays readable and changeable

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

Booking confirmation for the whole trip

One confirmation for the whole trip

Trip, traveller and payment details in one place, with a booking reference for each item.

Trips listing by traveller and date

All trips, by traveller and date

Upcoming and past trips, with status and export to CSV.

Cancelling one item of a trip

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

Four decisions that run across the product

Each chapter solved one screen. These four apply across several of them, and the map shows where each one lands in the journey.

Where each decision landsHover a decision to see the moment it handles
Policy
Seats
Price changes
Partial failure
DiscoverSelectAssembleCheckoutBookManage
01Select → Checkout
Policy at four pointsRestricted fares can't be chosen. Out-of-policy fares can, with a reason at checkout.
Every fare within policy
In policySelect
In policySelect
What if a fare breaks policy?
02Select → Manage
Seats stay optionalSome flights have no seat map, and some airlines only allow seats after booking. Either way, the booking continues.
Airline sends a seat map
Seat map
unavailable
SeatRow 2 · Seat C
ContinueStill bookable
What if there's no seat map?
03Assemble → Checkout
Changes stay on the itemWhen a price changes, only the item that changed shows its old and new price. The rest of the trip is untouched.
Cart prices match the search
$486
Price updated$212$236
$94
What if a price changes before payment?
04Book → Manage
Each booking can fail aloneFlight, hotel and car book in order. Every message says what is booked and what isn't, so the arranger retries only what failed.
Flight, hotel and car all confirm
Flight Booked
Hotel Booked
Car Booked
What if one item fails to book?

Outcome and reflection

What the work delivered

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

Bring supplier limits into the design from the start

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?

Create a free website with Framer, the website builder loved by startups, designers and agencies.