Background

Sita is India’s leading and most awared Destination Management Company offers travel and related services to India, Nepal, Bhutan and Sri Lanka, each supported by dedicated local teams with over 400 experienced professionals across 23 offices.

The company offers a unique consultative approach, warm personalised service and hyper-customized itineraries to inbound travellers.

Scale

The company operates on a massive scale so designing a system that can scale was a big challenge.

Research

Status Quo

Our main form of research was to understand the current flow of operations and find out where the inefficiencies were. After interviewing the employees we understood the flow.

User Pain Points

We held interviews and surveys with the employees to understand how they go about their day and where they struggle. Here are some of the pain points we found.

• Multiple different tools used to operate various facets of the business causes inadvertent data loss and corruption
• Offline itinerary planning deprives planners of crucial information like ratings, costing and availability
• Undocumented planning makes it hard to track employee efficiency
• Overdependance on spreadsheets causes disorganized and inconsistent invoices ridden with untraceable costing mistakes

Proposed System

It was clear that the current system was not working effieciently and we needed to unify operations into a single platform. This will help us scale and also help us track employee efficiency.

💡 I worked on the planning part of the unified platform.

Itenarary Creation

This was the part of the platform that I was responsible for. After speaking with the planners we came up with a simpliefied flow.

💡 An itinerary in this context is a daily breakdown for a traveller 's travel in India including hotels, flights, activities.

The Flow

Lets look at the final screens for the hero flow and later we 'll break down how the design system using the atomic design approach got us there.

Adding cities

Planners can add city for each day of the itinerary. They can chose number of days and nights for each city.

Adding products

Once the cities are added, planners can add products to each day. Products include hotels, flights, activities and more.

Viewing modes

While building the itinerary, planners can view the itinerary in different modes to get a better understanding of the flow – PLanning mode, Map mode and Timeline mode.

Edit and export

Once the itineraries are complete, planners can edit them, add text and export them as PDFs. These PDFs are then shared with the travellers for approval.

Atomic Design

We followed the atomic design methodology to create a design system that can scale.

Atoms

Atoms are the smallest building blocks of the design system like colors, typography, icons, buttons, inputs, etc. In this example we can see how primary color, secondary color, box shadow etc. are defined.

Molecules

Molecules are combinations of atoms that form a more complex system. In this example, we can see how a card is constructed with different molecules like text, stat and button.

Organisms

Organisms are combinations of molecules that form a more complex UI Element. In this example, we can see different variotions of the card molecule.

Templates

Templates combine organisms to form a page. In this example, we can see how the itinerary creation page is constructed using different organisms like cards, navbar, background image, etc.