...
She takes out her iPhone and presses, “Food is here.” She then types “5th floor” as the location and hits send. The other people will now get a notification that their food is ready and that they should pick it up.
Designs
Design #1
Task: Creating an Order
Sketch:
Story:
This is the main starting page of the application. When a user wants to order a meal, they first pick a time slot. The time slot is the approximate time when the food will be ready for pickup. Each time slot closes 30 minutes before the delivery time to give the runner time to collect the money and pick up the food.
...
If the user makes a mistake, they can always go back and edit their order or remove it entirely.
Task: Picking a Runner
Sketch:
Story:
After a user has added their order, they are asked if they are willing to be a runner. A runner will be the person that goes down to the trucks and picks up the food. They are presented with a simple three-option dialog box. This dialog is displayed after the user taps either the “Add order” or “+1” buttons.
...
Safety:
The main safety concern here is if the user accidentally taps “Yes” by mistake. Or, if they tap “Yes”, but then something else comes up and they can’t pick up the food. Their decision can be undone by tapping the “Runner” tab on the bottom of the application. The runner tab will show which time slots they are current the runner for. All they need to do is change their selection here.
Task: Collect Money
Sketch:
Story:
Once a timeslot closes, the runner will be sent a notification and asked to enter into a three part process: collect money, place orders, and notify eaters.
...
The key concern here is accidentally indicating that a person has paid. This is easy to correct - all the user needs to do is hit the check box again and it will reverse the decision.
Task: Place Order
Sketch:
Story:
This is the second screen for the runner - indicated by the dots near the bottom of the UI.
...
There really are no safety concerns with this UI. If the runner accidentally taps the checkbox on the wrong order, all he needs to do is tap it again to uncheck it.
Task: Notify Eaters
Sketch:
Story:
This is the last screen for the runner - indicated by the dots near the bottom of the UI.
...
The text box on this screen defaults to the last submitted location. This is helpful if the runner always delivers the food to the same place - for example a lounge or kitchen area. Instead of typing in the location over and over again, all they need to do is tap “Notify”.
Safety:
*Given the fact that the text field defaults to the last message, a common error that may occur is that the runner just taps “Notify” out of habit and accidentally sends the wrong location. However, that is okay. The notification screen allows the runner to send out multiple notifications. If they make a mistake, all they do is send out another message saying, “Sorry - the food is actually on the kitchen counter”.*
Alternate Scenarios
As a group we also explored other scenarios. We felt that the scenario shown above best encapsulated our findings from our user and task analysis. Nevertheless, we brainstormed other scenarios that we thought were also valuable. Those are included here.
...