Page History

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.