Welcome to my second part article about design thinking in an application called Exotrip. At this time I will explain how I did usability testing.
In my previous writing, I have explained the design thinking process in making the Exotrip app. From conducting interviews to the design exploration stage. And this article I will explain how the process of doing usability testing to test whether the Exotrip app could answer the user’s problems and needs, or not at all.
“The application will not be useful if it does not answer user pain poins and needs”
So let’s dig it!
First, Set the research context!
In the context of usability this app, what I want to dig deeper is to find out whether the Exotrip design that I created previously is suitable for the user’s needs or not.
What do I really want to learn about this process?
I want to learn as much as possible, especially in finding out the usefulness of the Exotrip app. So that the purpose of this research process didn’t spread too widely, I focused on my research objectives including:
- Find out the percentage of task success in the search attraction journey & create an itinerary journey
- Find out how much time the user takes to carry out both tasks
- Looking for input or feedback from the user about improvements that might be improved from both tasks
- Find out input or feedback from the user about user interface improvements that might be done from both tasks
The research success criteria
Here I also decided the success of the criteria research in conducting user testing on the Exotrip app, that are the user can succeed in :
- finding the details of attraction and add to their list in under 3 minutes
- creating the itinerary until the finish in under 5 minutes
- and the percentage of task success is above 80%.
What did I think I know?
From the results of the design that I have done before, I assume that :
- users can easily get the details of these tourist objects
- the user can easily create neatly arranged itineraries based on the location of the tourist attractions that have been previously added
What did I think will happen?
By using the Exotrip app, users will find it easier and faster to find the location of the tourist attractions they want to visit along with reviews and videos so that users don’t have to move to other websites to find tourist attractions. As well as easily add to their itinerary with just a press of a button in one application ;).
Who is my participant criteria for this research?
In this usability testing, I also focused on participant criteria into several specific user categories:
- 5 participants (mix women & men)
- Max male/female (20–35 y.o)
- beginner travelers/experienced travelers
- have traveled in solo/group
- have traveled domestically or abroad
why do I choose such participant criteria? because according to my objective in making this application, it is to help beginner travelers or experienced travelers, whether they find it easier with the application that I made or not.
Which research method did I use?
I did unmoderated observe, where I conduct this UT, ask all questions and constraints by recording during the testing process so that no insight from the user is missed. You can read moderate or unmoderated usability testing here. I also used the Useberry tools via remote, so that the results of the task time can be measured accurately.
And if you don’t know what Useberry is, it is a tool for usability testing and gathering insights. And is greatly helped by remote testing. And did I do everything myself?
The interview guideline
In doing the interview, I asked users to think aloud and also by giving an open question. So that the user can tell and give as much feedback as possible on the design flow and also on the interface design. The task that I asked are:
- users are asked to search for attraction details and add them to their wishlist
- users are asked to create an itinerary from the beginning and add tourist attraction to their itinerary
- users are asked to set their travel time and complete their itinerary
In the open question that I proposed, I made questions based on the objective research points that were determined previously.
How’s the result?
- The average time spent by users is searching for details of a requested tourist location and then entering it into their wishlist takes approx 150 seconds or 2 minutes 30 seconds, which is good.
- The average time spent by users in creating an itinerary until completing the process takes approx 253 seconds or 4 minutes 13 seconds, which is also good.
- The percentage of task success is 100% because all users have completed the given task. This is also following the task success criteria where I set the number 80%.
- Some users think that they need information on the estimated time and distance from the first location to the next so that they can estimate their travel time properly.
When the user sees the details of the tourist location, I change the icon button to a tab button. I did this because some users felt confused about the function of the button and there was also a favorite button on the same screen so that the user felt that there were two functions the same. and when the tab button is pressed, the user will be prompted to enter tourist locations in their favorite tourist locations or to be added to their itinerary.
When the user is making their itinerary, so as not to feel confused when they want to add tourist attractions to their list, I also change the icon button to a tab button. So that users feel they know what they have to do on this screen.
So, what’s the next step?
After completing user testing, what must be done in the next step are to determine the priority of improvements and also input from users related to adding information in distance and time estimates. This is followed up again by research, design exploration, and usability testing to get some feedback.
Many things are needed before do usability testing, by making guidelines so as not to deviate from the predetermined goals. And prepare all the tools before doing usability so that we don’t lose insight from the user. Also, we have to empathize with the user when they have problems using the application are testing. If you want to read about the design process, you can read it here.
I am very grateful to Kenneth Mahakim as a mentor and instructor. Also, Handoko Dyan Aditya is a UX participant and evaluator for my design. Thank you for reading! I hope you can get any lessons from my study case. If you have any feedback, feel free to contact me at firstname.lastname@example.org or my LinkedIn.