UX Case Study

Case Study: Car Hire

The main objective with this case study was to create a better experience for the user in purchasing their desired product. This would involve having systems in place that would help users find items that suited their needs in the most optimal way. Before starting a design for a system like this, the first step would be to find the existing pain points users have with these sites.

Competitive Benchmarking

For this analysis, the companies evaluated were Europcar, Hertz, and Car Europe. They all share some similar characteristics on their platforms and with that they also share some common issues. As their repeating customers would already be accustomed with the structure of these websites, a radical change would be less beneficial than helpful, although some areas could use enhancement without detracting from the user's experience.

Each site contained a sizable search function where the user could enter the essential information, such as length and locations. As the user would move onto the search results, they do a poor job in narrowing down the results to what the user wants. Certain details, such as the overall fee or letting the user know that the vehicle they selected might not be the car they receive on the day, could be missed due to not being made clear enough.

Note Taking

Two different individuals were used to test the websites of competing companies in the same industry. The sites that the two testers tested were sixt.co.uk and greenmotion.co.uk. Both testers have had different experiences using sites like these. One would have used them as part of his job while the other would have used them more commonly for holidays and trips abroad.

For these tests they both were given the same objectives. Looking for a car with automatic transmission and having different pickup and drop off locations.

Affinity Diagram

The information was acquired from taking notes during a few usability tests and benchmarking a number of industry rivals. The issues consumers kept encountering became fairly obvious. Several features, such as a filter, were anticipated but were absent. The required payment was not made clear enough. Also, there were advertisements and banners that served to annoy users rather than to aid them.

The first draft is shown in the images here. The diagram's final digital representation was produced with Miro and can be viewed by clicking the link below.

Customer Journey Map

The user is hiring a car for a reason. If they are planning on a short trip, they may have little luggage with them so a smaller car would meet their needs, but if it's a longer trip they may require something larger. Users' needs can differ from one another, therefore it would be helpful if they could narrow down their options to those that were more relevant to them. 

Another issue for the user is knowing how much that is needed to be paid at checkout. It is not always clear to the user what is the required amount to reserve a car.

Link to full diagram

Flow Diagram

The user's objective in this case study is to rent a car. The user should be required to take as few steps as possible to achieve their goal. A flow diagram can be used to assess how many steps a user must perform.

I used previous usability tests as examples of how consumers might interact with a car-rental website. I discovered what could be a better route to the end goal after being even more more aware of where issues emerge. To get to the payments page using a more effective approach, the user would need to perform roughly seventeen actions or inputs.

Interaction Design

In using a Low Fidelity prototype, the proposed solution was tested to find any issues. Using a pen and paper a paper prototype was created. This showed on a basic level how a user could interact with the product.

One of the problems that popped up was with the selecting the time. The design had to change since it wasn’t clear to the user how to use it. It was a common issue amongst the testers.

Prototype

Amendments were make to the design after some issues were put forward. One of the main issues was with the clock popping out for the user to select a time. A Medium Fidelity Prototype was created with a different solution to this problem was implemented.

The prototype was crated using Figma the Prototype can tested using the link below. This will give a good representation of how the website is to interact with.

Link to Prototype

UX Audit

For the developer to better understand how the site is meant to respond to the users action I used different labels to explain what is meant to happen. Here is an example how the annotations would be presented for each page.