Yelp Re-Design
Finding problems with Yelp’s desktop experience and solving them.
Project Background
For my UX design class at UC San Diego Extension, I conducted user testing on Yelp's desktop website experience.
With its diverse range of functions and widespread popularity, I thought Yelp's website was a good choice for evaluating user experiences and identifying potential design opportunities. Three participants were asked to complete various tasks while interacting with the website, allowing me to observe and identify areas for improvement.
The Objective
Find 3 problems, then provide solutions.
The Process
4 steps.
Initial Questionnaire
For the users who have used Yelp before, they are asked the question:
“Are there things that you don’t like about Yelp’s interface?”—the goal of this step is to immediately obtain user problems before going through the task analysis.
Task Analysis
Users are asked to complete a set of common tasks on Yelp’s website; during this process users are asked questions—this method is known as contextual inquiry. Users are also encouraged to voice any thoughts aloud that arise.
If the user was able to complete the task, they are asked to give a 1-to-5 usability rating (1=unusable, 5=perfect) and to justify it. If the user could not complete the task, they are given the answer and asked to give their qualitative opinion on it. Data is collected with screen-recording software and note-taking.
Narrowing Down the Problems
At this point, several problems have been found via the initial questionnaire and task analysis— they are narrowed down to three.
The three problems chosen are the ones most commonly shared among the user group, and most in need of a substantial re-design.
Solving the Problems
The three chosen problems are analyzed, and re-designs of the interface are created as solutions.
Problems Found
3 problems were found.
The interface for ordering food has two usability issues.
The Collections page has two usability issues.
It takes too much time to view the entire restaurant menu.
Problem 1
The interface for ordering food has two usability issues.
Why is this a problem?
Task Analysis #1:
Users are told to remove an item from the cart.
Result:
1/3 users could not complete the task.
Task Analysis #2:
Users are told to search for “Shanghai Bowl” by using the “Search Menu Items” bar and then return to the full menu.
Result:
2/3 users could not complete the task.
Interpreting the Results
Problem 2
The "Collections" page has two usability issues.
Why is this a problem?
Task Analysis #1:
Users are told to save “Mighty Bowl” to the “Asian Restaurants” collection and then find the “Collections” page.
Result:
2/3 users could not complete the task.
Task Analysis #2:
Users are told to remove “Mighty Bowl” from the “Asian Restaurants” collection.
Result:
1/3 users could not complete the task.
Interpreting the Results
Problem 3
It takes too long to view the entire restaurant menu.
Why is this a problem?
Task Analysis:
Users are told “Read the restaurant menu and pick items as if you were going eat there.”
Result:
3/3 users scrolled to the bottom.
2/3 users scrolled back up and down the menu.
Interpreting the Results
Lessons Learned
This was my first project where I got to experience what it was like to observe and test users. Due to the constraints at the time I was only able to have 3 test participants, but I was still able to gain valuable insights. If I were to do this project again, I would try to test at least 5 users.