☰

Queens Hotels Booking System

A UX project focused on developing a new booking system, aimed at creating a seamless, user-friendly experience from search to payment.

Queens Hotels London


Scenario

Design a new booking system for Queen’s Hotels London, a small boutique hotel chain. The final outcome is a high-fidelity prototype, fully prepared for handover to the development team. The project covered the following stages:

  • Research
  • Analysis
  • Concept development
  • Final design development

Stage one: research

The project began by analysing websites from similar businesses, major hotel chains, and non-hotel companies with comparable booking systems. A diverse group of volunteers was then recruited. They completed booking tasks with minimal guidance, ensuring the collection of unbiased data about their natural behavior. This allowed for the gathering of information on:

  • The primary goals of the user
  • Secondary and tertiary goals
  • How the user achieves their goals
  • Behaviours
  • Context of use
  • Pain points
  • Product desirability and functionality

Key UX Insights

Observations on What Works Well

  • Simple and clean. Minimal branding, clutter-free layouts, and no unnecessary scrolling
  • Clear choices. Visual hierarchy clearly highlights main vs. secondary options
  • Upfront details. Amenities, key info, and next steps are instantly visible
  • Fast process. Minimal steps and pages to complete a booking

Key Pain Points Identifed

  • Cluttered and Wordy. Too much text, long paragraphs, and unnecessary filler content
  • Hidden costs. Total price isn't shown until late in the process
  • Awkward controls. Separate arrival/departure calendars and hard-to-click room links
  • Confusing layouts. Too much scrolling, dead-end links, and duplicate buttons for a single action
Notes made for the Hilton Hotel group website home page

Notes made for the Hilton Hotel group website home page

Notes made for the Hilton Hotel group room selection page

Notes made for the Hilton Hotel group room selection page

Notes made for the Hilton Hotel group room information page

Notes made for the Hilton Hotel group room information page

Notes made for the Annabelle Hotel room information page

Notes made for the Annabelle Hotel room information page

Notes made for the Queens Hotel homepage

Notes made for the Queens Hotel exsisting homepage

Notes made for the Queens Hotel room information homepage

Notes made for the Queens Hotel room information homepage

Notes made for the London Eye homepage

Notes made for the London Eye homepage

Notes made for the London Eye booking page

Notes made for the London Eye booking page


Stage two: analysis

Affinity Diagram

Each observation was recorded as a single digital post-it note in FigJam, creating dozens of individual insights. Simple thumbs-up and thumbs-down icons were used to show whether an experience was positive or negative.

Figjam file with the gathered notes prior to sorting



Grouping the notes by theme began to reveal key patterns, major pain points, and feature priorities across the user experience. The resulting categories covered search issues, booking stages, unnecessary features, and two general feedback groups titled "Nice and Simple" and "Would Have Been Nice if…," reflecting participants' exact words.

Figjam file with the notes sorted into groups



Customer Journey Map

The affinity diagram results were used to map the user journey throughout the booking process. Each stage was clearly defined and separated. Insights for each stage were documented and organised into seven key areas:

  • Goals
  • Context of Use
  • Mental Modes
  • Behaviours
  • Pain points
  • Positives
  • User Quotes


The positive and negative points for each of the seven key areas were used to create a timeline illustrating user emotions throughout the booking process. These are shown in the completed customer journey map below.

The completed customer journey map



Focused Key UX Insights

Three stages of the booking process yielded more negative emotions than positive. These were: Search/Date Input, Room Selection and Add-ons. These pain points became the primary focus for the website redesign, which aimed to preserve existing positive interactions while eliminating friction.

The list below outlines key positive features and pain points that served as a crucial reference during the design process.

What's Working Well - Pros

  • Intuitive Search and Flow. Simple, uncluttered layouts make searching and finding next steps straightforward
  • Integrated Maps. Map inclusion gives users helpful geographical context early on
  • Visual Room Insights. Photos and dimensions make room sizes and types easy to evaluate
  • Low-Pressure Upsells. Add-ons appear at the expected time with clear descriptions and no hard-sell tactics

Key Pain Points - Cons

  • Difficult Comparisons. Comparing available hotels, room types, and rates is challenging
  • Pricing Lack of Transparency. Total costs are hidden upfront, and child discounts are unclear
  • Rate Confusion. Presenting multiple rates per room confuses users during room selection
  • Phantom Availability. Search results display rooms that are actually unavailable for selected dates
  • Map Disconnect. Users are unsure if search results directly match the displayed map
  • Cluttered and Long Lists. Result pages are excessively long, requiring heavy scrolling and sorting
  • Hidden Information. Dropdown menus obscure key room features and confuse multi-hotel hierarchy
  • Editing Friction. Correcting date errors is frustrating, and single-click add-ons are missing


