One Checkout
Expedia’s effort to new checkout experience
One Checkout
It’s Expedia's solution to multi-brand migration. The goal is to create a unified checkout experience for all the brands that Expedia owns.
Contribution
Creating reusable & scalable components and enabling smart input with minimal user efforts (Smart form & Coupon).
My Roles
UX/UI Designer
Legacy form challenge
1
Wrong way of greeting
When greeting the account holder, it is recommended to use their name instead of their login email.
2
Repetitive info (Room amenities)
Reconsider the placement of information playback for room amenities.
3
Lengthy option info
By revealing the optional field, sections such as payment are pushed down on the page.
4
Repetitive form section
It is redundant to have two form sections that serve the same purpose by default.
Data-informed strategy
Priority should be given to designing lodging products due to the low risk and high revenue generation potential
One page template
Data suggests a one-page template is better for Lite Checkout tasks (lodging, rental cars, and single traveler flights) as users prefer having all important info in one place and the ability to double-check details and payment.
Multi-page templates are more suitable for packages and multi-traveler flight bookings, as they help to simplify the lengthy process and reduce cognitive load.
A scalable designs strategy (different Lines of Business)
Car
Lodging (single-room)
Lodging (Multi-room)
Activity
A scalable designs strategy
-Design treatments for specific error cases
A scalable designs strategy
Create affordance for all optional fields
Auto-fill
-For Guest users. Name info will beconnected in the form and payment module.
Auto-fill
-For Login users. The main account holder was selected and auto-populated by default
A Minimal Form
Multi-room bookings now require only one traveler's information.
A subsequent user study indicates that the response from users has been positive.