Project Background
Objectives
City Night Line was used as an exercise for how to work within an existing, iconic brand in the transactional realm of railways. The goal was to design a responsive website that covers the main functionality: search for a connection and booking of tickets.
Role
User Research, UX and UI Design
Timeline
80h
Discover
Market Trends, Competitor Analysis, User Surveys
Night trains have long served as a means of transportation to travel
long distances in reasonable amounts of time. But since the advent
of affordable air travel, the number of night trains has fallen.
Operators find themselves in the increasingly uncomfortable position
between high-speed rail services, low-cost airlines, and low-cost
bus operators.
I started the project with market research to learn about current
trends and the future of transportation. Additionally, I analyzed
possible competitors.
To gain insights about people traveling with night trains, I
conducted a survey. From 40 survey responses, 73% of respondents
stated to travel at least once a year by train. 46% (14 people) of
them answered that they traveled already by night train.
I used an affinity map to group the responses.
The following conclusions are drawn from the survey.
Insights
- travelers choose night trains mostly to save time
- experience and sustainability play a smaller role
- the price is a significant factor for most travelers when booking train tickets, followed by details of the journey like the duration and the number of changes
- 85% of travelers are using night trains for leisure trips
- 64% are traveling alone, followed by 28% with family and 21% with a travel group
- while 21% state they are booking tickets with via app or respectively buy their ticket at a station, 93% purchase their tickets per website mostly using a desktop computer (71%)
Needs
- passengers need an easy way to find tickets for the best price
- for frequent travelers, it is essential to have a degree of service offerings, f.e. the possibility to cancel or reschedule their tickets
Pain Points
- intransparent pricing, f.e. when it is not clear upfront that service fees are applied or when there are different prices for the same comfort category
- it is annoying when it is necessary to buy tickets from different train operators, or knowledge of the railroad network is needed to find the best connections
Define
Personas, Sitemap, User Flow
In the next step, I clustered the gathered information to find patterns. At first, the similarities between all travelers seemed to lead to only one persona. But on a closer look, the differences between frequent travelers and the occasional traveler were too distinct.
Eventually, I split them up to create two personas. Please meet Emma Anderson and Paul Novak.
For the definition of the sitemap, I conducted an open Card Sorting. The results of this exercise were quite ambiguous. The users’ agreement where to place menu items was not conclusive enough to create a sitemap. Therefore I conducted a second round of Card Sorting. Based on the first results, I provided categories to the participants, but allowed the creation of own categories if necessary. The results turned out more distinct to create a sitemap.
The most important task for the personas is to purchase tickets. Thus I modeled the user flow accordingly. See the detailed user flow
Ideate
Sketches, Wireframes, Mood Board, Logo & Wordmark, Style Tile, Responsive UI Design
Before I started creating wireframes in the digital realm, I sketched landing page screens in an Crazy Eights activity. My goal was to generate as many ideas as possible in a short amount of time. Since the website's main functionality is to search trains, book tickets, and check-in online, my main focus was on providing an uncomplicated search functionality. The search should work well for frequent travelers that want an efficient way to book tickets. But furthermore, it also needs to serve users booking their annual vacation.
This exercise helped me to ideate and eventually create the wireframes.
Validating assumptions helps to make informed decisions. Testing in an early stage of a project has the benefit that changes are easier to make, preventing going in the wrong direction. Therefore, I conducted a usability test to evaluate the websites' user flow. For the test, I created two scenarios modeled after the main goals of the personas:
- booking a ticket to a specific destination with flexible dates
- researching a possible destination with a set date range and budget
With the wireframes at hand, I created a low-fidelity prototype based on these two scenarios.
While the first task worked as intended, the performance of the
second one was rather unsatisfying. The task had a bounce rate of
50%, while the other 50% of users could only indirectly finish the
mission. Interestingly all users who indirectly finished the first
scenario began browsing on the "Explore our destinations" page. They
rated their satisfaction with the booking process as high (on
average 8 on a scale from 0 to 9).
I used a Feedback Grid to gather and organize the user feedback.
Even though the tested user flow of booking a ticket worked as intended. The test revealed that users could get easily annoyed, maybe even frustrated, due to the high amount of necessary clicks. Additionally, the calendar caused trouble to some testers. Therefore, I aimed to streamline and simplify the process.
- Better accessible date selection: With the help of indicators like colors or icons that lead users to the best price, users' cognitive load can be reduced. Here it is crucial to find the right balance to prevent clutter in the UI.
- Reducing clicks: At the moment, it is necessary to click each form field separately. When data is entered, the form can step forward without an additional click by the user. The system will guide the user better through the process.
While there is always room for improvement, I did not attempt to iterate further on the second test scenario's user flow in favor of optimizing the booking process. Yet, I took the collected insights to improve the discoverability of destinations. I integrated an "anywhere" option within the search form to help users find available destinations within their travel dates.
With the user flow in place, I focused on the branding. City Night Line connects cities across Europe. I took inspiration from the lights that pass by the windows when traveling by night. As you come closer to the destination, the lights will increase in numbers, and colors get more vibrant. City centers, especially around the central station, often have a multitude of lights.
I gathered inspiration on a mood board to develop a feeling for the City Night Line brand. The former CNL used royal blue and bright yellow to transport the idea of night traveling. My goal was to give the color palette a little twist to emphasize the new take on night trains. It contains bright, neon colors, resembling the neon light of big cities. With a shade of dark blue as a base color, the color palette aims for a luxurious feel that emphasizes the brand attributes of modern and comfortable travel overnight that lets you arrive relaxed at your destination.
Logo and wordmark are an essential part of a brand. Since City Night Line was an actual operator, I revised the old logo. The goal was to keep its essence - a flashy font type and the moon to symbolize night travel. The result is a minimalistic logo. Moreover, I created a Style Tile to dive deeper into defining the look and feel.
Eventually, this lead me to the creation of the user interface.
Deliver
UI Kit, Prototype
In the next step, I collected all interface elements in a UI Kit. This collection of UI components can serve as a reference point for later additions to the project and be useful for communication in further development. See the detailed UI Kit
Prototypes help to communicate the way a website interacts with the user. Therefore, I created a prototype to fill the screen design with life. See the prototype
Iterate
User Testing, Second UI Design Iteration
To uncover usability issues in the design, I conducted a second user test. This test aimed to validate if the iteration of the booking process improved the user experience. Additionally, the goal was to find out about users' overall satisfaction and impression. For that, I created a high-fidelity prototype based on the desktop screen designs. To get comparable results, I conducted the same tasks as in the first test run. But since the second task was not specific enough, I refined the wording to be more clear.
Afterward, I clustered all user reactions in a Feedback Grid to find patterns. It became evident that the success rate of the test scenarios increased compared to the first test setup. Especially the second scenario's success rate showed a significant increase. It showed that incorporating the 'Anywhere' option delivered added value to the user flow. Overall, users described the user flow mostly as intuitive and easy to follow. While the UI design also got mainly positive feedback, the user test showed that users struggled at some parts of the process.
Finally, I iterated over the UI based on the user feedback. I targeted the discovered issues and updated the prototype accordingly.
- Make clickable elements better recognizable - Users found it difficult to tell the difference between clickable items and pure text. Buttons and links should be highlighted and be noticeably clickable to reduce the user's cognitive load.
- Indicate which option will be selected on click - Similar to the previous point, it helps users navigate through a product when it indicates selectable options, f.e. through hover states.
- Simplify the selection of train options - This issue is as well related.
- Add information to the travel comfort options.
- Revision of the background image in the booking process
I also revised the prototype. See the updated prototype here