...
Colin's text goes here
Prototype Iteration
(Joao) Description of Changes
Initial Page changes
- Changed names of the options
We realized that the question "Who is here?" was a bit confusing for our users. We decided to change the names of all of the options to represent actions so that the users know exactly were to go when they need to accomplish a task.
- Added large buttons in the middle of the page
In the first version we weren't completely sure about what to put in the middle of the initial page. We decided to include 4 large buttons that do exactly the same thing as the options in the sidebar. We included expressive icons in the buttons that made it easier for first users to know what each option is about.
- Included Report Lunch as one of the initial options
In the first version, Lunch report was an option that appeared in a submenu when the user clicked in Daily Reports. The daycare worker is going to be logging information about the children's lunches fairly frequently and also at a different time than he is going to be filling daily reports. Therefore, as we had plenty of space and it made sense to separate them, we decided to make the Report Lunch a button on its own.
Changes to Check in/out Page
With version 1 there was room for some confusion between the actions of checking in and out. At first we were thinking of separating both actions and make them two completely separate menus. However, it could get confusing to the user because the check in and check out screens would be essentially identical but would do different things (could motivate modal errors). We decided to go with the check in/out screen from the Visual and Simple design. As the daycare worker checkins children he is building a set of kids that are at daycare. The user takes advantage of that set for tasks like reporting lunch.
Changes to Report Lunch page
The interface for entering lunch information was also changed. The name of the page was changed to "Report Lunch" for clarity, and the structure of the interface was changed. Based on user feedback, it wasn't clear or intuitive how the different UI elements interacted, especially the meal entry portion of the interface and the child data entry sections. To remedy this problem, we opted to move the meal entry information into a sidebar and make the child data entry take the center stage in the pain part of the page.
...