UX Design Project

This project was completed as part of my Diploma in Product Design through the UX Design Institute, which I undertook from June 2024 to May 2025. The goal was to design a hotel desktop booking experience that is intuitive, user-centered, and based on real research insights. It challenged me to apply the full UX process—from research and analysis to prototyping and usability testing—while developing a functional, clickable prototype that could be handed off to developers.

Hotel Desktop Booking App

My Role

Introduction

Problem Statement

Travelers often encounter friction when booking hotels online, from confusing interfaces to unclear booking summaries. The goal of this project was to reimagine and streamline the hotel booking process for a fictional desktop-based application—focusing specifically on one core user flow: searching for a location, selecting dates and guests, choosing room types and extras, and proceeding to a final booking summary.

My Role

As the sole UX Designer on this case study, I was responsible for conducting user research, analyzing insights, conceptualizing user flows, designing wireframes and prototypes, running usability tests, and delivering annotated handoffs to the development team.

Methodologies Used

The project followed a structured UX design process, consisting of:

  • Research: Conducted usability testing, note-taking, and optional surveys to gather qualitative insights.

  • Analysis: Created affinity diagrams and a customer journey map to identify user pain points and opportunities.

  • Concept Development: Mapped out the user flow and produced initial interaction sketches to explore solutions.

  • Design: Developed a high-fidelity clickable prototype in Figma, supported by optional usability tests and detailed annotations for developers.

UX Design Process

This project strictly adhered to the end-to-end UX process. I began with understanding real user problems through qualitative research and usability testing. Insights were synthesized into actionable findings, which informed the journey mapping and flow design. The iterative prototyping and testing phases ensured that the final experience was smooth, intuitive, and user-focused.

This case study highlights how thoughtful UX research and process can reduce design risks and improve the quality of digital products. By grounding design decisions in real user needs, I was able to deliver a functional prototype that not only meets business goals but also provides a seamless booking experience for users.

Research

User research was the foundation of this project, ensuring that every design decision was grounded in real user needs and behaviors. This phase focused on uncovering both pain points and opportunities within the hotel booking experience. The research methods I used were a combination of qualitative and quantitative approaches to gain a holistic understanding of user expectations.

Competitive Benchmarking

Why I did It

To understand current industry standards and identify strengths and weaknesses in competitor booking flows. This helped me recognize patterns users are familiar with and discover areas where the experience could be improved.

Process

I analyzed the hotel booking processes of leading travel websites, evaluating them on aspects such as layout clarity, ease of use, filtering options, and the booking summary experience.

Key Insights
  • Clear date and guest selection tools are essential for reducing booking friction.

  • Overloaded interfaces and upselling clutter can overwhelm users.

  • Trust signals (like reviews, ratings, and secure payment notices) significantly influence booking decisions.

Online Survey

Why I did It

To gather broader, initial feedback on users’ past experiences with booking hotels online. The goal was to validate assumptions and identify user priorities across a larger sample.

Process

I created a short Google Form and shared it to my friend & Family and some gathered from social media sharing, collecting data from a range of users with different booking habits.

Key Insights
  • Most users prioritize clear images, price, room quality, and flexible cancellation.

  • Frustrations included hidden fees, poor mobile responsiveness, and lack of booking transparency.

  • Users expect search filters and comparison tools to be intuitive and quick to access.

Note-Taking

Why I did It

To ensure meaningful and unbiased capture of user behavior during usability testing. Note-taking helped me organize observations into themes later used in the affinity diagram.

Process

During interviews and usability testing, I documented user actions, comments, hesitations, and emotional responses in a structured format.

Key Insights
  • Users often paused when unclear on which room details were included in the price.

  • Confusion arose around guest number limits and how extra fees were applied.

  • Positive reactions were noted for clear summaries and real-time feedback during form completion.

Usability Testing

Why I did It

To observe how users interact with existing booking systems and identify usability issues in real time. This was critical for understanding where users get stuck and what features improve their flow.

Process

I asked 1 participant to complete a booking journey on a competitor site while thinking aloud. Sessions were recorded and conducted over Google Meets.

Key Insights
  • Users appreciated step-by-step booking with visible progress indicators.

  • Many struggled to go back and change a detail without restarting the process.

  • Lack of summary clarity often led to hesitation at the payment stage.

