...
Flow through the application:
Changes:
Briefing
EatTogether is a website designed to allow people to order food for delivery from food trucks at MIT. In a minute, we are going to ask you to carry out a couple of ordering tasks. However, first we would like to ask you a couple of background questions:
...
Observations - Round 1
User 1
This user eats from the food trucks but prefers eating at Stata for lunch. The Asian Bistro truck is his favorite lunch truck. The user usually eats lunch with friends but not his research group which is made up of 3-4 people. Sometimes however, the user skips lunch because of conflicting meetings. Ordering online for dinner is a usual activity that the user does.
Overall, the user’s interaction with the interface was smooth. He even commented about the coolness and easiness of the interface. In some cases however he got confused by whether some objects like the upper arrows were clickable. Also, the user made assumptions that the personal information section in the checkout page is saved. After submitting the first order in Task 3, the user showed his concern about not wanting to post to Facebook but then realized that its optional.
User 2
For lunch, this user eats from either Forbes cafe at Stata or the food trucks. He has tried all the trucks, but usually eats from either Clover or the Falafel truck. The user usually eats lunch with friends and infrequently with 2 of his research group. A couple of times a week however, the user skips lunch. The user has only tried ordering food online from a service in New York.
...
Observations - Round 2
User 4
For lunch, this user either buys food from the Asian truck or places around Kendall square. The user usually eats lunch with friends. A couple of times a week however, the user skips or delays lunch because of either waking up late or classes. The user has tried ordering lunch and dinner online from CampusFood.
The user executed the tasks successfully but was concerned by the usability with Task 4 (task 1 edited) regarding the of the up and down arrows next to the order. She did not realize that the box indicating the number of order for the dish was an editable one, and thought it will be hard to order as much as 10 orders from the same dish by clicking the up arrow 10 times. Notably, the user was asking whether the pick location can be changed for a delivery from a certain food truck.
User 5
For lunch, this user usually eats at the student center. He used to order from the falafel truck but not anymore. The user eats lunch with friends at the student center. Sometimes the user divides his lunch and eats twice depending on his daily schedule.
During Task 3, the user started by ordering for his self, then before submitting the order, the user went back to the other trucks menu to order for his friend. However, he then realized that his previous order was deleted. He then did 2 separate orders for him and his friend. The user assumed the idea of a shopping cart with this interface, where any added item to the shopping cart remains there unless deleted by the user. The user said that after realizing that it is not the case, then the rest interface was simple to grasp, but the initial mistake seemed like a pretty big disconnect.
User 6
Overall, the user did some back and forth steps to accomplished the tasks, especially Task 2. In the task, the user had to delete the item added to add a cheaper one. The user had to go forth and back to check the amount of the item to make sure the new one selected is cheaper. For deleting the item, the user was confused as to whether he should press the “edit order” or the x button to remove the item.
...