Design 2:
...
Storyboard:
...
Modular Forms and Comprehensive Feeds UI
General Design:
This design relies on two main principles:
- The ratio of children to daycare workers is relatively small, and the daycare workers must make custom submissions for each child
- Parents will be able to keep up with the flow of updates as they come
If the ratio of children to daycare workers is small, the daycare workers would be able to go through the list of kids multiple times a day filling out the new custom information each time. Furthermore, if parents can keep relatively on top of all of the updates as they come, they would not need to organize or filter updates and they would benefit from the simplicity of an all inclusive timeline.
Storyboard:
Illustration | Step | Description |
|---|---|---|
| Dan enters ChildFeed App | As Dan enters the ChildFeed app, he is welcome to a main page that has links to all of the sub-pages of the app. |
| Paul drops off Chuck; Dan signs Chuck in | Dan selects the Check-In option from the main page to get to the Check-In page. |
...
Once on the Check-In page, Dan |
...
either |
...
types Chuck's name in the search to force a scroll to his name or he |
...
just manually |
...
scrolls to |
...
Chuck's name in the alphabetically sorted list. Once at Chuck's name |
...
, Dan clicks the check mark to mark him as checked-in. If he makes a mistake, he can just click the x to "un-check" him. After |
...
Dan clicks share, the notification |
...
is sent to Chuck's parents. |
...
| Patricia checks the account; sees notification of Chuck being dropped off | Patricia checks her ChildFeed feed and |
...
sees from the exclamation mark that she has an unread message |
...
. The ChildFeed feed is where all the information is posted and organized chronologically with newest postings posted on the top. Patricia sees the new entry at the top and |
...
sees that her son has been safely checked into the daycare. |
...
|
...
Dan shares photo story of Chuck finger painting | Dan clicks the Events button from the main page to get to the Event page. From there he clicks the "Add Children" button and |
...
types and |
...
selects Chuck's account. He |
...
then |
...
selects the "Text" text box and |
...
types up his comment. |
...
Then, Dan |
...
clicks the "Add Photo" button, |
...
selects the desired photo, and |
...
clicks the "SHARE" button. |
Again,
Analysis:
Learnability:
Efficiency:
| Patricia checks the account; sees notification of Chuck's new story | Again, the new event pops up on Paul and Patricia's ChildFeed feed, so they see that they have an unread story. From the feed Patricia sees a thumbnail of the photo and the first few lines of the comment of the story. Patricia then clicks the story in order to trigger an info box overlay with a larger version of the image and the full additional text. |
| Dan and his coworkers go through the children in his ChildFeed app, logging what they all ate and how much they ate. | As the children eat their meals Dan clicks the "Food" button from the main menu and begins entering each child's meal. To do so, Dan either adds a new meal or selects one of the existing meals and then clicks on each of the children who ate the selected meal(s). Thus in this case, Dan selects "macaroni and cheese" and then selects Chuck. After selecting Chuck, Dan then checks the box marked "a little" and then goes on to log the information for the other children. |
| Paul and Patrica notice that Chuck did not eat much today, and go back to check his eating history, and notice that he doesn’t eat very much whenever they serve macaroni and cheese | Paula and Patricia then get a new notification posted to the top of their feed. Since she notices that Chuck seems to not eat very much when macaroni and cheese is served, she decides to go to the "Analysis" tab to confirm her suspicions. |
| Dan puts all of the kids to sleep and sits down and logs information about each child’s mood, temperament, overall energy, etc. | As the children nap, Dan goes to each of the daily information pages and fills in information for each child. For example, on the Mood page, Dan scrolls through the list of children that were checked-in clicking on either the sad face, the neutral face, or the happy face for each child. After finishing the logging process for each page, Dan clicks share to send the updated information. |
| Patricia checks ChildFeed for overall information on Chuck’s wellness and notices that he is not in a very good mood. | Patricia again notices a new input on her feed with all of the daily information. She sees that Chuck's mood is listed as "unhappy" and knows that she should probably get him something to cheer him up. |
| Patrica picks Chuck up; Dan signs him off . | As Patricia picks up Chuck, Dan goes to the Check-Out page and then searches and selects Chuck as he did on the Check-in page. |
Analysis:
Learnability:
Advantages:
- Each page for the daycare worker has only one functionality, making it easy to know where to go for what
- Selecting children and adding information for each child consists mostly of just searching for the child and inserting the necessary information
- The parents' site consists of just a Feed page where all updates appear in a timeline and an Analysis page where they can visualize the data
Disadvantages:
- There are inconsistencies among how data is submitted among the different pages in the daycare worker's app
- The daycare workers cannot see how the parents get their information, so it delays learning about how their actions affect the parents' feeds
- The parents might not know what is best to analyze in the Analysis section and thus would not know how to take advantage of this feature
Efficiency:
Advantages:
- If there are relatively few children per daycare worker and detailed updates are necessary, the modularity of the pages makes it easier to customize information for each child
- All new information pops up to the top of the parents' feeds, so they can always get the most current updates
Disadvantages:
- No real options for daycare workers to update children's information in batches. So if the information is the same for many of children, entering the information child by child would be inefficient
- The parents have no way of organizing or filtering the parents' feeds, if there is too much information it would get cluttered quickly
- In logging the daily report information, the daycare workers need to go through all of the children multiple times (once per feature to enter)
Safety:
Advantages:
- Before sharing information, the daycare worker can undo anything that they changed with single clicks
- Tasks are modularized so that daycare workers are forced to do only specific tasks at a time, limiting confusion
- The daycare worker can easily review all of his entries before submission
Disadvantages:
- The daycare workers have no way of seeing what his/her actions cause the parent to see
- They daycare workers have no way of deleting or undoing shared messages
...