Case study 📣:

Project context:

The user gets irritated while booking flight tickets and hotel rooms individually and oftentimes is lazy enough to look out for vacation spots. So we aim to provide a simplified solution to the user, where the user can book tickets and respective rooms in a single place.

Project objective:

-To make the booking experience user-friendly.

-Clipping vacation deals on a single platform.

-To make the payment method simplified.

-To provide filters respective to the user’s requirement.

Roles & responsibility:

I and my teammate Ramoth were responsible for making the payment process simplified and user-friendly.

Research objective:

-To understand the user preferences while booking a hotel.

-To know the user’s traveling mode.

-To understand the user’s comforts with online payment methods.

-To understand the user’s preference while booking a vacation trip.

Research methods:

-Interviewing the user in the form of a questionnaire & phone call.

-Checking out the existing methods while also taking inspiration from them.

-Comparing the current solutions with our output and user’s problems to come up with a simplified way to deal with it.

-Discussed the various ideas to come up with a single solution.

These are the apps I have gone through to get a basic idea of how payment methods are carried out in different apps (this comes under my secondary research).

Target Users:

-Around age 18–50, folks who trust virtual surfing and are comfortable dealing with it.

-Having a knack for traveling.

-People who are comfortable traveling via flight mode.

-People who are used to digital transactions.

User interviews:

How often do you travel?

What mode do you prefer to travel to?

Are you comfortable with online transactions?

What mode of payment are you most familiar with?

What’s your all-time app to plan your trips? Do you use the same app for booking your flights, hotel, etc?

What do you look for when you book a hotel?

How was your checkout experience?

Research analysis:

Key finding & learning:

*Pain points:

-Typing card details for every transaction.

-No immediate intimation if payment failed.

-Cancellation inquiry should be dealt with by the app.

-Steps to contact the app for the refund process.

*Goals🏹:

-Travel loans while checkout.

-Quick EMI options and travel loan eligibility.

-Different modes of payment.

Personas:

User scenario:

User Flows:

Information architecture & site map:

The process me and my teammate were responsible for is colored in yellow.

High fidelity wireframes & wire flows:

I kept the background plain as not all age groups fascinate a fancy design, though all my previous designs were screaming for attention😅. My mentor helped me understand this.

Here I thought of using step-by-step instructions for getting a refund, where people who are not familiar with online payment and are conscious about the refund problem can go through these steps to get their refund instead of freaking out😱.

SIDE NOTE📑:

Hush, coming to this card part. I wish banks should introduce the tapping system to the ATM where once you tap your card, you can immediately do your work whether it's withdrawing your money, checking balance, or anything else. (though this they have applied on card machines) but coming to the ATMs inserting and waiting for your card to get read and getting a glare from a stranger who is waiting in the line for a long time as you are doing your business is really tiring.

Frankly speaking, I have never used mobile wallets as I am very much comfortable with UPI and card methods that I never tried any new options.

PAY LATER option is really good for bachelor students where each person can pay separately for each month to complete their target. Wish I could have explored more of it in my engineering days😒.

Here I thought of using the concept of a cart option where payment of flight and hotels can be done in one place.

But sorting out the payment for the flight and hotel so that they would get back their money individually would be the work of the app.

So I don't think it's feasible enough as it may cause lot more issues than there are currently.

Conclusion:

What did I learn?

So the main and foremost thing I learned is that your design should be balanced between its design part and content part, It should be in such a way that the user should know what the next step is without handing out the instructions.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store