Sojourn hotels

Hotel database, designed with simplicity at the forefront; from browsing, to sharing, to booking.

Ideation
User testing
Branding

Your home away from home.

Sojourn Hotels is a premium hotel booking service designed for mobile applications. As the sole UX designer, I created the entire project across all user touch-points; through research, ideation, branding, design and testing.

This project was part of my 8 month UX Design course, curated by the UX Design Institute. The course has helped me to further my knowledge into the product design space.
Client
Student Project for the UX Design Institute
My Role
Entire Product Design - Research, Design and Testing
Methods
Quantitive research techniques, User Surveys, Running Usability Tests and Design Tools (Figma, XD)
Timeframe
8 Months (2021)

Process

1
Research
2
Define
3
Ideate
4
Design
5
Prototype

Competitive Analysis

Conducting competitive analysis allowed me to gain better insights into the processes and functionality that the market leaders use in order to guide their users as smoothly as possible through the process.

From my research, I found that while most apps had good initial foundations such as search function and date selection, there seemed to be a few cases of information overload or data confusion the further the user gets through the process.

Considering that the payment stages are the most significant part of the booking process, it was imperative that there needed to be a focus on significantly reducing the amount of pain points for the user during the latter stages of the process.

Surveys and Usability Testing

By creating online surveys and conducting usability tests, I was able to gain key insights and data to help better understand the user’s needs and behaviours when using a similar product or website.

I surveyed 50 adults and categorised my results into 3 age groups. I then selected 2 adults from each age group and conducted usability tests and depth interviews for each person. The information I gathered from this qualitative research proved to be instrumental in helping inform my design decisions later in the process.
10%
Premier Inn
46%
Hilton
76%
Booking.com
87%
Air BnB
51%
Expedia
69%
Trivago

66%

of people use booking apps to browse hotels with no intention of booking.

53%

of users favour functionality of the apps over the content or aesthetics.

34%

of users choose to browse without inputting data such as dates or guests.

Key Findings and Insights

Across most current hotel or holiday apps, users were typically happy with the first few introductory screens; things like search functions and inputting the desired dates. But as they moved through the process, there seemed to be mounting information that was not communicated in a concise way. This then has a domino effect on the preceding screens and ultimately leads to a higher drop-off rate towards the end of the booking process.

Another key insight into user behaviours showed that nearly half of all the candidates surveyed used hotel booking apps to browse and compare hotels with no intention of booking. These insights showed that there was a necessary focus needed at the 'search' and 'browsing' screens to optimise the overall experience for the user.

The data produced from these techniques gave me valuable insights into the way in which users flow through a typical booking service. The research techniques produced both quantitative and qualitative results which helped to influence the define stage of my process.
1
Research
2
Define
3
Ideate
4
Design
5
Prototype

Affinity Diagrams

In order to make sense of the data produced by the various techniques used, I ran an affinity diagram session with two other designers. I shared the various sources of data with the team to give top level insights before starting.

The session ran for 2 hours, in which time we gathered a wide range of information ranging from user pain points and emotions, to user processes and thought patterns. We then grouped the data into similar themes to create structured data from an otherwise unorganised collection of points.

User Journey Mapping

Utilising the data from our affinity diagrams, we were able to determine the user journey map to clearly identify the user flow through similar applications. This process helps to outline the users flow through a similar product or application.

Using this process allowed me to clearly identify that most of the users pain points are located around the final stages of the booking process. It was therefore clear at this point in the define stage that it was imperative that there should be a focus on significantly simplifying the product for the user during the latter stages of the process.
Home Screen
Browse Screen
Hotel Browse
Room Selection
Summary
Payment Screen
• User Goals
Start to search or browse for a holiday or hotel.

• Behaviours
User looks for search bar to begin searching by location.

• Pain Points
The next step from the home screen should be very clear. Otherwise this could become a pain point.
• User Goals
Input the dates in which they intend to travel and see the availability of hotels for those dates.

• Behaviours
Users want to input their details as quickly and easily as possible to move to the next step.

• Pain Points
Calendars are large sections of information that need to be as clear and easy to use as possible.
• User Goals
Select a hotel that looks like it fits their needs: aesthetics, location, attributes.