Summary of Research Findings

From this research phase, I identified several key user needs and frustrations that informed my design decisions:

  • Clarity and simplicity are essential across all steps of the booking process.

  • Users want control, including the ability to easily update details mid-flow.

  • Transparency in pricing and booking terms builds trust and reduces drop-off.

  • Familiar patterns and clean UI reduce cognitive load and increase task completion rates.

Analysis​

After gathering qualitative and quantitative data through research, the next step was to make sense of all that information. I used two core analysis techniques — an Affinity Diagram and a Customer Journey Map — to identify patterns, uncover key user insights, and lay the groundwork for informed UX decisions.

This phase was critical to synthesize what users were really experiencing, to separate anecdotal feedback from consistent patterns, and to prioritise which problems to solve first based on real user needs and potential business impact.

Affinity Diagram

Why I did It

An Affinity Diagram is a powerful technique to organise scattered observations and data points into meaningful clusters. Since my research included both note-taking sessions and usability tests, there was a large volume of findings to work through. This tool helped to:

  • Identify repeated patterns across multiple users

  • Highlight surprising findings that stood out

  • Align all insights into digestible categories

  • Set a foundation for the Customer Journey Map

Examples of Raw Notes (with context)
  • “Double bed in add-on is confusing - don’t know what it means” Clearer indication would have been appreciated

  • “Like the feedback from trip advisor.” Feels trustworthy.

  • “Don’t like the lengthy scrolling” User prefers a simpler one page, comparison layout.

  • “Too many next page clicks, process to get to final booking stage takes too long” Looking for a more compact layout

  • “Liked classier look of the site” Good first impression and creates a warm feeling of user

Process
  • I compiled all raw notes from both the note-taking and usability testing projects.

  • Each observation or direct quote was written as a standalone sticky note in FigJam.

  • I avoided interpretation at this stage and focused purely on what users said or did.

  • Notes were then grouped into logical categories based on common themes.

  • Categories were named after recurring user concerns, actions, or emotional reactions.

Identified Clusters & Themes
  • Search & Filters Confusion

    Users often struggled with filter visibility or placement. Important search fields (dates, guest numbers) weren’t always clear.

  • Missing Visual Hierarchy

    CTAs were frequently overlooked. Users scanned for price or ratings first — these were inconsistently prioritized.

  • Trust & Transparency

    Users wanted clearer pricing breakdowns. Reviews and location details helped increase confidence.

  • Positive Design Elements

    Users appreciated map integrations. Local language and imagery added a sense of familiarity.

Key Insights
  • User pain points are largely tied to lack of clarity and visual hierarchy.

  • User objectives revolve around quick access to essential info: availability, price, ratings.

  • Positive reactions highlight the value of localized, trustworthy content.

  • The business opportunity lies in addressing usability while retaining the trust-building features.

Customer Journey Map

Why I did It

The Customer Journey Map allowed me to visualise the end-to-end experience of a typical user booking a hotel. It took the structured themes from the Affinity Diagram and laid them out in sequence, from first interaction to final confirmation. This helped identify where users face friction and where delight occurs.

Process
  • I mapped the user journey in 6 core stages:

    1. Landing on Homepage

    2. Entering Search Criteria

    3. Browsing Results

    4. Selecting a Property

    5. Viewing Booking Summary

    6. Finalising the Booking

  • I filled in observations, pain points, emotional responses, and positive moments for each step using my research data.

  • I ensured the map was concise and easy to scan, with color-coded indicators and formatting to guide the viewer’s eye.

Key Insights
  • The biggest drop-off risk is between browsing and selecting a property, due to clutter and inconsistent info.

  • The most emotionally positive point is when users view location and photo galleries — strong visual content helps drive trust.

  • The summary stage needs clear price breakdowns, editable fields, and confirmation reassurance.

  • Early user confusion on the homepage signals a need for a stronger, more prominent CTA and clearer search flow.

Problem Definition

Based on both analysis techniques, the primary problem to solve is:

Users are struggling to complete bookings efficiently due to inconsistent layout, unclear CTAs, and a lack of pricing and property transparency.

This affects both user satisfaction and business conversion — solving this will improve retention and reduce booking abandonment.

Concept Development​

