...
What can go wrong? (Exceptions, errors, emergencies)
- The user can insert improper and/or incorrect information.
- The information entered can be confusing.
Who else is involved in the task?
No one else needs to be involved in the task, but the manager may ask a chef or photographer to help update the restaurant profile.
What are the subtasks?
- Adding the restaurant description
- Creating individual menu items
- Uploading pictures of individual menu items
- Adding details to individual menu items
- Saving the description
2. Searching and selecting a restaurant (Client)
Why is the task being done?
The client may want to search for a particular restaurant to see its menu, or to find restaurants in the area.
What does the user need to know or have before doing the task?
The user can either search by name, in which case he/she should have the name of the restaurant. Otherwise, the mobile app will use location to search for restaurants.
Where is the task being performed?
The task can be performed anywhere, although it has special behavior if performed at the same location as the restaurant.
How often is the task performed?
This task is performed whenever the user wants to eat or search a menu.
What are its time or resource constraints?
There are no resource constraints but time might be constrained by the client’s hunger or desire to order food. Furthermore, a search is especially tilted in the favor of efficiency.
How is the task learned?
The task is meant to be intuitive and learnable, mirroring other interfaces that users will have seen if they are already mobile phone users.
What can go wrong? (Exceptions, errors, emergencies)
The task is meant to inform clients of the restaurants available to them in an innovative way, and the client will not be able to provide any feedback through the site.
Who else is involved in the task?
No one.
What are the subtasks?
Path 1:
- Check in via-location
- Presented a list of restaurants to choose from
- Select the restaurant
Path 2:
- Enter query into a search bar
- Choose the relevant text-matched name for the restaurant
3. View a Menu (Client/Waiter)
...
What are the subtasks?
- Click on the relevant menu subitems
- Scroll through the relevant food items
- Click on food items for more specific information
4. Filter a Menu (Client/Waiter)
Why is the task being done?
The user wants to see or show a more specific list of the items presented on a particular restaurant menu.
What does the user need to know or have before doing the task?
The type of filter that needs to be applied i.e. vegetarian, gluten-free, meat-only, etc.
Where is the task being performed?
The task can be performed inside of the restaurant before the client orders or while on the go as a precursor to deciding to visit the restaurant. Anywhere the user can access the internet from his/her mobile phone is a valid location for the task.
How often is the task performed?
This task is performed whenever the user wants to get a more specific idea of the menu.
What are its time or resource constraints?
There are resource constraints for data processing and time might be constrained by the client’s hunger or desire to order food and quick feedback.
How is the task learned?
The task is meant to be intuitive and easily learnable. On occasion, waiters might be trained in this task in order to help the client learn the task or search the menu themselves.
What can go wrong? (Exceptions, errors, emergencies)
- The client can select the wrong restaurant.
- The client can select the incorrect filter, and the incorrect specifications to apply it to.
Who else is involved in the task?
A waiter can potentially aide the client in using the app, but it should mainly be used by the client.
What are the subtasks?
- Selecting the relevant filter
- Applying the filter to the relevant list of menu items
5. Review a menu item (Client)
Why is the task being done?
To provide feedback to other customers
What does the user need to know or have before doing the task?
What food they have just eaten and the restaurant they have just eaten it at
Where is the task being performed?
The task is performed at the restaurant after the food is eaten, or at any other location that the user prefers
How often is the task performed?
Every time a user eats an item, and wants to provide feedback
What are its time or resource constraints?
There are resource constraints for data processing and time might be constrained by the client’s willingness to rate a menu and the efficiency with which a submission can be made.
How is the task learned?
The task is meant to be similar to reviews on Amazon or Yelp, demonstrating consistency
What can go wrong? (Exceptions, errors, emergencies)
- The client can select the wrong menu item
- Malicious users can submit incorrect or unnecessary reviews
- The reviewer can enter incorrect information
Who else is involved in the task?
The waiter and manager can view the reviews as feedback.
What are the subtasks?
- Select the appropriate restaurant
- Select the correct food item
- Write a review
- Submit a review