Booking.com

Back

Payments, and the team that designs them — a vision for how travellers pay across a whole trip, and the principles and rituals the department works by.

Years
2023 - Present
Roles
UX Design Lead, FinTech
A wall of payment-method logos, row after row: Visa, PayPal, Apple Pay, Google Pay, iDeal, Venmo, Klarna, Bancontact, Alipay, Affirm, Trustly, BLIK, LINE Pay and dozens more, each in its own bordered tile with its name beneath.

Overview

Four strands of work at Booking.com: leading a payments design team, the strategy behind it, the vision projects that set its direction, and the hands-on work.

Underlined are some of my highlights.

Leadership

Strategy

Hands-on

  • Instalments explorations
  • DSA Dark pattern scan
  • EAA Accessibility readiness
  • Easy Getaways - AI Trip planning hackathon winner

Project one

Connected Trip Payments Vision

How travellers budget, pay, use loyalty and manage transactions across a whole trip — drawn end to end.

Four travellers down the left - Family, Couple, Solo business and Solo - each introduced by a card with their trip context, needs and products. Beside each one its scenario boards: plan, search, book and pay, and in-trip for the family; search and book and pay for the couple; three trip-management scenarios for the solo business traveller; book and pay and in-trip for the solo traveller. Each board is a row of annotated screens over coloured phase bands.
Four travellers, four journeys: every phase from planning to in-trip, drawn as one continuous board.

The challenge

Align our work with the overarching Booking.com Connected Trip product vision by illustrating the core customer experiences for travellers: how they budget, pay, use loyalty and manage transactions, in a seamless way and addressing current pain points. All of it aimed at inspiring and aligning everyone towards a clear, shared path forward.

Scenarios were written for 4 distinct traveller types, then drawn phase by phase — plan, search, book and pay, and in-trip — so the payment moments could be seen where they actually fall rather than as a checkout in isolation.

Project two

Team principles and review ritual

How a design department gives each other feedback, and the weekly hour where design, writing and research do it together.

The challenge

Refresh our collaboration principles and rituals based on input from the UX community, and align them with leadership goals for collaboration and quality. Bring in clear purpose, improved structure and a more engaging schedule — and raise the level of the work at the same time.

The 6 principles

We are open for feedback. We actively listen and stay open to discussion; feedback is never personal. We share early and often. The tone of our meetings stays light and informal — a safe space without judgment, mindful of the phase the project is in.

We review and present our work in a few circles. First a small circle: one to one with your closest collaborator, a UX writer, designer or lead. Then a bigger one: a craft ritual, followed by the cross-craft PayJam. Going from smaller circles to bigger ones, the work can only get better.

We review from start to finish. Every stage benefits from other perspectives — from before anything exists to after the product is live and wants evaluating. Four phases to review in: the problem and the why, early concepts, getting ready for handover, and results and next iterations.

We unblock each other. We don’t block anybody in their design journey; the mission is the opposite. We aim to be solution centric rather than problem centric, always offering options for moving forward faster and better.

We follow up and follow through. Every piece of feedback is treated as a to-do: captured, considered, and implemented where it can be. It goes straight into Figma so it can be tracked, and the status comes back in the channel or at the next PayJam.

We prepare well and set expectations. Presenters give the context the stage calls for and a clear ask — what kind of feedback is wanted right now. Reviewers answer in kind: no critique of visual design or copy while a concept is still forming, and no reopening the problem statement when the work is nearly ready for handover.

The ritual

A weekly hour where design, writing and research come together to do four things. Review: critique from each craft’s perspective, constructively and informally. Co-create: put collective brain power into making something from nothing — a brainstorm early in a project, with the organiser collecting, refining and bringing the ideas back. Learn: sessions that go deep on a topic or a skill, drawn from the work already reviewed together. Have fun: dry runs, new ideation techniques, redesigning our own workflows.

The presenter gets broader perspectives and no blind spots, and the level of their work rises. The participant gets a better overview and a way to make an impact outside their own scope. Both of them learn.

The full story, with the principles as they were first written and the practicalities that hold the ritual together, is an article of its own.

Project three

Continuous improvement of the payment experience

Uncovering and tackling the checkout issues and opportunities

The audit board behind the initiative: six long rows of screens, each row headed by its own coloured label card and covering one platform or flow - desktop web, mobile web and the apps - with hundreds of annotated screens and red, orange and yellow markers pinned to the places where something goes wrong.
The audit underneath it: every platform, every flow, every issue marked where it happens.

We initiated the UX Issues & Opportunities initiative to address the accumulation of small usability issues that collectively create significant friction, leading to customer churn, while also providing the organisation with the visibility, prioritisation framework, and experimentation methods needed to measure and track the impact of UX improvements effectively.

More than a simple audit, this initiative aimed to create a comprehensive understanding of the user experience across all touchpoints. After the initial scan, we set up processes to continuously identify, filter and fix the identified issues. The 170+ issues will go through a structured resolution process in 2027 and beyond.

More work