The Concept phase marks the shift from understanding the problem to exploring possible solutions. Building on research and analysis, this phase aims to transform identified user pain points into practical design concepts — specifically through User Flow Diagrams and Interaction Sketches.

By working with flows and paper sketches before jumping into high-fidelity wireframes, I ensured that core interactions and structures were user-focused, iterative, and informed by real needs — rather than visual assumptions.

User Flow Diagram

Why I did It

Creating a Flow Diagram helped break down the complex booking process into manageable, sequential steps. By mapping out the ‘happy path’ — the ideal flow a user would take from landing on the homepage to confirming a booking — I could:

  • Clarify the logic behind screen transitions

  • Avoid feature creep before screen design begins

  • Pinpoint exactly which screens would need to be sketched

  • Align user interactions with problem areas found in the Customer Journey Map

This was essential to ensure the solution addressed the right problem without overwhelming the design phase.

Process
  • I reviewed all pain points highlighted in earlier phases, particularly where user confusion or drop-off occurred.

  • I sketched an initial flow by hand, starting at the homepage and ending at the booking summary screen.

  • I focused on the primary, linear booking experience — the most common path a user would follow.

Flow Diagram Sketch

Interaction Sketches

Why I did It

Before diving into digital design, I created Interaction Sketches to explore how each screen would look and function. Sketching allowed me to iterate quickly, test layout options, and define interface logic with clarity and speed.

By sticking to hand-drawn sketches, I stayed focused on usability and structure, not visual polish. This kept the process lean and user-centered.

Concept Takeaways
  • A well-defined flow helps eliminate guesswork during UI design.

  • Sketching before wireframing ensures fast iteration and better problem-solving.

  • Each step in the booking process is now intentional, with interaction logic directly rooted in research.

  • The concept phase set a solid foundation for usability-focused digital design.

Homepage
Hotel List
Hotel Page
Hotel Confirmation & Payment Page

Design

The design phase is where all the insights, flows, and sketches come together in the form of a medium-fidelity prototype. This interactive model brings the concept to life, allowing for realistic testing of the experience and usability before any development begins.

The prototype is also accompanied by detailed annotations, which communicate exactly how the interface should function — ensuring alignment between designers and developers.

Prototype

Why I did It

The prototype simulates the full booking experience, from homepage to booking summary, and includes all key interactions, copy, and screen transitions. This gave me the opportunity to:

  • Validate my design decisions against real user flows

  • Test whether my proposed solution genuinely solved the issues uncovered during research

  • Gather feedback to iterate and improve, without the cost of coding anything

Annotations

Why I did It

Design annotations are essential for communicating interaction behavior and logic to the development team. They bridge the gap between visual design and technical implementation, ensuring the user experience is developed exactly as intended.

Below are a few screenshots of annotations showing how I went about this task.

Conclusion & Reflection​

Final Solution & Reflection

As I reached the end of this UX project, my focus was to ensure that the final solution not only looked good on paper but functioned seamlessly for users. Every design decision was grounded in user research, journey mapping, flow analysis, and iterative testing — all aimed at solving the original core problem:

“The booking process is unclear, disjointed, and lacks transparency — leading to user frustration and drop-off.”

How the Final Solution Solves the Problem

Through each phase — from discovery to prototype — I addressed the key issues identified in the Customer Journey Map and Affinity Diagram:

  • Confusing Booking Navigation

    Problem: Users struggled to understand where they were in the process. Solution: The flow was simplified into a clear, step-by-step process, reinforced by strong CTAs and visual hierarchy at every stage.

  • Lack of Transparency in Pricing

    Problem: Users felt uncertain about total costs and hidden fees. Solution: Each screen prominently displays a dynamic pricing breakdown, even before reaching the final summary.

  • Missing Context About Room Inclusions

    Problem: Users lacked information about the accommodation inclusions and its surroundings. Solution: The property details screen includes clear descriptions, a photo carousel, amenities, maps, and reviews — all above the fold to inform decisions quickly.

Why This Solution Works

This design succeeds because it is:

  • User-validated through research and testing

  • Built on real user pain points, not assumptions

  • Simple, intuitive, and transparent, reducing friction throughout

  • Ready for handoff, complete with developer-friendly annotations

The result is a streamlined booking process that builds user trust, reduces drop-off, and encourages conversion — all with usability and clarity at its core.