Briefing
ChildFeed is a web app that allows daycare workers to share information about children under their care to the children’s parents in real time.
Using ChildFeed, daycare workers can notify parents of:
- when their child has been checked-in and checked-out of the daycare
- what their child ate that day and how much
- what general mood and energy level their child was in that day
- special events with custom text and attached photos
In addition to checking their feed, parents can also analyze daily information using customizable visual representations.
Note that ChildFeed is meant to be a one way communication system from the daycare workers to the parents. Also, ChildFeed is not designed to be used in cases of emergency.
In this scenario, you are Dan Donald a day care worker. We will be giving you a series of tasks that we would like you to try your best to accomplish using our prototype interface. As you attempt these tasks, we ask that you vocalize your thought process to the best of your ability, so that we can better understand what is clear and unclear in our design. Note that there are no wrong answers and that we just ask you to try your best at accomplishing the given tasks.
Thanks for your help and remember that you are free to leave the experiment at any time.
Scenario Tasks
# |
Task |
|---|---|
Task 1 |
Check-in Chuck, Derp, and Herp. |
Task 2 |
Notify Chuck's parents that Chuck got covered in paint today and please include a photo of this adorable event. |
Task 3 |
Log that everyone except Derpina had macaroni and cheese for lunch. Derpina had tomato soup. Log that everyone ate a healthy amount except for Herp, who ate so much he threw up. |
Initial Prototype
Photos go here.
Observations
Colin's text goes here
Prototype Iteration
(Joao) Description of Changes
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.
We also modified the paradigm behind this portion of the interface, slightly. Instead of the lunch report feeling like a story that is "published", the lunch report now feels like a log, where you add information and submit it. Daycare workers can go back to the Report Lunches page at any time and edit the information entered if need be. As such, we eliminated the need for the checkboxes for the child tiles. This is a good change because we had problems with people knowing that they need to check or uncheck boxes when reporting lunch information for specific children.
Users were also confused by the fact that adding the first menu item will fill it by default to all child tiles, but not the second. Instead, we opted to make the meal sidebar not fill any information by default, and instead added a "Fill All" button next to each meal item.
Photos go here.
Iteration Observations
Colin's text goes here