...
Observations | Prototype Iteration |
|---|---|
User 1 asked if tabs will be highlighted during tutorial |
|
User 3 felt that going through the initial tutorial was natural and straight forward. Easily walked through tutorial without many questions. |
|
User 1, when selecting attendees, wondered if multiple people that are added will be stacked on top of each other below the field or fill in order on a line. Also wonders if this is covered up by pop-ups or drop-downs. |
|
User 1 and 3 noticed asterisks for mandatory info when filling in event details |
|
When User 1 was finding drivers, first scanned the top toolbar since it looked permanent and natural place to look. Eventually found "reach out" in specified event. |
|
User 1 questioned if there was verification when finally selecting a driver (such as no longer highlighted, etc.) |
|
All users wondered how to get back to previous screen viewing all schedules from current soccer team schedule |
|
It was unclear for users where to check for invitations. They naturally headed to the inbox, rather than the schedules page. It wasn't clear from the design that the schedules page had a pending invitation/request. |
|
Users 1 and 3 think drag and drop drivers would be a good idea. |
|
All users were were unclear about the distinction between driving groups and activity groups. |
|
User 1 and 2 were not sure what modals were, however, User 3 was familiar with modals |
|
User 2 preferred to type information into event fields rather than using drop downs | Parsing user input might potentially be a hard problem to solve (since the user may enter times in one of a gazillion different formats) so perhaps it should be made obvious that it's only possible to pick times from a modal, or otherwise some other simple means of input. |
Users had a hard time figuring out which events may be conflicting for picking up/dropping off/driving. | It would be beneficial in the calendar page to show an overview of the user's activities for the day in terms of driving, in chronological order, in order to discern where any conflicts may arise. We can't figure this out strictly algorithmically because say, dropping two kids off to two separate events at the same time needn't conflict if you can drop them off on time along the way. |
It wasn't entirely obvious where one had to click in order to edit an event. The single "pencil" button (to indicate editing) wasn't obvious enough in the design. | Make clicking on the event anywhere pop up a quick-edit modal. |
User 3 had a hard time looking for a kid's particular schedule. Tried clicking the kid's name in the calendar to see his events, rather than going to the schedules section. | In production, the way you find out that you have a schedule invite is that the respective tab will show a badge with the number of notifications, so the user will naturally know to click on that tab. |
Users 1 and 2 wondered if there was a way to filter between selecting groups and individual people. | The drop-down box should have a "pick a person or group" text hint to indicate the multiple functionality. |
User 2 noticed that he can simply cater alter and adjust message to clarify drivers he wants to reach out to | When reaching out to drivers, there should be a pre-filled message with the event info, or it should be such that the event info is automatically shared and when the driver accepts the request, it is added to his/her calendar too, and the event data is synced. |
When User 2 wanted to edit an event by adding a driver, mistakenly clicked on event tile rather than individual "to" and "from" drivers drop downs listed per event. Users 1 and 3 did not have this problem. |
|
User 2 had trouble viewing a specific schedule when already viewing a list of events for a given day. User then notices "schedules" tab and that it helps categorizes events. |
|
Users found the task of manually assigning all of the drivers to a schedule tedious, and noted that an "auto assign" feature would be useful. |
|
...