• Behaviours
Browse through a variety of hotels to best match their needs.

• Pain Points
Button to move onto the next step must be clear from here. Key points need to be clear at this screen.
• User Goals
Select a room that looks like it fits their needs: aesthetics, comfort.

• Behaviours
Browsing to see what type of room matches their needs.

• Pain Points
Images of rooms must be shown at this screen and button to move onto the next step must be clear from here.
• User Goals
To check that the items they have selected are listed in the summary.

• Behaviours
Checking that the information entered on the previous pages is all accurate.

• Pain Points
Add-ons sometimes can be considered annoying. Summary needs to be as concise as possible to avoid information overload.
• User Goals
Book their stay, holiday or hotel.

• Behaviours
Entering payment information.

• Pain Points
Currency must be correct for the location of the user.
1
Research
2
Define
3
Ideate
4
Design
5
Prototype

User Flow Diagrams

The ideation stage begins by gathering all the data, insights and key learnings from the two previous stages. I created screen flows, with user interactions as wayfinders to get from point A, to point B.

This technique acted as the catalyst for what became the design and prototype stages of the product. This process aims to demonstrate best practice user flows, enabling navigation around the product with minimal effort.

Interaction Design

After gathering all the data from the research techniques and establishing the problems in the processes, I was able to start to design my product. Utilising the user flow diagram as a screen guide, I was able to sketch out the top-line user flow screens as low fidelity wireframes for my product.

Low fidelity wireframes are named as such, because the only follow the top-line user interaction of an application - in this case, booking a hotel stay. This is because the main aim of this process is to test the interactions between product screens. It is actioned in this very simple format to save time, and identify any problems that otherwise might occur in mid or high fidelity wireframes.
1
Research
2
Define
3
Ideate
4
Design
5
Prototype

UI Design and Development

After addressing a couple of minor points from the low fidelity sketches, I was then able refine the screen designs and start to build out the user interface. These would be in the form of mid-high fidelity wireframes, with the goal of being able to prototype and test my product with actual users.

I brainstormed ideas for brand name, developed a minimal and impactful colour pallet and settled on a tone of voice for my product. These key branding attributes were essential to the early stages of the design process. From here, I was able to develop icons, select imagery and start to think about page interactions.

Product Branding

I decided on the name ‘Sojourn’ - from the noun, which means to stay or visit. An english translation from the French word Sejour, it is usually used within the context of a second home or vacation house.

The brand identity I was creating was aimed at users that wanted a more premium stay in some of the worlds greatest cities and so I felt that this could be a perfect name for a premium product.

Navigation Function

My research determined that 66% of hotel application users, utilised these types of products simply to browse hotels stays and holiday destinations. It was therefore extremely important to have the initial stages of the product simple to navigate and easy to use. This meant that swapping back through the initial data input screens, such as dates, location or guest count, needed to be very accessible.

Throughout my wireframes and designs, I took inspiration from filing systems, such as the tabs you might find on a rolodex, and incorporated them within the header of the search screens. This type of filing system matches users mental model for what could be considered organised data and therefore, is easily updated at any time as the user browses through the product.
Tab 1 - Location
Tab 2 - Date selection
Tab 3 - Guest Count
1
Research
2
Define
3
Ideate
4
Design
5
Prototype

Prototyping and Testing

After refining the brand aesthetics and product functions, I was able to design mid-high fidelity prototypes. This level of detail begins to offer an experience that is more in-line with what the end product aims to be; a fully functioning, easy to use hotel booking application. From this stage I am able to start to test my product with users, much in the same way I did at the definition stage of the project.

From here, I was able to conduct usability tests on my product. I enlisted the help of friends and family to help test my product to see if I was able to address the problem that I had discovered in the research stage.
In order to obtain unbiased results, I chose not disclose any of my initial findings throughout the research or defining stages of the project. By asking broad, open ended questions about some of the latter stages of the user journey, I was able to receive unbiased, qualitative data from my subjects about previous pain points.

In addition to these insights, this process can also offer additional data into the users needs, goals and pain points, which allows me to begin to gather more information and start to develop the product further.
©NickJoDesign2024