01 SimpleNight · 2023–2024

One promise.Many kindsof travel.One coherentway through.

I led the product experience that connected discovery, comparison, configuration, checkout, and confirmation across a broad travel platform.

Role

Creative Director
Principal product design

Scope

External experience
End-to-end booking

Partners

Executive · Product
Engineering · Design

02 The experience problem

Simple on the surface.Different underneath.

A hotel, a flight, and an activity do not ask travelers to make the same decisions. The product still had to feel like one experience.

01

One entry point

Give travelers a recognizable way to start without hiding the information each category needs.

02

Many decision models

Support rooms, fares, passengers, seats, dates, availability, and policies without creating unrelated products.

03

Continuous confidence

Preserve context, price, selection, and progress from first search through final confirmation.

DiscoverSearchCompareEvaluateConfigurePurchaseConfirm

03 Shared intent · adapted interaction

The experiencestayed coherent.The choreographychanged.

Responsive behavior was part of the product language—not a smaller copy of the desktop interface. Mobile controls focused each decision, preserved state, and returned the traveler to the larger journey.

  • Shared intentDestination, guests, dates, and clear completion.
  • Contextual behaviorFocused sheets, touch targets, range states, and sticky actions.
  • Continuous orientationEvery interaction reconnects to the same search and booking model.

04 Decision support at scale

Results did morethan return inventory.They helped peoplemake tradeoffs.

Travelers needed to compare value, location, quality, availability, and fit—not simply scan a list. I organized those signals around the decision each result had to support.

01

Filter with intent

Price, rating, amenities, and location narrowed the choice without obscuring the available inventory.

02

Rank the signals

Imagery established fit; price, quality, reviews, and availability made the comparison actionable.

03

Support scanning

Consistent card anatomy let travelers compare quickly while alternate layouts supported different shopping modes.

05 Progressive disclosure

Give travelers depth.Keep the next decisionwithin reach.

A hotel detail page carries a lot of evidence. The design revealed rooms, amenities, reviews, policies, location, and recommendations in layers while preserving a clear path back to selection.

Orient

Keep the property, price, and booking path recognizable across a long surface.

Reveal

Let rich media and supporting details expand when the traveler asks for them.

Reconnect

Return each exploration to room selection and the next meaningful action.

06 Checkout as confidence

The final stepshad to feel likecontinuation—nota new experience.

Checkout preserved the selected inventory, total price, trip context, and progress so form completion never felt disconnected from the choice that brought the traveler there.

01

Preserve context

Keep the selected property, dates, guests, and price visible while details are completed.

02

Make progress legible

Use clear completion states, grouped inputs, and action hierarchy to reduce uncertainty.

03

Close the loop

Carry the same booking language through a confirmation that makes the outcome unmistakable.

07 Shared does not mean identical

Standardize the language.Protect what makeseach task different.

Hotels ask travelers to compare properties and rooms. Flights introduce passengers, segments, fares, and spatial seat selection. The common model created continuity without forcing unlike decisions into the same interface.

The design rule

I standardized intent, hierarchy, state, and feedback—then let each inventory type keep the behavior its task required.
SharedProgress · action hierarchy · selection state · pricing continuity
AdaptedPassenger structure · segment logic · spatial seat selection

08 One confirmation language

Different reservations.One clear senseof completion.

A confirmation had to do more than announce success. It needed to organize what was booked, make the next steps obvious, and support a traveler whose trip could contain more than one reservation.

  • ConfirmMake status and completion unmistakable.
  • OrganizeGroup each reservation without fragmenting the trip.
  • PrepareSurface reference details and the actions that follow.

09 The system beneath the journey

The interface languageconnected brand expressionto repeatable behavior.

The reusable layer was not decoration. Navigation, fields, controls, action hierarchy, and states gave teams a common foundation for building distinct booking journeys that still felt related.

10 What changed

A broad promise becamea coherent productexperience.

I led the design of a new external product experience that connected discovery, comparison, configuration, checkout, and confirmation through one recognizable interaction language.

The result was a more consistent and usable foundation for complex booking journeys across categories and devices—without erasing the decisions that made each journey distinct.

01

One journey model

A shared path from discovery through confirmation gave the experience a coherent backbone.

02

Adaptable interaction

Responsive and category-specific behavior preserved intent across different tasks and contexts.

03

Reusable product language

Navigation, inputs, actions, hierarchy, and states connected the brand to repeatable behavior.

The strongest lesson: coherence comes from shared judgment—not identical screens.

Expanded SimpleNight interface