UI/UX Case Study

Revolution Travel CRM

UI/UX Design

Project Duration

3 Months

Start Date

2 Jaunary 2023

Designer

Sumit Barapatre

Overview

Revolution Travel CRM is a mobile-first travel platform designed to help users discover destinations, book trips, and manage itineraries in one unified experience. The project focused on reducing friction in the booking journey and improving post-booking visibility through a more structured and scalable UX.

My Role

I led the end-to-end UX/UI design of the mobile experience, working closely with product and engineering to define user flows, improve usability, and establish consistent UI patterns. Responsibilities Owned UX from discovery to high-fidelity delivery Partnered with Product Manager and developers Conducted UX audit of existing flows Designed scalable mobile components Prepared developer-ready Figma files Team: PM + 2 Developers + Designer (me) Timeline: (add yours)

problem statement

Travelers were experiencing friction during destination discovery and booking due to scattered information, inconsistent hierarchy, and multi-step cognitive load. This was increasing decision time and creating drop-offs during the booking journey.

UX Approach

I tackled key user challenges and refined the automation experience through a structured UX approach, grounded in real user feedback, behavioral insights, and continuous iteration.

RESEARCH & DISCOVERY

Evaluated existing travel booking patterns

Identified friction in destination browsing

Reviewed user expectations for mobile travel apps

DEFINITION & IDEATION

Mapped core journey: Explore → Book → Manage

Prioritized high-impact usability gaps

Defined improved information hierarchy

DEPLOYMENT & ITERATION

Designed mobile-first responsive flows

Built reusable component patterns

Iterated with stakeholder feedback

Understanding User Behavior

Initial analysis revealed key friction points in the travel journey:

Users struggled to quickly compare destinations Booking steps felt cognitively heavy
Trip details were difficult to scan post-booking
Visual hierarchy was inconsistent
Navigation lacked clear progression
These insights shaped the redesign priorities.

Solution Strategy

Guided Travel Experience

Goal: Create a smooth end-to-end journey from discovery to trip management.

Approach

➤ Simplified browsing patterns

➤ Reduced booking complexity

➤ Structured trip information

➤ Standardized UI components

Outcome

A more confident and fluid travel experience across the lifecycle.

Navigation Flow

Explore → Select → Book → View Trip → Manage

This improved:

➤ task continuity

➤ decision clarity

➤ flow predictability

➤ user confidence

Key Design Decisions

➤ Prioritized card-based browsing to reduce cognitive load during destination scanning

➤ Introduced progressive disclosure in booking to prevent user overwhelm

➤ Structured trip details using grouped information blocks for faster glanceability

➤ Standardized spacing and typography to support mobile readability at scale

Trade-offs Considered

We explored a more information-dense layout for power users, but early reviews showed it increased cognitive load on mobile. We intentionally optimized for clarity and progressive reveal, accepting slightly deeper navigation in exchange for improved scanability and user confidence.

Sketches & Exploration

Early explorations focused on:

➤ destination card hierarchy

➤ booking step reduction

➤ mobile readability

➤ quick-scan information layout

Multiple layout directions were tested before converging on the final mobile pattern.

Wireframe & prototyping

Interactive prototypes were created to

➤ validate booking flow clarity

➤ test navigation comprehension

➤ align stakeholders early

➤ reduce development ambiguity

Iterations primarily targeted cognitive load reduction during booking.

Final Design System

Key Experience Improvements

Design Impact

The redesigned experience improved content scanability, reduced booking friction, and established a scalable mobile foundation for future travel features. The new structure also enabled faster iteration cycles for the product team.

System Thinking

The component system was designed to support future feature expansion and maintain visual consistency across new travel surfaces as the product scales.

Outcomes & Learnings

➤ Travel apps demand extremely strong visual hierarchy

➤ Progressive disclosure reduces booking friction

➤ Component systems improve scalability

➤ Early product–engineering alignment speeds delivery