FlixBus

UX Design Challenge
Note: Showing FlixBus latest result after I'm hired is confidential and not possible
Project Overview
For this challenge, the FlixBus (German brand which offers bus & train trip service in various European countries) will be presented as a case study. my main goal is to improve the experience of FlixBus users; improve the search-engine find-ability when looking for a ticket,
increase the satisfaction and make the important information accessible and transparent when booking the bus ticket as well as when waiting for the bus to arrive.

Tools: Competitor analysis, Balsamiq, Sketch App, Invisionapp, usable testing.
Case study Brief & Method
1. Increase the progression rate from the FlixBus landing page to the search result page.
2. Identify customer pain points when booking a ticket
3. Better promote ticketing information and purchase
4. A quick and easy way to find a ticket that suits the user the most.

For this task I've used the Nielsen Norman group design-thinking framework, follows an overall flow of: Understand, Explore and Materialise.
Within these larger buckets fall the 6 phases: empathise, define, ideate, prototype, test, and implement
1. Understand
My research process begins with an exploration focused on the user for a better understanding of the common pain points, as well as doing a Competitors analysis.

User Research
In the best case scenario, I would have access to the company dashboard numbers or work closely with the data team to pull out valuable data and numbers to help me identify customer problems and understand their behaviour. Since it is not the case I've interviewed potential user which could be used as a proto-persona as well to support my hypothesis.

During the user testing session the participant were asked to book a round trip ticket from Berlin to Paris using FlixBus Mobile site, The research focuses on the following:

- How is the user experience with the FlixBus mobile site?
- Does the company offer relative/helpful information to help you book your ticket faster?
- Is there are any information that might be missing and would like to know about them?
- Where are the opportunities for improving satisfaction with the FlixBus mobile site experience?

Key Findings
- The users look for a cheap ticket to travel with FlixBus.
- The users prefer to select the bus station from the homepage to narrow down the options in the search result page.
- The users would like to see the cheapest/fastest ticket highlighted in the search result page.
- The users appreciate information transparency in the search result page, (ex.FAQ).
- A Journey map to check the trip route is nice to have.
Competitors analysis
Once I had an idea in which direction to go, I made an analysis of the Competitors, since it is a good way to to get inspiration and insight into what works and doesn't.
2.Explore
The next step after collecting data from different sources was filtering and
grouping these data and then break them into small digestible pieces.
based on that, I came up with hypotheses and ideas to improve customer
experience and help to solve their problems.

Hypotheses
- Showing users the bus stop in the home page would narrow down the search result options.
- Showing users the bus stop in the home page would allow users to choose the closest bus station to them.
- Hiding the search form in the search result page will allow users to scan the ticket options faster, and show the important information first.
- Users would be interested in knowing more about the Journey details before booking the ticket in the search result page.
- Highlighting the ticket (eg.cheapest) in the search result page will increase FlixBus CRT
- Showing more details (seating, luggage ) in the search result page will help the user in taking a better decision to book their ticket.
3.Sketching & Wireframes
Creating Wireframe whether it is high fidelity or low-fidelity is crucial in the design process, to better visualise how the design solution would be like.
Next step!
The next step will be continuo the testing and gettingback to users feedback until the implementation phase