...
Analysis of scenario
This scenario identifies three main tasks: -
- Picking ingredients
...
- Finding a recipe and preparing the meal
...
- Getting feedback from kids
Individual Sketches
Sketch 1 Josh: Feedback/Recipe Finder
This sketch is designed to incorporate previous feedback from the kids to find new recipes. When a parent is deciding what to make, they can see how picky a kid is and what they like or are allergic to. They can then search with these preferences automatically placed as filters. When preparing the meal, caregivers have a list that lets them choose what they have and what they need as well as cooking directions. The feedback stage has a slider for the overall meal and binary (heart or broken heart) value for each major ingredient.
Sketch 2 Josh: Kid’s Decide
This design aims at letting the kids have feedback in choosing the meal. Each child can see their previous favorites and search for new dishes. They drag whatever they want for their caregiver to review. The caregiver can then see an aggregated result of what each kid chose and suggestions based on this. If they don’t like any of these options they can also search for dishes. During the prepare phase the caregiver can watch a video of how to prepare the meal and has a static shopping list for ingredients. The feedback system has a rating (0-5) for the overall meal and three buckets, “loved”, “liked”, “never again” for each major ingredient.
Sketch 3 Josh: Mobile Design
The mobile design was designed with efficiency as top priority. During the decide phase, caregivers either search or get a random choice by selecting “Get Ideas”. This system allows a choice to be quickly made, either by knowing what to search for or being inspired by the ideas. Any dish that is selected can be shared so that the dish, ingredients, and shopping list can be sent to others, for example, a wife can send it to her husband to pick up groceries. The feedback system is a single vote for the meal and each major ingredient. Each child can vote +/-1, or 0 for an item and the total score is aggregated for the caregiver.
Sketch 1 Sarah: Basic design
This design was created to cover all of the basic points of ingredient selection, recipe finding, and feedback. From the main page, the parent can either look at/edit the food preferences of the children or search for a recipe based on the preferences of their children. The generated recipe list includes both new recipes and recipes that have been tried before (with their previous rating). After the parent makes the dish, the children can individually rate the recipe and the individual ingredients. The ingredient ratings will be pre-populated based on previous preferences, so the kids only have to rate the new ingredients.
Sketch 2 Sarah: More ingredient control
In this design, the caregivers have a lot of control over which ingredients they want to include in their dish. They can select ingredients based on each of the kids’ preferences, and choose to add new ingredients. On the screen with the recipe, the kids can rate what they thought and the caregivers see how to make the dish. The kids don’t have to rate the ingredients, they will automatically be put in their “will eat” section. If they specifically don’t like something, it is easy to return to the preferences page and change anything.
Sketch 3 Sarah: Design for illiterate users
This UI is designed for illiterate users, so must communicate the flow without words. The log in screen is a combination lock-- the user gets a random code if they click on the “???” button. The next screen has a tile for each of the children, and when they click on it it brings up symbols for the ingredients they like and don’t like. The parent can drag each ingredient into the “shopping cart” box, and from there create a recipe. After selecting ingredients, the parent is brought to the recipe screen where the UI takes them through symbolic representations of the steps. When they have completed this, they can give feedback, also symbolically.
...