Users encountered a problem when required to add a new event from the Calendar view. User 2 voiced that he looked for the new event button below the events listed for the day.

To fix this, the new event button was added to the end of the list of events, as it originally was in storyboard 3 of design 2. By having the button here, users will know that clicking the button will add an event to the currently viewed day.

When creating an event, User 1 wanted to be able to see events already scheduled for that day, even though he did not need to see it for the task.

To fix this, a quick summary of the day's events could be added to the new event modal. This way, users can choose drivers more effectively while creating an event.

Some users hesitated while filling out the new event modal because they were unsure which fields they were required to fill out.

As a simple fix, asterisks can be added to each required field along with some text at the top like "* Indicates Required"

When asked to reach out for help, many users did the wrong thing. One user clicked the edit event button while another clicked "Driving Groups" in the top bar.

While part of this may be due to the difficulty of making paper things look clickable, these buttons should still be easier to see. One possible solution is adding a drop down arrow next to them.

Two of the users completely missed that there was a message field in the reach out for help modal.

The message field needs to be more prominent and will have a default message to make users aware.

User 2 and User 3 had trouble knowing which modal they were in or how to navigate back and forth between schedules and list of events within a schedule

We attempted to fix this by adding titles to modals and additional pages to let the user know which screen they were in. Clickable headers gave the option to view the previous page

Users 1 & 2 were not sure what buttons create and add did on the schedules and similar pages

We made buttons positioned properly and more descriptive such as "create schedule", "add event", "submit schedule" that adds additional support for the user.

Users had trouble sharing schedules or view them in their calendar once they were created

Immediately after a schedule is completed, a modal pops up asking if they want to share now or later. If the choose to do so later, they can click the "share" button next to a desired schedule. Also, a "view" button for each event will direct the user to their calendar to the day an event of the schedule is listed

Users had a hard time knowing where to look for shared schedules, or invites to groups/events. It wasn't clear that these items would all land in the inbox.

In addition to showing these invites/shares in the inbox, they are show in the relevant tab. So the schedules page will contain any shared schedule notifications, the activity groups page would contain invites to activity groups and so forth.

When completing the form to indicate driving availability for driving groups, users were not sure how to indicate driving availability.

The buttons that were located at the top middle of an event tile will be removed, and buttons saying "I can drive to" and "I can drive from" will be stacked in front of the event tile.

User 1 noted that he wanted an easier way to assign drivers within a driving group

An auto-assign button will be added to the page which will automatically assign drivers to all events based on which drivers indicated their availability.

Some users could not tell what the use of the driving counter on the driving group page. For example, User 1 tried to drag and drop the names to assign driving responsibilities.

The he counter section will be redrawn as its own tile to have better affordances. This will allow the user to better understand the use of the driving counter and use it effectively.

When attempting to assign drivers, most users tried clicking on the driver button on the driving group's page. This functionality was not considered, as a separate "edit drivers" page was created.

The edit drivers page will be removed, and users will manage drivers for events by clicking on the button within each event tile. This will create a simpler flow, and remove the complexity of another page. It is more efficient for a user to assign and edit drivers from within the driving groups page, rather than navigating to a new page.

User 1 asked if tabs will be highlighted during tutorial

We will show verification with highlighted tabs or borders representing which tab is being described in the tutorial.

User 3 felt that going through the initial tutorial was natural and straight forward. Easily walked through tutorial without many questions.

We will continue to make the tutorial straight forward and conduct a step-by-step process to ensure simplicity and optimize usability

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.

When using drop downs, we will check that when the user moves outside the drop down, it will no longer be viewable.  Also, we will check what information is blocked from a drop down and if it influences any selections for remaining fields in the screen.

User 1 and 3 noticed asterisks for mandatory info when filling in event details

We will keep asterisks as a way to represent information that needs to be filled out.  Still thinking if there are only other clear ways to notify mandatory information.

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.

No change to original design, however, perhaps a shortcut to reaching out to drivers on the toolbar rather than reaching out to a driver for specific event.

User 1 questioned if there was verification when finally selecting a driver (such as no longer highlighted, etc.)

When a user selects a driver, there will be confirmation that the driver is set (whether its highlighting, changing background color, etc.)

All users wondered how to get back to previous screen viewing all schedules from current soccer team schedule

There will be a back button on the current screen to get back to the main schedules tab.

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.

There will be a red number count on top of the schedules tab to distinguish between messages that are in your inbox and schedules that are requesting to be shared.

Users 1 and 3 think drag and drop drivers would be a good idea.

We are thinking of doing drag and drop for drivers, but not sure how to implement it just yet.  Perhaps progress will be made in the computer prototype.

All users were were unclear about the distinction between driving groups and activity groups.

In progress of getting rid of activity groups and rather link people together based on shared schedules/events or carpools.

User 1 and 2 were not sure what modals were, however, User 3 was familiar with modals

Modals are an effective way to keep most of the information viewable on the screen without transitioning between multiple pages.

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 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 title rather than individual "to" and "from" drivers drop downs listed per event. Users 1 and 3 did not have this problem.

Clicking on the title should take one to the edit event page, where one should be able to edit drivers in any case.

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.

If we can figure it out, an auto-assign feature would be nice.