Stage three: concept development

Structure and Flow

A flow diagram was developed to define an optimal user journey. The diagram incorporated flexible pathways, allowing users either to explore hotel and room options in depth, or to fast-track directly to payment if they wished. Each stage of the process was structured as a similar loop, gradually decreasing in complexity as the user progressed towards the final step.

The final flow diagram used for concept generation




Wireframes and Sketches

Initial design ideas for pages were sketched out using pen and paper. While the sketches were rough and informal, it enabled rapid idea generation and minimised time spent on concepts that were discarded. Concepts were developed for the following features:

  • Homepage
  • Single vs. multiple hotel search options
  • Date picker
  • Guest information input
  • Available hotel options
  • Available room options
  • What to do if a user changes their mind or makes a mistake
  • Board selection
  • Add-ons
  • Payment
Notes made for the Hilton Hotel group website home page

Initial sketches for the homepage

Notes made for the Hilton Hotel group room selection page

Sketch for guest selection pop-up

Notes made for the Hilton Hotel group room information page

Date-picker design

Notes made for the Annabelle Hotel room information page

Page showing hotel availabilty and map

Notes made for the Queens Hotel homepage

Detailed hotel information pop-up

Notes made for the Queens Hotel room information homepage

Room selection page

Notes made for the London Eye homepage

Detailed room information pop-up

Notes made for the London Eye booking page

Board selection, add-ons and payment details displayed on a single page

Notes made for the London Eye booking page

Potential payment input panel, including clumping and payment button

Notes made for the London Eye booking page

Simple pop-up to display terms and conditions


Stage four: final designs

High Fidelity Prototypes

Using Figma, the final sketches were evolved into high-fidelity, interactive prototypes. Iterative testing ensured the integration of observed key UX insights. Core components, such as colours, fonts, icons, and button styles, were compiled into a cohesive design system.

Notes made for the Hilton Hotel group website home page

Homepage design which features search options for single and multiple hotels

Notes made for the Hilton Hotel group room selection page

Date selection pop-up window

Notes made for the Hilton Hotel group room information page

Guest information pop-up window

Notes made for the Annabelle Hotel room information page

Hotel options page including an interactive map

Notes made for the Queens Hotel homepage

Pop-up window displaying detailed hotel description. The window can be closed or used to proceed to the next step

Notes made for the Queens Hotel room information homepage

Room selection pop-up which also features a panel to adjust location, dates and guest selection

Notes made for the London Eye homepage

Pop-up window displaying detailed room description. The window can be closed or used to proceed to payment

Notes made for the London Eye booking page

Board selection, add-ons and payment details displayed on a single page

Notes made for the London Eye booking page

Payment panel detail including a clear indication that funds are about to be taken

Notes made for the London Eye booking page

The booking confirmation page


The Final Designs

Once the individual pages were designed and tested, a fully functional prototype was assembled using Figma’s prototyping tools. The video below demonstrates the complete booking process, highlighting the design features that enhance and streamline the user experience.





The final high fidelity interactive working prototype is embedded below. If you have difficulty viewing it, the large button below will also open the file.


The final high fidelity prototype built in Figma


Project Reflection

Designing for boutique hotel guests required finding a delicate balance between elegant visuals and functional simplicity. Boutique hospitality thrives on character, but the research revealed that when it comes to booking, clarity and speed were more important than complex visual flourishes. The early qualitative testing to identify subtle friction points by observing natural user behaviour uncovered critical issues. These became the primary focus of the new designs.

What Went Well

  • Upfront Transparency. Redesigning the pricing flow to show total costs upfront eliminated major emotional friction during room selection and significantly reduced cart abandonment risks
  • Mapping Emotions. The customer journey mapping revealed that drop-off was driven by negative emotional spikes at search and payment. By focusing specifically on these three pain-point stages (Search, Room Selection, Add-ons), the project impact was maximised without over-engineering the unaffected parts of the process
  • Designing for Two Mindsets. Creating a flexible user flow that catered to both fast-track bookers and thorough explorers highlighted the importance of modular navigation rather than a rigid linear funnel
  • Simplicity. Eliminating filler content, long paragraphs, and fragmented drop-downs transformed the experience from overwhelming to delightful. Bad UX often stems from over-communicating rather than under-communicating

What Could Be Done Differently

  • Iterative Usability Testing on High-Fi Prototypes. While extensive upfront testing was conducted during research, running a secondary usability round on the high-fidelity interactive prototype would have provided quantitative validation on the new date-editing and room selection controls
  • Returning Guest Personalisation. More time could be spent prototyping personalised user paths for returning guests. This could involve features such as saved guest preferences or one-click re-booking to further streamline the booking process beyond first-time visitors