Travis is a traveling app, including all collective modes of transportation: public transport, electric scooters, Taxis etc.. You can search your trip and buy your trip/ticket in Travis for all transportations. Travis has existed as an app for about two years
The goal was to ger started with usability tests, Travis wanted to know what users first impression was. I was also assigned to do a strategic plan of how to work with usability tests in the future.
Usability tests
Guerrilla tests
Mid fidelity designs in Figma
Product Owners
UX-designers
Marketing
Copywriter
2 months
First and foremost Travis wanted to know users first impression of the app. Travis also wanted a strategic plan on how to recruit users for future usability tests without using an agency.
Persons of ages between 18-65 that lives in Stockholm and who has and hasn't used Travis before and are open to tests new apps.
Usability tests
Guerrilla tests
Different designs in Figma
Staff from Travis have been recruiting their family and friends for the usability test I was going to do. I did in total six remote usability tests.
I invited staff (PO, testers etc.) from Travis to participate as observants.
Before I get started with the usability test I like to do a "warm up" interview with the user so that they can feel comfortable with the setting and me.
Interview topics
What traveling apps do they use?
Taxis? Electric scooters? Google maps?
What do they appreciate the most about the traveling apps they use?
What do they feel is missing in their traveling app? Or is there something that they don't like
Does the user see following features:
"Favorites" and what it is
Buying tickets
Search trips
Menu option
Electric scooters and car pools
Are the users familiar with the concept "favorites"
Do they know how to add favorites
Does the user understand that they can change color/name/icons?
How to change favorites after you've added them
How to book a taxi was hard to find and the information provided was often inadequate. Did the user find following:
The taxi option
Did the user understand the information that was given
Can the user find the second fastest option (other than taxi?)
Great! - Users didn't have any problem interpreting the information about "favorites".
Not so great... - The users said that they thought Travis main purpose was to search and find trips. Unfortunately, that is not the case. Travis main purpose is to sell tickets/trips
A lot of potential - But when it came to the 3rd scenario, users had a hard time finding the taxi option and couldn't really understand the information provided. There's potential of how to make improvements, such as making clear error-pages for the user.
During the usability test I saw other issues that could be improved
Bad color-contrast in the calendar, users had a hard time reading.
Difficult for user to see which street they've chosen when theres multiple areas with same street name.
These findings became the foundation of what I wanted to test on the guerrilla test.
A suggestion of improvements from this usability test would be:
Present the taxi option in the home page.
Give clearer feedback/error messages to users.
Travis had a booth in Stockholm Open and it was a great opportunity to do some guerrilla tests at the event. This was a good start to expand the demographic.
After introducing Travis as a traveling app, users were free to tell me what they think you can do in the app.
I told users that they were going to the location "Karl bergsslott" and wanted to see if they were gonna take a scooter as part of their trip.
Users were assigned to plan a trip back to Stockholm Open the next day. I wanted to see if the contrast in the calendar was readable.
Users were very interested in testing the search box. But no user typed in a destination first. They wanted suggestions of e.g: restaurants.
Users expressed a concern that you can't plan a trip ahead with scooters because what if there isn't any scooters available when you reach the location?
Some users didn't even see the dates and time and gave up planing altogether.