|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This is the briefing statement we gave to our testers:
Hello and thank you for help us with our project, OpenMenu! This is _________, _______, and _______. Picture this: You are going out to a restaurant on a Friday night with a couple friends. When you are seated, you notice that instead of menus, your waiter has grabbed tablets instead. Your waiter informs you that the restaurant is trying out a new electronic ordering system. The purpose of this new ordering system is to make ordering and waiting at restaurants faster and more efficient and to entertain customers while waiting for their orders to arrive. To help us test the system, we're going to ask you to do some scenario tasks. |
# |
Title of the Task and Statement to User |
Steps of the Task (For our personal use) |
|
---|---|---|---|
1 |
Viewing and Ordering Foods
|
1. Scroll through the menu |
|
2 |
Play Some Games
|
1. Navigate the game screen |
|
3 |
Pay the Bill
|
1. View the bill |
|
4 |
Filter and Comparing Foods
|
1. Filter the menu based on certain specifications |
|
5 |
Ask for Help
|
1. Click on the help button |
|
6 |
Do the Tutorial (Iteration #2 task only)
|
1. When the system starts, click on |
User |
Description (Abridged) |
Lessons Learned |
---|---|---|
1 |
Task: Viewing and Ordering Foods |
Learnabilitiy |
2 |
Task: Viewing and Ordering Foods |
Learnability |
3 |
|
Learnability |
User |
Description |
Lessons Learned |
---|---|---|
1 |
Task: Do the Tutorial |
Learnability |
2 |
Task: Viewing and Ordering Foods |
Learnability |
3 |
Task: Do the Tutorial |
Learnability |
After the first prototype iteration, we noticed a lot of key flaws that caused our prototype design to change. |
One of the most common responses we got was that they did not like our tab system. Some users though that it reminded them too much of web browsers or settings tabs on computers, so they don't "feel" like they were using a virtual menu. This issue was not noticed when we switched to using buttons as navigations system. |
Users would like to know when their food was coming and when they are playing games they want the information to be displayed somewhere. We decided to make the system more efficient by displayed a mini info window in the games in the up right that displays important data like time and estimated food arrival time.
|
One of the users suggested that we added quick tutorials to make the learning curve of the device better. We omitted it in the initial prototype under the assumption that it was unnecessary, but we decided to add it to the second prototype. We did get advise they we should avoid video tutorials and use interactive tutorials. We added the extra task of viewing the tutorial and got good feedback on it. It said it helped them learn of features they did not know available.
|
We are having a difficult time teaching users hows to use the compare feature, since they have to make a list of items they want to compare. At first, we used check boxes but users were unclear whether the check boxes meant added to their order or to the compare feature. During the second round of prototyping we chained it to a "Add to Compare" button would received better feedback, but it was still taking users a long time to use it. We need to make it more intuitive to use for better learnability, easier to add items to the list for better efficiently, and make it more noticeable when users have added it to the list for better efficiently. |
On our first design, we added a pop up when users were adding items to their order where they can customize it and leave a note for the chef. However, one user suggested that since we have so much tablet space, we should display the item description somewhere so that the user can make sure its the item that they wanted. This makes it easier for the user to read the description while adding it to the order for better efficiently and safety by making the users more aware of what they are doing so they don't make errors. |